Accessibility work splits into three layers, and only one of them is a job most people can walk into.
Automated scanners catch missing labels, contrast failures and structural errors. A conformance audit covers what the standard specifies and is a profession with credentials attached. Between them sits the layer neither reaches: a flow that satisfies every checkpoint and still defeats the person using it.
Finding that requires someone who uses assistive technology as their ordinary way of working, at their ordinary speed. That is the work being paid for here.
What it pays
| Work | Typical reward |
|---|---|
| Real-usage session on a task marketplace | $20 – $40 |
| Moderated session through a research panel | $60 – $150 |
| Ongoing tester with a product team | Hourly, often $40 – $90 |
| WCAG conformance audit | A separate profession, priced accordingly |
The rate is set by scarcity rather than session length. A screen reader user on iOS is genuinely hard to recruit, and briefs that need one are priced to reflect it. If a task is paying general user-testing rates for assistive technology expertise, that is a client who does not understand what they are buying.
What a session actually involves
You are given an outcome, not a route
"Buy the cheapest item in the sale and reach confirmation." A brief that lists the steps has removed the navigation problem, which is usually where the finding is.
You work at your normal speed
Not carefully. Careful use hides exactly the problems being paid for, because nobody uses anything carefully in real life.
You report the highest friction point
One place you nearly gave up is worth more than a list of twelve small annoyances, and it is the one that costs the client customers.
You say what you would have done unpaid
Often the honest answer is "left". Knowing where is the deliverable.
The artefact is usually a screen recording with the assistive technology audio where the platform allows it, plus the exact software and version. That version detail matters more than people expect: behaviour differs enough between screen reader versions that a report without it is hard to act on.
What to refuse
Three things come up often enough to name:
- Unpaid requests. Framed as helping, as advocacy, or as exposure. It is expert labour and the framing does not change that.
- Requests to work carefully. A brief asking you to be thorough and methodical has misunderstood the instrument. Normal speed is the method.
- Requests for a conformance verdict. A usage session cannot produce one, and a client who represents it as an audit is exposing themselves and misrepresenting your work. Say the distinction plainly; most clients accept it once stated.
Why this work is growing
Regulatory pressure is the honest reason. The European Accessibility Act obligations landed in 2025, procurement processes increasingly require conformance statements, and litigation in several markets has made inaccessible checkout flows expensive.
Most of that drives audit demand rather than usage testing. But teams that have been through an audit generally discover the gap this page opens with: they now pass the standard and still have users who cannot finish. That is when they start looking for testers.
Where to find it
Specialist panels and agencies pay best and recruit slowly. General testing marketplaces carry occasional work and vary in how well they brief it.
On Brief Buck it appears as a bounded task naming one assistive technology and one journey, with the reward set for the expertise rather than the minutes. The accessibility spot check page sets out what a client is asked to specify — including that it does not substitute for an audit, and that findings of "this technically works and is horrible" are the point.
If you are looking at general website testing rather than accessibility specifically, user testing jobs covers the wider market and what it pays.