Section 508 Trusted Tester
Accessibility testing with nothing hidden.
See every barrier I find. I can fix it, or teach you and your AI agent to, and set up guardrails so it stays fixed.
- No subscription
- No widget
- Yours to keep
Try it on this page
Not sure where to start?
Start with why you’re here.
You don’t need to know WCAG or Section 508 to begin. Pick the situation closest to yours, answer a few questions, and I’ll suggest what to test first.
-
We got a legal letter or complaint
Every barrier it names checked by hand within 5 business days, fixes quoted from what holds, and a dated retest for counsel. Fixed price $995.
See the letter response: We got a legal letter or complaint -
A customer asked for a VPAT or ACR
A record has to rest on testing. You get a result for every criterion with its evidence, signed by a named Trusted Tester. The record with its audit, $1495.
See the record: A customer asked for a VPAT or ACR -
We sell to government
Testing follows the Section 508 Trusted Tester process, done by a certified Trusted Tester, and ends in the ACR a federal or state buyer asks for.
See the record: We sell to government -
We run a Shopify store
Your theme, your apps and Shopify’s checkout each add their own code. A fixed-price review sorts every barrier by where it comes from.
See the store review: We run a Shopify store -
We just want to get it right
Start with the one thing your customers must be able to do, such as checking out or booking, and see where they get stuck.
Start here: We just want to get it right
An easy first step is the Starting-point review: $495, fixed price, with the full amount credited toward a full audit. See what’s included
Fixing it yourself? Your coding agent can use every guide through the free accessibility MCP server.
What automated accessibility checkers miss
Passes every automated check. Still blocks people.
Each example below gets a clean result from automated accessibility checkers. Each one stops a customer. Only a person at the keyboard notices.
- ✓ Automated check: 0 issues
✗ Focus ring exists. Nobody can see it.
- ✓ Automated check: 0 issues
✗ Error shows. It doesn’t say how to fix it.
- ✓ Automated check: 0 issues
✗ Dialog opens. The keyboard is stuck behind it.
- ✓ Automated check: 0 issues
✗ Order placed. The screen reader says nothing.
Why the checks pass and people still get stuck See how to fix each one
About accessibility widgets
A widget alone is not a fix.
Overlay widget added
✗ The badge says WCAG AA. The button still has no name, until someone files a complaint.
Fixed in the code
✓ The button gets a real name in your code. Every screen reader reads it.
Low contrast is the easiest problem to find. A free checker spots it in seconds, yet it is still one of the most common failures on the web.
Already paying for a widget, scanner or AI auto-fix? See what it still misses
From scope to staying fixed.
- 1
Scope
Agree on pages, interactions, methodology, and deliverables.
- 2
Test
Combine useful automated checks with manual evaluation.
- 3
Report
Document barriers, impact, and practical next steps.
- 4
Fix
I fix the code and keep your design, or support your developers while they do, then retest the fixes.
- Guardrail Checks I build into your CI. Blocked? Your developer fixes it.
- 5
Release
Every release passes the guardrail first, so new barriers don’t go live.
After the first pass, releases don’t start the whole line again: the guardrail catches regressions, and a full test by hand comes round only periodically. How the guardrail works
Watch your audit progress.
Your private client space shows who picked up your audit, by name, and how many checks are done so far. Once the date is confirmed, it shows when your report is expected. When testing finishes, you can see it's in its final quality check before it's shared.
Not sure yet? Send your questions with your request. The person who will do the work answers them by email.
Checkout and account pages
Picked up by (your tester's name)
- Oct 17
Useful
detail.
Clear next steps.
Review findings in a private client space. Your team can discuss changes and request agreed retesting alongside the original evidence.
Explore the deliverableMain menu cannot be opened with a keyboard
Global issue All tested pages · Main menu
The menu trigger is a clickable div. Tab skips it, so the navigation links cannot be reached with a keyboard.
WCAG 2.1.1 Keyboard Test 4.A
- How to fix it
- Use a native button for the menu trigger. Keep its expanded state in sync with the menu and make sure the revealed links are reachable.
- Read the solution in Learn
A focused scope. A clear starting price.
Start with an important journey or a small set of templates. One person does the work, with no sales team or account manager in the price, so testing by hand is within reach of a small business, not only a large one. We agree on the work and total price before testing begins.
See pricing and scope| First unique page or template | Starting at $149 |
|---|---|
| Additional unique page or template | Starting at $99 |
| Repeated-template or light supporting page | Starting at $49 |
Enterprise: Contact us for custom pricing.
Scope depends on unique layouts, components, states, and workflows—not URL count alone. Complex and authenticated workflows receive a custom quote. Remediation and retesting are separate unless your quote includes them.
Tell me what needs testing.
Share your website, the journeys that matter most, and any deadline or access requirements.