Accessibility QA Tester

Role

Checks whether access features, alternatives, and presentation conditions work in practice.

Description

An Accessibility QA Tester verifies that a project's access features actually work: captions appear where and when they should, seated mode keeps everything reachable, remapped controls persist, audio description triggers fire, and the accessible path through the experience survives each new build.

Access features break quietly. A patch that moves an interface element or retimes a scene can disable an alternative that nobody on the team uses daily, and without dedicated verification the failure surfaces only when the person who needed it is already in the headset.

Discipline-Specific Description

Within the testing family, this role applies QA discipline to access: repeatable checks, regression passes, and device coverage aimed specifically at access features and presentation conditions, build after build.

Scope Note

May include regression testing of access features, caption and audio description checks, alternative input verification, seated and standing mode passes, calibration and reach checks, and per-build documentation of the access conditions actually tested.

Boundary Note

This role verifies that designed access features function. The Accessibility Tester evaluates the wider experience for barriers, including ones no feature yet addresses, and the Accessibility Designer decides what to build in the first place. Verification, evaluation, and design fail in different ways, which is why the guide keeps them distinct.

Collaboration Note

Collaborates with accessibility designers and testers, QA leads, the developers who own access features, and facilitation teams who put those features in front of real audiences.

Related entries