Accessibility consulting
Accessibility reviews
A review done in the markup, with the findings turned into checks your build runs from then on.
The engagement
What it costs and how long it runs
Stated up front, because these are the questions everything else depends on. The price is where the work starts, not a quote: scope moves it.
- Starts from
- $6,000
- Typical length
- 2 to 3 weeks
- Standard
- WCAG 2.2 AA, AAA where reachable
- Delivered as
- Findings, fixes and build checks
Detail
What the work is
A review against WCAG, done in the markup rather than in a dashboard, with automated checks added to your build so the findings stay fixed.
An automated scan finds the problems that can be found by a machine, which is roughly a third of them. It cannot tell you that a link says “read more”, that a focus order jumps across the page, or that two elements both claim to be the page you are on.
So the review is done by using the site: with a keyboard only, with a screen reader, at 200% zoom, and with the colours measured rather than eyeballed. What comes back is a list of things a person could not do, each one tied to the markup that stopped them.
Then the findings become checks. A document describing what was wrong in March is worth very little in June; a build that fails when the mistake comes back is worth the same in both months.
Scope
What it includes
Everything below is part of the price. Anything not on this list is quoted separately rather than assumed.
- Keyboard, screen reader and contrast testing on real pages
- Findings written as build-time checks, not a one-off document
- Colour and typography adjusted to clear AAA where it is reachable
Process
How it runs
In this order, with each step finishing in something you can look at rather than a status update.
1. Use the site properly
Keyboard, screen reader, zoom and reduced motion, on the journeys that matter rather than on a sample of templates.
2. Measure what can be measured
Contrast ratios against both colour schemes, target sizes, and heading outlines read as a document rather than looked at as a page.
3. Write the checks
Each finding that a build can detect becomes a check in your build: missing alt text, skipped heading levels, duplicate ids, contradictory aria-current.
Outcomes
What is different afterwards
Not what happens during the work, but what you are left holding when it is over.
Findings that stay fixed
The regression that would have quietly returned in a redesign now stops the build the day it is introduced.
AAA where it is reachable
Colour and typography adjusted to clear 7:1 in both schemes, which is a decision about tokens rather than a pass over the pages.
A record you can show
What was tested, how, and what the result was — in a form that answers a procurement question without being rewritten first.
Services
The other three
They combine: an audit often ends in a build, and a migration usually starts with one.
From $12,000 · Web development
Site builds
A complete site, compiled once into plain HTML. Routes, components and content in TypeScript, deployed to an edge that only has to serve files.
From $4,000 · Performance engineering
Performance audits
A measured account of what your pages actually send and how long it takes to paint, followed by the specific changes that would move the numbers.
From $18,000 · Web development
Migrations
Moving a site off a framework it has outgrown, keeping every URL, redirect and search ranking intact through the change.
Sound like the right one?
Describe the site, what you want to be different about it, and roughly when.