Legend accessibility
See original GitHub issueIn their current form, in our product we can’t use the builtin react-vis
legends as they provide no keyboard accessibility, specifically tabindex
and aria-*
attributes.
Probably a bit wide for one issue, but it would be nice to be able to make series that have event handlers focusable too.
As always, happy to pitch in with a PR along these lines!
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Using the fieldset and legend elements
When used correctly, the <fieldset> and <legend> elements tie related form fields together in a way that is accessible to people who cannot ......
Read more >Grouping Controls | Web Accessibility Initiative (WAI) - W3C
Accessibility resources free online from the international standards ... The legend for a group of controls can also highlight common attributes of all ......
Read more >Fieldsets, Legends and Screen Readers - TPGi
The fieldset and legend elements are a useful part of a web developer's toolkit for making forms more accessible to people with disabilities....
Read more >fieldset must have one legend
The Functional Accessibility Evaluator (FAE) evaluates a website or a single ... Definition, Every fieldset element must contain exactly one legend element.
Read more ><fieldset> <legend> Accessibility Demos - Paul J. Adam
<fieldset> <legend> Accessibility Demos. http://pauljadam.com/demos/fieldsetlegend.html. Note on differences in Screen Reader Behavior: Not all screen readers ...
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
@mcnuttandrew (and anyone else who might be playing along at home) - in the midst of putting together a PR here - should have it in by the end of the week.
@mcnuttandrew
I’m going to do a bit more digging, but from what I can tell,
react-a11y
actually inspects rendered elements, so might catch more than the linter, which is just static. It does mutate theReact
object though, so we should only use it when hacking on the library (and potentially testing), not in the packaged build - it’s also pretty verbose in your console