-
Notifications
You must be signed in to change notification settings - Fork 84
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
Remove <nav> from pagination #686
Conversation
fixes zostera#449 Providing a fixed label is not feasible because this project does not have any translations yet. From the other two options, I guess that not having a <nav> element is better than having an unusable one.
Pull Request Test Coverage Report for Build 10888063486Details
💛 - Coveralls |
Removing the |
Perhaps a setting for |
Not really. As explained in #449, the current implementation does not follow best practices because it does not contain a label. Removing the Adding a parameter would allow authors to fix this issue, but the default would still be broken. That's why it is not my preferred option. But if you really think that adding a parameter is the way to go, I can adapt the code accordingly. |
I don't use screen readers myself. I can imagine that a |
I sent a mail to the Web Accessibility Initiative Interest Group Discussion list: https://lists.w3.org/Archives/Public/w3c-wai-ig/2024JulSep/0113.html So far, both answers recommended to remove the |
I'd say that settles it then. And we have documented the why and what in this issue. Thanks for all the effort you put into this @xi 🙏 |
fixes #449
Providing a fixed label is not feasible because this project does not have any translations yet.
From the other two options, I guess that not having a
<nav>
element is better than having an unusable one.