We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
role=figure
role=group
Hi. I greatly value a11y.css as a tool for quick assessment, but this warning about role="group" throws me off every time... There is an open ticket on the referenced WAI Tutorial repo indicating that, as of 2017, ARIA 1.1 provides role="figure". Since this is the implicit ARIA role of the <figure> tag, shouldn't this be the correct role to assign, rather than overriding it with group? An investigation by Scott O'Hara and his markup recommendation seem to support that as well: https://www.scottohara.me/blog/2019/01/21/how-do-you-figure.html PS: I summarized my "research" on the issue on my blog.
Hi. I greatly value a11y.css as a tool for quick assessment, but this warning about role="group" throws me off every time...
role="group"
There is an open ticket on the referenced WAI Tutorial repo indicating that, as of 2017, ARIA 1.1 provides role="figure". Since this is the implicit ARIA role of the <figure> tag, shouldn't this be the correct role to assign, rather than overriding it with group? An investigation by Scott O'Hara and his markup recommendation seem to support that as well: https://www.scottohara.me/blog/2019/01/21/how-do-you-figure.html
role="figure"
<figure>
group
PS: I summarized my "research" on the issue on my blog.
Originally posted by @sebastiangreger in #121 (comment)
The text was updated successfully, but these errors were encountered:
feat(figure): recommend [role=figure] insted of [role=group] to fix #392
538c489
fix(warning): improve figure test in #392 after lint
fa6467c
db9c0ef
e8fab4b
ffoodd
Successfully merging a pull request may close this issue.
Originally posted by @sebastiangreger in #121 (comment)
The text was updated successfully, but these errors were encountered: