Use button instead of span for disabled prev/next controls #3277
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes here.
Per accessibility audit feedback, the current
span
s used for the prev/next links when disabled are not announcable by screen readers. Instead ofspan
s, we should usebutton
s so that these disabled elements are focusable.I also updated the CSS to match the text styling of the buttons to the same styling used when the links aren't disabled.
Screenshots
Please provide before/after screenshots for any visual changes
Before:
After:
Merge checklist
Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.