Accessibility Tester interview questions and answers

9 of 9 questions shown

1. juniorStandardsWhat are the four WCAG principles and the target level?

   Model answer. Perceivable, Operable, Understandable and Robust (POUR). Conformance levels are A, AA and AAA, and most laws and procurement rules point to AA, currently WCAG 2.1 or 2.2 AA.

   Tools: axe / WAVE

   I can answer this
2. juniorKeyboardHow do you test keyboard accessibility?

   Model answer. Put the mouse aside and tab through the page. Order must be logical, focus must be clearly visible and not hidden behind sticky headers, there must be no keyboard trap, Enter and Space must activate controls, and Escape must close dialogs. Custom widgets should follow the ARIA Authoring Practices keys.

   I can answer this
3. juniorVisualWhat contrast ratios does WCAG AA require?

   Model answer. 4.5:1 for normal text and 3:1 for large text (18 pt, or 14 pt bold). Success criterion 1.4.11 also requires 3:1 for UI component boundaries and meaningful graphics against their background.

   I can answer this
4. midToolsHow much can automated tools catch and what do you check by hand?

   Model answer. Automated engines such as axe find roughly a third to half of issues, mostly missing labels, contrast and invalid ARIA. Humans must check alternative text quality, focus order, reading order, error messages, zoom and reflow, and the screen-reader experience.

   Tools: axe / WAVE

   I can answer this
5. midARIAWhat is the first rule of ARIA?

   Model answer. Do not use ARIA if a native HTML element already provides the semantics and behaviour: use button, not a div with role button. ARIA changes what assistive technology hears but adds no keyboard behaviour, and wrong ARIA is worse than none.

   I can answer this
6. midAssistive techWhich screen reader and browser combinations do you test?

   Model answer. NVDA with Firefox or Chrome and JAWS with Chrome on Windows, VoiceOver with Safari on macOS and iOS, and TalkBack with Chrome on Android. At minimum cover NVDA and VoiceOver, and check headings, landmarks, form labels, live regions and dialog focus.

   I can answer this
7. midFormsWhat makes a form accessible?

   Model answer. Programmatically associated labels, instructions before the field, and errors identified in text and linked with aria-describedby. Focus moves to the first error or an error summary. Add autocomplete attributes (1.3.5), indicate required fields without relying on colour, and never use placeholder-only labels.

   I can answer this
8. seniorSPAHow do you test route changes in a single-page app for screen readers?

   Model answer. After navigation, focus should move to the new page heading or the page title should be announced, document.title must update, and focus must not fall back to the body. Verify with NVDA and VoiceOver and check that the Back button restores the previous state.

   I can answer this
9. seniorReportingHow do you report accessibility defects and what is a VPAT?

   Model answer. Map each issue to a WCAG success criterion, state who is blocked, give steps with the assistive technology and browser versions, and rate severity by whether a task can be completed. A VPAT, which produces an Accessibility Conformance Report, states per criterion whether the product Supports, Partially Supports or Does Not Support it.

   I can answer this

No question matches those filters. Clear the search or choose All.