-
Notifications
You must be signed in to change notification settings - Fork 54
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
Fix pagination: make previous and next buttons accessible #2102
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for boosted ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This comment was marked as outdated.
This comment was marked as outdated.
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
ok, with the "title", i think, it's usable :) |
This comment was marked as outdated.
This comment was marked as outdated.
All looks good to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👌
Related issues
Closes #2008
Description
We currently have an a11y problem in pagination related to WCAG 2.1 Success Criterion 1.3.1 Info and Relationships (Level A) and WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence (Level A). It stated that all content must be available in text even when the CSS stylesheets are disabled.
If we disabled our stylesheets, the result is:
So:
It appears that the
<
and>
are conveying informations so they need to be focusable even when CSS is off.With this prototype:
Please note that I made the change only on the
previous button
to show the difference with thenext button
.Motivation & Context
Improve a11y of pagination component
Types of change
Live previews
Checklist
Contribution
Accessibility
Design
Development
Documentation
Checklist (for Core Team only)
After the merge