Accessibility Checklist for QA and Testers

Use this checklist when testing websites, applications, components, and digital services. Accessibility testing should combine automated tools with manual evaluation.

Automated Testing

  • Run the approved automated accessibility testing tool.
  • Review findings rather than relying only on a score or issue count.
  • Verify automated findings and document false positives when necessary.
  • Remember that automated tools detect only a portion of accessibility barriers.

Keyboard Testing

  • Complete all critical functionality using only the keyboard.
  • Verify focus is always visible.
  • Check that focus moves in a logical order.
  • Confirm there are no keyboard traps.
  • Verify menus, dialogs, tabs, accordions, and other interactive components support expected keyboard behavior.

Zoom and Visual Testing

  • Test content at increased browser zoom and narrow viewport widths.
  • Verify content reflows without loss of information or functionality.
  • Check text and meaningful interface elements for required contrast.
  • Verify information is not communicated by color alone.
  • Check that focused controls are not obscured by sticky headers, dialogs, or other content.

Forms and Dynamic Content

  • Verify form controls have clear labels and accessible names.
  • Test required fields, instructions, validation, and error recovery.
  • Confirm errors are clearly identified and associated with affected fields.
  • Verify status messages and important dynamic updates are communicated to assistive technology when needed.
  • Test dialogs and other components for correct focus management.

Assistive Technology

  • Test critical user journeys with an appropriate screen reader.
  • Verify controls expose meaningful names, roles, values, and states.
  • Check headings, landmarks, lists, tables, and form structure using assistive technology.
  • Verify meaningful images have useful text alternatives and decorative images are ignored.
  • Test with more than one environment when project risk or requirements warrant it.

Defects and Regression

  • Document accessibility defects with clear reproduction steps and expected behavior.
  • Identify the affected user interaction and severity, not just the technical criterion.
  • Retest accessibility defects after remediation.
  • Include accessibility in regression testing for changed components and critical workflows.
  • Escalate unresolved barriers that prevent users from completing critical tasks.

Accessibility is a shared responsibility. Use this checklist as a practical starting point and seek additional accessibility expertise when needed.

Off