Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upDeque's Axe Plugin catches WCAG violations in base storybook boilerplate #11062
Comments
|
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
|
Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook! |
|
Automention: Hey @Keraito, you've been tagged! Can you give a hand here? |
Describe the bug
When running Deque's Axe plugin on a webpage, I found multiple accessibility errors with the Storybook boilerplate.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Axe should return no errors.
System:
Binaries:
Node: 10.15.3
npm: 6.4.1
npmPackages:
@storybook/cli: 5.3.17
@storybook/html: 5.3.17
Additional context
Some issues have already been opened with solutions to the problems within Storybook's boilerplate. I've linked to those, where applicable. I have also linked directly to Deque's documentation on the required fixes for each accessibility defect.
Page must have means to bypass repeated blocks.
Page must have one main landmark.
Page must contain a level-one heading.
All page content must be contained by landmarks.
Text Elements must have sufficient color contrast against the background
Running the plugin before every release will help validate that no accessibility bugs exist and that consumers are compliant when building out storybook applications. Thank you for your time!