Tab index issue with aria-hidden vs. hidden
See original GitHub issueI see you recently changed the hidden
attribute to aria-hidden
. Would it be possible to render both attributes? I’m using your component in dynamic forms and it messes up the tab index. hidden
will instruct the browser to not include the input when tabbing through the form, aria-hidden
won’t.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (11 by maintainers)
Top Results From Across the Web
aria-hidden elements do not contain focusable elements
A focusable element with aria-hidden="true" is ignored as part of the reading order, but still part of the focus order, making it's state...
Read more >aria-hidden-focus - Accessibility Insights
In some browsers, the attribute aria-hidden="true" hides an element and all its children from assistive technologies. Users can still use the keyboard to ......
Read more >Elements with aria-hidden="true" are not focusable - Rules
This rule checks that elements that have been excluded from the accessibility tree using the aria-hidden attribute with a value of true are...
Read more >Element with aria-hidden has no content in sequential focus ...
This rule checks that elements with an aria-hidden attribute do not contain elements that are part of the sequential focus navigation and focusable....
Read more >aria-hidden - Accessibility - MDN Web Docs - Mozilla
Description · Purely decorative content, such as icons or images · Duplicated content, such as repeated text · Offscreen or collapsed content, such ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@martyf Thanks for all the work on this! I just published v2.0.0 with all your good good changes!
@martyf Thanks! I’ve been thinking about it and I think I agree with you. The most important use case is completely hiding the element (and then adding a
hidden
attribute), and the partial hiding can be an opt-in thing. I’d probably add a section to the docs about that and bump the major version.Can you prepare a PR?