Services · Compliance & standards
A Web App Audit Has to Do the Tasks, Not Crawl the Pages
For the SaaS team whose product lives behind a login, where enterprise buyers ask hard accessibility questions and a scanner score is worth less than it is anywhere else. Scope here is measured in tasks rather than URLs, and we agree the list with you before anything is charged.
What We Keep Finding
Apps fail differently from websites. The page never reloads, so nothing tells a screen reader what changed unless the app was built to say it. A modal opens, focus stays behind it, and a keyboard user is suddenly typing into a form that is visually gone. The dashboard updates live and silently, and the person who most needed to hear the new number is the one who does not.
Which is why an app audit has to work the app rather than crawl it. Create the record, change the setting, read the chart, invite the teammate. Our own free scanner is the proof of that gap, because it sees one state per page and never opens a dialog, submits a form, or triggers an error. It also cannot sign in, and it refuses anything on a private address or a non-standard port, which is most staging environments. A tool cannot know what your product is for. A tester can be told.
Two of the components that fail most often have published reasons, and they are worth knowing before your team argues about them. The combobox pattern changed substantially in ARIA 1.2 because the earlier guidance kept being implemented badly, which is why so much of the tutorial code on the web is now wrong. And the modal is mostly solved already, because a native dialog element opened with showModal() moves focus in, keeps Tab inside, closes on Escape, makes the background inert, and returns focus on close. Most of what we find is a div wearing a dialog's clothes, rebuilding all five and getting some of them wrong.
What We Check
- Work real tasks end to end while logged in, rather than scanning pages
- Test focus management on every modal, drawer, and route change
- Verify live updates announce, so toasts, saves, errors, and loading states
- Check whether a step announces its change or moves focus to it, because doing both says it twice
- Check the components tools misread, meaning comboboxes, tabs, and data grids
- Cover the keyboard completely, single-key shortcuts and escape routes included
What You Get
Every service on this site runs the same three-pass engine: an automated scan, an expert review of all 55 WCAG 2.2 A and AA rules, and a hands-on session with a professional blind screen-reader user. You get one report with every finding screenshotted, ranked by user impact, and linked to its fix. Your team fixes, we verify: the re-audit is half price within 3 months.
The format is not a mystery either. Read the sample report before you spend anything.
The Honest Limit
One honest limit, and a note about scope. We audit the journeys we can reach with the test account you give us. We ask for that by email once the scope is confirmed rather than through a web form, because a public form is the wrong place for credentials. Features gated behind roles we were not given stay untested, and the report names them rather than assuming they are fine. On scope, the tiers are written in pages and an app route can be one URL and 20 states, so we agree a task list with you at scope confirmation and count that instead. Ten pages of a dashboard would mean nothing to either of us.
What It Costs
Rapid Audit: $499, up to 10 pages you pick, report in 5 business days. Standard Audit: $1,499, up to 25 pages in 10 business days. Flat rates, no discovery calls, and a real blind screen-reader user on every engagement. Pick your pages. We bring the humans.
Worth Reading Next
Related on this site
Guides, checklists, tools, and terms that go with this service.