Accessibility Testing for Quality Assurance (QA)s
Accessibility testing checks that people using screen readers, keyboards, magnification or other assistive tools can use a product. It follows the Web Content Accessibility Guidelines, WCAG, which group requirements as perceivable, operable, understandable and robust, and combines automated scanners with manual keyboard and screen reader checks.
Stage: Non-functional Testing · Part of the Quality Assurance (QA) roadmap · Last reviewed 19 November 2026
What to learn in Accessibility Testing
- Explain the four WCAG principles with one example each
- Navigate a page using only the keyboard and note focus order problems
- Check text and background colour contrast against the required ratio
- Verify images have meaningful alt text and form fields have labels
- Run axe or Lighthouse and understand what automation cannot catch
- Test a flow with a screen reader such as NVDA
Accessibility Testing interview questions
Why can automated tools not fully test accessibility?
Scanners catch rule-based issues like missing alt attributes or low contrast, but they cannot judge whether alt text is meaningful, whether focus order makes sense or whether a flow is usable with a screen reader. Manual checks are still needed.
What is the minimum colour contrast ratio for normal text under WCAG AA?
WCAG 2.x level AA asks for at least 4.5 to 1 for normal text and 3 to 1 for large text. Level AAA is stricter. A contrast checker tool computes the ratio from the two colour values.
Where Accessibility Testing fits in the Quality Assurance (QA) roadmap
Accessibility Testing belongs to the Non-functional Testing stage (beginner level), which takes about 3 hours. Beyond happy paths.
Other units in this stage
Back to the full Quality Assurance (QA) roadmap