Skip to content
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

Closed
rajeevnaikte opened this issue Feb 11, 2016 · 14 comments
Labels
Milestone

Comments

@rajeevnaikte
Copy link

@rajeevnaikte rajeevnaikte commented Feb 11, 2016

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
Copy link
Contributor

@jcsteh jcsteh commented Feb 12, 2016

@rajeevnaikte
Copy link
Author

@rajeevnaikte rajeevnaikte commented Feb 19, 2016

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
Copy link
Contributor

@jcsteh jcsteh commented Feb 20, 2016

@kvn-dh-zeus
Copy link

@kvn-dh-zeus kvn-dh-zeus commented Jun 29, 2017

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
Copy link
Contributor

@jcsteh jcsteh commented Jun 30, 2017

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

@derekriemer
Copy link
Collaborator

@derekriemer derekriemer commented Jul 1, 2017

@kvn-dh-zeus
Copy link

@kvn-dh-zeus kvn-dh-zeus commented Jul 4, 2017

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 jcsteh changed the title When role is application NVDA reads every div as section Firefox: NVDA reads aria-hidden divs as section when they are ancestors of the focus Jul 5, 2017
@jcsteh
Copy link
Contributor

@jcsteh jcsteh commented Jul 5, 2017

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
Copy link
Contributor

@jcsteh jcsteh commented Jul 5, 2017

@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
Copy link

@kvn-dh-zeus kvn-dh-zeus commented Jul 24, 2017

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

@jcsteh jcsteh closed this in #7357 Aug 1, 2017
@nvaccessAuto nvaccessAuto added this to the 2017.3 milestone Aug 1, 2017
@derekriemer
Copy link
Collaborator

@derekriemer derekriemer commented Aug 2, 2017

@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
Copy link

@kvn-dh-zeus kvn-dh-zeus commented Aug 7, 2017

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
Copy link
Collaborator

@derekriemer derekriemer commented Aug 11, 2017

latest version of which track?

@kvn-dh-zeus
Copy link

@kvn-dh-zeus kvn-dh-zeus commented Aug 18, 2017

@derekriemer working fine right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

5 participants
You can’t perform that action at this time.