You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notes for a potential blog post on the topic of accessibility testing when using Theme Builder
Thoughts on next steps and tasks that can be created to integrate these tools with Theme Builder end to end design and testing
Proposed Solution
Evaluation observations, suggestions and notes for blogs and potential next steps should be included as comments on this issue, for review by the Theme Builder core maintainers.
The text was updated successfully, but these errors were encountered:
@lwnoble has a contact at Chromatic. Currently they do isolated, component-level testing, but not testing in context. We can ask them if they are interested in expanding the scope of their product (with our assistance). Otherwise probably not the best tool for us to use.
Commented on the Design Ops issue, but also would comment here:
Testing:
Accessibility Insights for Web - free Chrome/Edge extension that contains automated, guided, and manual test abilities. Very comprehensive - lots of tests that are available for free and it has a GitHub integration too that makes it easy to file issues. There is also tooling available for Windows + Android apps.
axe-devtools - freemium offering - Chrome extension with only automated tests are free. axe API is free up to a point - its Developer Hub offering is paid. Also has mobile offerings.
@storybook/addon-a11y - Storybook accessibility plugin - runs automated checks using axe api
eslint-plugin-jsx-a11y - plugin for ESLint - allows us to catch common accessibility issues + extend the configuration to map Material UI elements to HTML elements
For Designers:
axe for Designers - contains accessibility annotations + auto scan functionality
Stark - color contrast tool for designers - includes a lot more than just color contrast, including functionality for developers
Suggestion/Concern
The goal of this issue is to research how accessibility testing can be:
The outcome of this research should include:
Proposed Solution
Evaluation observations, suggestions and notes for blogs and potential next steps should be included as comments on this issue, for review by the Theme Builder core maintainers.
The text was updated successfully, but these errors were encountered: