-
Notifications
You must be signed in to change notification settings - Fork 5
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
Deprecation of doc-endnote
role
#22
Comments
Hello Xavier, Thank you for reaching out and for the kind words. I wasn’t aware, so very nice of you to share this information! I guess as soon as Axe flags this as “not okay”, we should update the library’s markup to remove it. Until then, I guess it’s fine to keep it. :) |
Just wanted to chime in here! Lighthouse unfortunately flags this as an accessibility issue, stating that |
Shall we just remove that attribute? I’ll happily accept a PR and publish it. :) |
@KittyGiraudel Sure! I can push up a PR. Edit: Although I'm not sure: Do we want to remove just the |
Done in v0.11.0. Thank you! :) |
Hi Kitty,
First, thank you for this component (and generally for all your works) which helped us build our own into aem env.
I would like your point of view concerning the deprecation of the
doc-endnote
role: https://www.w3.org/TR/dpub-aria-1.1/#doc-endnote and the recently change into Axe dequelabs/axe-core#2759What is your recommandation about this change? Should we simply remove the role on
<li>
or change it for another one likedoc-footnote
?Thank you for your time and your answer.
Xavier.
The text was updated successfully, but these errors were encountered: