Accessibility support
See original GitHub issueDescribe the bug
CheckboxTree
is almost completely unuseable with a screen reader, or a keyboard.
Reproduction steps
- Attempt to expand / collapse nodes with a keyboard.
- Try to read the contents of the tree view with the NVDA screen reader.
Expected behavior
The tree is completely operable via the keyboard, and reads correctly for screen reader users. See https://www.w3.org/TR/wai-aria-practices-1.1/#TreeView
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Accessibility Support - Official Apple Support
Find information about Apple's built-in accessibility tools and technologies that help people with disabilities get the most from their Apple products.
Read more >Accessibility Support
Please run some tests to help keep this project going and to learn about assistive technologies along the way. Features. Find support for...
Read more >Google Accessibility Help
Browse help topics · Accessibility support · Android accessibility · Chrome accessibility · Workspace accessibility · Chromebook accessibility · YouTube accessibility.
Read more >Documenting Accessibility Support for Uses of a Web ...
The documentation of accessibility support for uses of a Web technology provides the information needed to determine whether it is possible to satisfy...
Read more >Accessibility - Google
Google's support of accessibility extends beyond accessibility tools to include both external and internal research efforts. Back to top.
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
No updates, unfortunately. Accessibility is a high-priority addition, so it will be included in the next release.
I admit I have been terrible at finding time in the past. The recent outbreak has done little to stem this, as it has coincided with an increased workload in my professional capacity. My intention is to resume development on the next release sometime late April or early May, but timelines may change.
@zhr1130 I’ve created an MR that is still pending review, but if you want, you can use my branch with some fixes