Mid-LevelTest Automation & Frameworks
How do you test accessibility (a11y) in your automation suite?
- accessibility
- axe-core
- WCAG
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Integrate axe-core via `@axe-core/playwright` or `cypress-axe`. Run automated a11y scans as part of your test suite, check for missing alt text, color contrast, ARIA roles, keyboard navigation. Automated tools catch ~30-40% of a11y issues (WCAG violations). Supplement with manual keyboard-only testing, screen reader testing (NVDA/VoiceOver), and user testing with people who use assistive technology.
What interviewers listen for
- Test architecture instinctsYou can defend why your suite is shaped like a pyramid, a trophy, or a honeycomb.
- Locator disciplineYou rank selector strategies by stability and explain when to break the rule.
- Flaky test ownershipYou debug to a structural fix instead of retry-until-green.
- Parallelisation literacyYou know how your framework isolates state, fixtures, and database access across workers.