Improve accessibility compliance for keyboard navigation - #125
Conversation
Improved accessibility and keyboard navigation features.
|
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
|
Beep boop 🤖 I noticed you didn't make any changes at the
In order to keep track, I'll create an issue if you decide now is not a good time
|
iago1501
left a comment
There was a problem hiding this comment.
Hi @RichardByrneCP , thanks for the PR, just added some minor suggestions
Co-authored-by: Iago Espinoza <iago1501@gmail.com>
Co-authored-by: Iago Espinoza <iago1501@gmail.com>
Co-authored-by: Iago Espinoza <iago1501@gmail.com>
|
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
What problem is this solving?
The VTEX slider pagination dots were implemented using
<div>tags withrole="button". However, they lacked keyboard focus (tabindex="-1") and did not respond to keyboard inputs. This prevented users who rely on keyboards or screen readers from navigating the product shelves, violating WCAG 2.1 Success Criterion 2.1.1.This PR transforms the static pagination dots into fully interactive keyboard-accessible elements. Key technical changes include:
tabIndex={0}, allowing users to navigate through dots sequentially.How to test it?
Use keyboard navigation to scroll through the product carousel using the pagination dots.
https://accessibility1--colproatqa.myvtex.com/
Screenshots or example usage: