Accessibility testing careers: demand, skills and pay

01How visible is accessibility testing?

We searched 3,863 public postings for accessibility, a11y and WCAG in the title and for accessibility testing tools in the stack.

Accessibility appears in the stack of general QA and automation roles as often as in accessibility roles. In this sample it is a skill added to a QA job at least as often as a job of its own.

02What drives demand

Three things push demand up, even if job titles do not show it yet.

• Law and procurement. The European Accessibility Act has applied to many consumer products and services in the EU since 28 June 2025. In the US, a 2024 Department of Justice rule sets WCAG 2.1 AA as the technical standard for state and local government web content.
• Standards. WCAG 2.2 has been a W3C Recommendation since October 2023. Audits are written against it.
• Risk. Accessibility complaints are treated as legal risk, so audits are often bought as one-off projects.

Project-shaped demand suits task-based work. Our Flex board lists accessibility audits as one of seven task types; 2 are open now.

03Skills and pay

The skills list we use for accessibility tester roles:

• WCAG 2.2
• Screen readers
• HTML and ARIA
• axe
• Audit reports

On Flex, an audit task runs 1-3 weeks at 3-4 h/day and pays $35-75 an hour. Example: WCAG 2.2 AA audit of a checkout with screen readers.

04A route in

A practical route from general QA:

1. Learn the WCAG 2.2 success criteria at level AA. Read the criteria, not summaries.
2. Add automated checks (axe or WAVE) to an existing suite. Know what they cannot catch.
3. Test with a screen reader: NVDA on Windows or VoiceOver on macOS and iOS. Both are free.
4. Write two audit reports against a real product with severity and fix guidance.
5. Take Flex audit tasks to build a track record, or look for accessibility work inside QA roles.

See the Accessibility Tester role, its salary guide and Flex task types.

05Method and limits

Sample: 3,863 public postings harvested 20 Oct 2026 from employer career pages and public job feeds. Listings are postings, not people or confirmed openings: one role open in several cities counts several times (2,417 distinct titles across 3,863 postings). PassRidge talent-pipeline roles (149) are excluded from every statistic.

Title matching uses the words accessibility, accessible, a11y and WCAG. A role can do accessibility work without saying so in the title, so these counts are lower bounds. There are too few accessibility postings with a published pay range to publish a posted median; our salary model for this role leans on adjacent roles.

The method for roles, tools and pay is documented on our salary methodology page. Spot an error? Write to [email protected].