-
-
Notifications
You must be signed in to change notification settings - Fork 915
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
title / description for accessible svg #116
Comments
Our current accessibility guidance was kindly provided by @LJWatson in #50. As per the article you listed - https://css-tricks.com/accessible-svgs/#article-header-id-11 - we use |
Then we would need |
Well, at least the given guidance is not correct in most cases and misses some things. I'm fine with this if this is documented with some examples somewhere or the CSS Tricks or anything else linked . |
OK - I'm very happy if you want to edit the README to include more accessibility information. |
The icons already use The The advice to use |
Mh, is the browser support the same? Thanks for the clarification. Currently we test with pa11y / Koa11y. |
<Mh, is the browser support the same?< With the exception of |
So it may make sense that we stick to desc/title in svh elements as we also optimize for IE11. |
To be on the safe side, yes. It seems that Jaws and NVDA both have workarounds, meaning that the accessible name is announced even when it's applied using |
Interesting. Thanks for the information. Could be useful for our further testing. And thanks for taking the time give feedback on my proposal. @edent should I keep the issue open and propose an update to the readme with the CSS Tricks article or what do you think? |
Yes, please update the README with clear guidance 😀 |
…m-refactoring Medical website contact form refactoring
Afaik we should use title/description as this is what most a11y testing tools like pa11y, Koa11y and so on are looking for.
https://css-tricks.com/accessible-svgs/
Also
role="img"
,aria-hidden="true"
and similar solutions might be needed in accessible projects.The text was updated successfully, but these errors were encountered: