How our accessibility testing works
From form to finished report in a few days. Here's exactly what happens, and what we check.
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.
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.
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 do screen reader testing, zoom to 200% and 400%, and check color contrast and motion.
We write it up in plain English
You get an accessibility audit report where each issue has 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.
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.
Our website accessibility audit checklist
- Keyboard access, focus order, visible focus, and keyboard traps
- Screen reader names for links, buttons, images, and form fields
- Headings, landmarks, page titles, and page language
- Form labels, instructions, and error messages
- Color contrast of text and interface parts
- Zoom to 200% and reflow at 400% (320 pixels wide)
- Motion, media, and anything that moves on its own
What we need from you
- Your site address and the pages that matter most
- A test account or test mode if a task needs a login or checkout
- For a Fix Sprint: a limited editor login, which you can remove when we're done
Pick a package
All three are fixed-price packages, from $299. See a sample report first if you like.