E-mail List Archives
Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows
From: Jonathan Avila
Date: Jan 27, 2021 11:10AM
- Next message: Brooks Newton: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Previous message: Jonathan Avila: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Next message in Thread: Brooks Newton: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Previous message in Thread: Jonathan Avila: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- View all messages in this Thread
One reason why trees and other widgets may not be navigable with browse mode is that they require knowing the focused element. In browse mode JAWS and NVDA (no longer) sets focus to the elements on navigation with arrow keys. Focus setting would need to occur - but this has potential side effects that would need to be handled. It's likely something that could be addressed but my guess is that it's tricky.
Jonathan
- Next message: Brooks Newton: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Previous message: Jonathan Avila: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Next message in Thread: Brooks Newton: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Previous message in Thread: Jonathan Avila: "Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- View all messages in this Thread