An accessibility audit your developers can act on.
We test your website or app by hand and with assistive technology, against WCAG 2.2 AA, AODA, Section 508 or ADA. Then we help you fix what we find.
Five ways people use your site. We test all of them.
A scanner checks your code. People use your site with a keyboard, a screen reader, a magnifier or their own colours, so that's how we test it.
Audit note: 4.1.2Passes These are native <details> elements, so screen readers announce whether each one is expanded or collapsed.
Keyboard onlyPeople with motor disabilities, and anyone using a switch device.
We complete every key journey without a mouse: navigation, forms, menus, dialogs and checkout. Focus must always be visible, move in a sensible order, and never get trapped.
- Tools
- A keyboard, and nothing else
- Catches
- 2.1.1 Keyboard
- 2.1.2 No Keyboard Trap
- 2.4.3 Focus Order
- 2.4.7 Focus Visible
Screen readersBlind and low-vision people who listen to the page.
We listen to each journey on the screen readers people actually use, on desktop and mobile. Every control has to announce what it is, what it does and what state it is in.
- Tools
- JAWS, NVDA, VoiceOver, TalkBack
- Catches
- 1.1.1 Non-text Content
- 1.3.1 Info and Relationships
- 4.1.2 Name, Role, Value
Zoom and magnificationPeople with low vision who enlarge text or the whole screen.
We enlarge text to 200% and zoom the page to 400%, and check that nothing is cut off, overlaps, or needs scrolling sideways to read.
- Tools
- ZoomText, browser zoom, iOS and Android zoom
- Catches
- 1.4.4 Resize Text
- 1.4.10 Reflow
Colour and contrastPeople with low vision or colour blindness.
We measure text, icons and focus indicators against the contrast minimums, and check that no information is carried by colour alone.
- Tools
- TPGi Colour Contrast Analyser, WebAIM Contrast Checker
- Catches
- 1.4.1 Use of Color
- 1.4.3 Contrast (Minimum)
- 1.4.11 Non-text Contrast
Automated baselineEvery page in scope, so manual time goes where it matters.
An automated pass finds the mechanical issues quickly, such as missing alt text, empty links and unlabelled fields, before we start testing by hand.
- Tools
- axe DevTools, Lighthouse
- Catches
- 1.1.1 Non-text Content
- 2.4.4 Link Purpose (In Context)
- 3.3.2 Labels or Instructions
What each person on your team gets
- Developers
- A findings report. Every issue has its location, severity, who it affects, how to fix it and the WCAG criterion it breaks. See a sample report
- Leadership and legal
- A prioritised roadmap: where you stand against the standard, and what to fix first.
- Procurement
- An Accessibility Conformance Report (VPAT), written from the audit, if your buyers ask for one.
- Everyone
- A call to walk through the findings and answer your team's questions, and one re-test of every finding after your fixes, within 90 days of delivery.
Then, fixing it
Either way, we work from the audit report we deliver. See what each option costs.
Which rules apply to you
Canada
Ontario's AODA requires public sector organisations and businesses with 50 or more employees to meet WCAG 2.0 Level AA on their public websites. Federally regulated organisations fall under the Accessible Canada Act.
Canada's accessibility requirementsUnited States
Section 508 covers federal agencies and the technology they buy. The ADA covers businesses open to the public, and courts have applied it to websites.
We test to WCAG 2.2 AA, which covers everything the WCAG 2.0 AA legal baseline requires. This is a summary, not legal advice.
Audits are led by our founder, Sarah Tugcu, a member of the International Association of Accessibility Professionals (IAAP).
Tell us what's in scope.
Send us the site or app, the key user journeys and your deadline. Audits start at $950 CAD, fixed price, with monitoring included. We'll reply with a quote. See pricing