Automated a11y testing in CI and its limits
WHAT IT TESTS: building a11y checks into CI while knowing their ceiling. OUTLINE: axe-core in unit and story tests, fail the build on violations, plus manual screen-reader and keyboard testing.
WHAT IT TESTS: whether you can automate accessibility checks and honestly state what they miss. ANSWER OUTLINE: run axe-core against component stories or unit tests in CI, fail builds on new violations, add linting like eslint-jsx-a11y and contrast checks, and gate pull requests. Then acknowledge limits: automated tools catch only a fraction of issues and cannot judge focus order quality, meaningful labels, or screen-reader experience, so pair them with manual keyboard and assistive-tech testing.
Read the original → interview
- #accessibility
- #ci-cd
- #testing
- #axe-core
- #automation
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.