E-mail List Archives
Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows
From: Jonathan Cohn
Date: Jan 27, 2021 8:50AM
- Next message: Benjamin.Hofer@telekom.de: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Previous message: Mark Magennis: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Next message in Thread: Benjamin.Hofer@telekom.de: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Previous message in Thread: Mark Magennis: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- View all messages in this Thread
Hello,
Thinking about this a little more, Touch Navigation mode in JAWS or Object Navigation mode in NVDA should be able to view the individual elements of the tree. I believe however, that few Screen Reader users know how to use these modes.
To enable Touch mode in JAWs press shift with numpad plus. Object Navigation mode in NVDA is just using numpad arrow keys and the insert/zero numpad key.
Best wishes,
Jonathan Cohn
> On Jan 27, 2021, at 10:25, Mark Magennis < <EMAIL REMOVED> > wrote:
>
> It seems a bit strange to me too Ben but it's not confined to treeviews. Take a menu for example. Jaws enters forms mode in a menu (role="menu"). I would have expected that if I exit forms mode by pressing numpad + while still in the menu Jaws, now in virtual mode, would respond to the down arrow by reading the next element instead of traversing the menu. But instead, it traverses the menu, wrapping if that's the behaviour the menu scripting implements. So it seems that while you are inside a menu, Jaws passes key presses to the browser no matter what and you can't stop that. Which makes me wonder why it needed to enter forms mode in the first place.
>
> Mark
>
>
- Next message: Benjamin.Hofer@telekom.de: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Previous message: Mark Magennis: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Next message in Thread: Benjamin.Hofer@telekom.de: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Previous message in Thread: Mark Magennis: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- View all messages in this Thread