w3.org states elements with `role='gridcell'` should be owned by an element with `role='row'`
See original GitHub issuehttps://www.w3.org/TR/wai-aria-1.1/#grid states that elements with role='gridcell'
should be owned by an element with role='row'
.
With the current implementation of FixedSizedGrid
or VariableSizedGrid
I don’t think this is possible as there aren’t any elements surrounding a row of cells once rendered in the DOM.
Is this something that could be added so that full aria support becomes possible?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:7 (4 by maintainers)
Top Results From Across the Web
The Roles Model | Accessible Rich Internet ... - W3C
When a widget is missing required owned elements due to script execution or loading, authors MUST mark a containing element with aria-busy equal...
Read more >The Roles Model | Accessible Rich Internet ... - W3C
Authors MUST ensure that elements with role gridcell are owned by elements with role row , which in turn are owned by an...
Read more >Accessible Rich Internet Applications (WAI-ARIA) 1.1 - W3C
See related gridcell . Authors MUST ensure elements with role cell are contained in, or owned by, an element with the role row...
Read more >6. Supported States and Properties - W3C
When a widget is missing required owned elements due to script execution or loading, authors MUST mark a containing element with aria-busy equal...
Read more >ARIA in HTML - W3C
This specification defines the authoring rules (author conformance requirements) for the use of Accessible Rich Internet Applications ...
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
Wondering if #218 has any plans to happen. Lacking screen reader accessibility is totally a deal-breaker for me and my company. Sad that we invested some time with this library to realize this is not possible to be used in a production environment where accessibility is required.
Maybe adding a note on the readme file would help to be aware of the lack of accessibility support for this specific scenario?
I think for this specific case https://bvaughn.github.io/react-virtualized/#/components/Table is a solid alternative.
By the way, thank you for the amazing work @bvaughn
I’d love to review ideas, yes. Can’t promise to land them, but it would be helpful for discussion.