Skip to content
RED SAGSkills
mediumQA Engineer interview question

How do you include accessibility testing in your normal QA work for a web application?

What the interviewer wants to hear

  • Use WCAG 2.2 AA as the target standard
  • Automated checks with tools like axe or Lighthouse, also in CI
  • Manual keyboard-only testing: focus order, visible focus, no traps
  • Screen reader testing with NVDA, VoiceOver or TalkBack
  • Check contrast, zoom and reflow, form labels and error messages, alt text
  • Shift left: accessibility in acceptance criteria and design reviews

Model answer

I treat WCAG 2.2 AA as the target and build checks into each story rather than leaving them to the end. Automated scans with axe, in DevTools and in our Playwright suite, catch issues like missing labels, low contrast and bad ARIA quickly. But automation finds only part of the problems, so I also test manually. I complete key journeys using only the keyboard, checking focus order, visible focus and that dialogs trap and return focus properly. I use a screen reader such as NVDA or VoiceOver to confirm buttons, images and errors are announced clearly. I zoom to 200% and 400% to check reflow, and confirm errors are not shown by colour alone. I also ask for accessibility notes in acceptance criteria and design reviews, because fixing them early is much cheaper.

Can you answer it under time pressure?

Take a timed medium round and get scored on every answer.

Start mock interview

More medium QA Engineer questions