-
-
Notifications
You must be signed in to change notification settings - Fork 176
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
Accessibility #13
Comments
@gregoriopellegrino Very good point. I will add this to my TODO list. |
You might be able to use the table header for axis names and legend. That way the table header cells are visible elements that will be triggered by the screen reader. For many charts the first th will be the main variable, the following th:s will be either categories which could be used as a legend or a single variable that could be used for the secondary axis. I guess the calculations for this will be a bit tricky to work with since the preference for layout differ a lot. Still, might be worth investigating. |
I saw this this morning and thought I might as well have a stab at the most obvious change for Pull request: #23 |
@ramiy now that 1.1.0 is out, should this issue be closed, or is accessibility still an issue? |
I'll check |
Yes, it was fixed. As of v1.0.0, elements are no longer hidden with @gregoriopellegrino Thank you for your valuable feedback. |
This approach is very interesting and - relying on tables - could also be very accessible.
However, from a first text with the screen reader I noticed that important labels (
thead
,th
, etc.) are hidden withdisplay:none
. This makes them completely hidden from assistive technologies.Perhaps with another approach you can achieve the same result, while maintaining the high level of data accessibility, for example: https://webaim.org/techniques/css/invisiblecontent/
The text was updated successfully, but these errors were encountered: