Six phases. Zero surprises.
Our method is built on one rule from the flight line: you don't sign off on what you haven't inspected. Every finding is tied to something we tested, rated on a published scale, and reviewed with you before it becomes final.
Scoping
We agree on what's in scope (sites, apps, key user paths, documents), the standard you're measured against, the browsers and devices that matter, and your deadline. You get a fixed-scope, fixed-price proposal before testing starts.
Automated scan
We run automated rule checks across the pages and screens in scope. This catches common problems quickly, like missing labels and many contrast failures, and shows us where to look closer. Automated tools find only part of what WCAG covers, so this is a starting point, not the result.
Manual & assistive technology testing
We work through each key path the way people with disabilities do: keyboard only, with a screen reader (NVDA on Windows, VoiceOver on Mac and iOS), zoomed to 200 and 400 percent, and with attention to forms, error messages, focus order, and content that changes on the page.
Findings review with you
We walk every finding with your team before anything is final. If you have context we didn't, like a fix already in progress or content that's being retired, we note it. A finding you haven't seen before the final report is a failure of process.
Final report & briefing
You get a severity-ranked findings report mapped to WCAG or Section 508, a summary for leadership, and, for SaaS vendors who ordered one, a VPAT® / ACR written from our results. We brief the people who need to hear it.
Independent retest
When you've made fixes with whoever you choose, book a retest. We retest the original findings and report what's resolved and what's still open.
Rated by what it stops people from doing.
| Rating | What it means |
|---|---|
| Critical | Blocks some users from finishing a key task, with no workaround. |
| High | Makes a key task very hard, or blocks a secondary task. |
| Medium | Causes real difficulty or confusion, but a workaround exists. |
| Low | Fails a requirement with limited effect on completing tasks. |
A widget is not an assessment.
Overlay tools add a toolbar or script on top of a site. The underlying code that screen readers and keyboards rely on stays the same, which is where most of the problems we find live.
- Automated detection covers only part of WCAG. Many problems need a person to find them.
- Disability advocates and many assistive technology users have publicly opposed overlays.
- In 2025 the Federal Trade Commission finalized an order against an overlay vendor over claims that its product made websites compliant.
Start with a scoping call.
Thirty minutes to confirm scope, standard, and deadline. You'll leave with a fixed-scope proposal.