Tabstop Audits

How it works

From form to finished report in a few days. Here's exactly what happens.

  1. You tell us about your site

    Fill in the intake form: your site address, roughly how many pages it has, the platform it's built on, and which package you're interested in. We confirm the pages in scope in writing before any work starts.

  2. We run automated scans

    We scan each page with axe-core and Lighthouse, and review it the way the WAVE tool does. Scanners are fast and consistent, but they can only test some WCAG criteria and can't tell whether alt text actually makes sense.

  3. A person tests it by hand

    We put the mouse away and use only the keyboard: can we reach every link, button, and form field? Can we see where focus is? Then we listen to the page with a screen reader, zoom to 200% and 400%, and check color contrast and motion.

  4. We write it up in plain English

    Each issue gets a severity, the WCAG 2.2 success criterion, where it is, why it matters to real people, and how to fix it. Developers get code snippets; owners get a summary they can read in five minutes.

  5. You fix it, or we do

    Hand the report to your web person, do it yourself, or add a Fix Sprint. Full Audits include one re-test of fixed issues within 60 days.

What the report looks like

We audited the W3C's intentionally inaccessible demo page so you can see a real report without exposing anyone's business. Read the sample report.

What we need from you