-
-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firefox: NVDA reads aria-hidden divs as section when they are ancestors of the focus #5741
Comments
If NVDA is reading "section" multiple times, that suggests that you're
focusing multiple divs in quick succession. As for "document", that will
be read if content gets focused inside of a document, which is certainly
expected. We need more thorough details or a test case in order to
provide any further info.
|
I found the cause of this issue of reading "section". When overlay is opened was setting aria-hidden="true" to the overlay itself instead of other(non-overlay) child elements of body. But didn't understand that, why even after setting aria-hidden="true" NVDA was reading all the text? |
Sorry; there's literally nothing we can do here without a minimal test
case. Please provide one if you want someone to look into this. Thanks.
|
If we focus a div which is not sibling of currently focused div & it is grandchild of sibling of currently focused div, then NVDA is reading "section" for twice for 2 parent div present. So how can I fix this issue. This time I'm not focusing over each divs coming in the way in quick succession. If this is due to browser's default behavior, please provide a solution for that. |
Please provide a minimal test case. We cannot provide any further information without one. Thanks. |
I see this on twitter, but have no clue why. I just Hear "section " over
and over basically.
…On Thu, Jun 29, 2017 at 6:38 PM, James Teh ***@***.***> wrote:
Please provide a minimal test case. We cannot provide any further
information without one. Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5741 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFGivQ63-ClAn9QkSa7NNyK7RjJUgUq-ks5sJEOIgaJpZM4HYL1L>
.
--
Derek Riemer: Improving the world one byte at a time!
- University of Colorado Boulder Department of computer science, 4th
year undergraduate student.
- Accessibility enthusiast.
- Proud user of the NVDA screen reader.
- Open source enthusiast.
- Skier.
Personal website <http://derekriemer.com>
|
@jcsteh You also can refer below link: |
Thanks for the test case. I can indeed reproduce the issue with that. Note, however, that focusing content inside an aria-hidden tree is an authoring error. The spec actually says that aria-hidden trees should not be exposed to accessibility at all, so assistive technology users possibly won't be able to interact with your focusable element at all. In Firefox, users can interact with focusable aria-hidden elements (which allows the user to work around authoring errors somewhat), but this should not be relied upon. |
@derekriemer commented on 1 Jul 2017, 20:14 GMT+10:
Looks like Twitter briefly focuses an aria-hidden element when expanding a tweet. It shouldn't do this, but ideally, we'd ignore it. We'll deal with the weird NVDA bug that causes this "section section section" reporting, but p3 because this only occurs due to authoring error. |
Where can we find updated version of nvda with fix of this issue? |
@kvn-dh-zeus commented on Jul 24, 2017, 5:33 AM MDT:
It'll be live in about 3 weeks. The RC for 2017.3 is about 2 weeks away, and after that, the 2017.3 release will be a week later barring any bugs, to which we'll delay until they are fixed. |
Currently in latest version, NVDA do not reading anything in any website only in firefox (Updated NVDA few minutes ago). Is there any settings needed in firefox for latest update? @jcsteh @derekriemer @nvaccessAuto |
latest version of which track? |
@derekriemer working fine right now. |
As we are using many YUI widgets and custom events/event handlers, we made our HTML body as role='application'. But, when we focus on an element it starts reading section multiple times (it is reading section for all parents of the focused element). And also when an overlay is opened, NVDA starts reading - , document, .
The text was updated successfully, but these errors were encountered: