Firefox: NVDA reads aria-hidden divs as section when they are ancestors of the focus

[rajeevnaikte]

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, .

[jcsteh]

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.

[rajeevnaikte]

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?

[jcsteh]

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.

[kvn-dh-zeus]

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.

[jcsteh]

Please provide a minimal test case. We cannot provide any further information without one. Thanks.

[derekriemer]

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>

[kvn-dh-zeus]

nvda section.txt

@jcsteh
Try attached html in firefox with nvda. Issue it not present for role application, it is replicated for aria-hidden="true".
While aria-hidden="true" is given to any div, (inside that div) nvda reads "section" for each div coming their way while focusing some control element.
How can we fix this issue?

You also can refer below link:
https://codepen.io/kevindhadukzs/pen/XgqBem

[jcsteh]

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.

[jcsteh]

@derekriemer commented on 1 Jul 2017, 20:14 GMT+10:

I see this on twitter, but have no clue why. I just Hear "section " over
and over basically.

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.

[kvn-dh-zeus]

Where can we find updated version of nvda with fix of this issue?

[derekriemer]

@kvn-dh-zeus commented on Jul 24, 2017, 5:33 AM MDT:

Where can we find updated version of nvda with fix of this issue?

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.
Thanks.

[kvn-dh-zeus]

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

[derekriemer]

latest version of which track?

[kvn-dh-zeus]

@derekriemer working fine right now.