How it works
Six steps, each ending in something you can check.
When we finish, every fix is documented, and anything still open is listed in the report.
From the first scan to a published statement.
We work in your site’s real code and content. Nothing is layered on top.
Each step ends with something you can see: a number, a report, a quote, a fixed page, a statement.
We do every step; you give us access and answer a few questions.
- Site scan
- Report
- Quote
- Fix
- Re-test
- Accessibility statement
- Monitoring, if you choose it
We test against WCAG 2.1 AA, the level the 2024 ADA rule for state and local governments uses as its technical standard (its compliance dates were extended in 2026 to April 2027 and April 2028). Title III has no technical regulation for businesses, and the Justice Department points to WCAG. We also check the newer WCAG 2.2 criteria where they apply. ADA.gov: the 2024 rule · Federal Register: 2026 extension · WCAG 2.1 · WCAG 2.2
Real fixes in your code. A full report. A written commitment.
We fix the code itself.
The barriers are repaired in your site’s own theme, templates and content, not hidden behind a menu or an overlay.
What we fix:
- Color contrast
- Alt text for images and icons
- Headings and page structure
- Keyboard access
- Forms: labels, required fields, errors
- Visible focus
- ARIA names, roles and states
- PDFs and documents
- Captions and transcripts
- Zoom, reflow and touch targets
The delivery date is written in your quote.
The fix stays yours
Every fix lives in your code, so it stays even if you stop working with us.
You get a log of every change.
If an issue we fixed comes back within two months of delivery, we fix it again for free.
Every issue documented. Every fix proven.
Before we change anything, you get a full report: how many accessibility issues your site has, which ones they are, where they appear and how serious each one is.
At delivery you get an updated report with your site’s score, the number of errors and a dated log of every fix. In the re-test, we run the automated scan again across several tools, check what a screen reader receives from the site (labels, headings and component names), and confirm the focus indicator stays visible during keyboard navigation.
Our commitment at delivery
At delivery, every page in your report meets each WCAG 2.1 AA criterion we tested. If one is found unmet on those pages, we fix it free.
Our target is WCAG 2.2. The minimum we commit to is WCAG 2.1 Level AA.
What the commitment covers, and what it does not
- It is a promise about our work. It is not legal advice, and it is not a promise of protection from claims or lawsuits.
1. Scan: the automated pass, then the full audit.
The site scan ($29) runs an automated checker over your pages and gives you the number of issues it finds.
That number is useful, but it is only part of the picture: automated tools cannot judge whether alt text makes sense, whether the order of a page is logical, or whether a checkout can be finished with a keyboard. WebAIM Million, on the limits of automated testing
So the full audit goes through your key pages and journeys (home, menus, search, product or service pages, forms, booking and checkout) the way a visitor would:
- Keyboard only: every link, menu, dialog and form step with Tab, Shift+Tab, Enter, Space and Esc, with a visible focus.
- Screen-reader information: we check the information the site passes to screen readers, including labels, headings, and component names and roles. We do not run listening tests with a screen reader.
- Zoom and reflow: text at 200%, and the layout at a 320-pixel-wide window without sideways scrolling.
- Color and contrast, motion, captions, documents and the third-party parts of the site (maps, booking, payment, chat).
2. Report: every issue, in plain language.
You get a written report you keep.
For each issue it says where it is, who it blocks, how serious it is, which criterion it relates to, and how to fix it.
Issues that repeat across a template are grouped, so you see the real size of the work.
The report opens with the totals: how many issues the site has and how many errors, by severity.
Then it goes through them one by one.
Severity is practical: “blocks a task” (someone cannot finish), “makes it hard” and “minor”.
Blocking issues come first in every plan.
3. Quote: one clear price, based on what we found.
The quote is personal.
It is based on the report and the size of your site, and it states one clear price, the scope, the timeline and the payment terms.
If you want us to keep the site accessible after future updates, ongoing monitoring can be part of it.
4. Fix: in the code, template by template.
We fix the code itself, not a layer on top: the cause, not the symptom.
A missing label in a form component is fixed once in the component, and every page that uses it is fixed with it.
Every change is logged, and it stays in your code. Typical work includes:
- Headings, landmarks and a logical reading order.
- Text alternatives for images and icons, and empty links or buttons given real names.
- Form labels, required fields, clear error messages and error summaries.
- Keyboard access, visible focus and dialogs that trap and return focus correctly.
- Color contrast, text resizing, reflow on small screens and touch target size.
- A way to pause anything that moves, and respect for the “reduce motion” setting.
Most of the time the site looks the same afterwards.
Where a design choice itself is the barrier (say, light grey text on white), we propose the smallest change that passes and agree it with you first.
Drag, or use the arrow keys, to compare.
Before: a sample page with barriers. After: the same sample page, fixed in code.
The parts that are easy to forget.
Documents and PDFs
Documents such as PDFs on your site are part of its content, so WCAG applies to them too, and the forms customers use to get your service have to work for them whatever their age.
We fix the source file where we can, or convert it to an accessible page.
Video
Recorded videos need captions: it is a level A success criterion in WCAG (1.2.2), and video that carries information also needs a text or audio alternative.
We add captions and transcripts, and check that the player itself works with a keyboard. WCAG 2.1
Maps, booking, payment and chat
Content that other companies supply still reaches your customers through your site.
A booking or payment widget that is part of how customers get your service is something they have to be able to use.
We test each one, fix what we can reach, and where a vendor’s component is the problem we tell you plainly and suggest an accessible alternative.
5. Re-test, then the accessibility statement.
When the fixes are in, we run the full audit again and give you an updated report with your site’s score and the number of remaining errors, a before-and-after summary, and a dated log of the fixes.
Anything left open is listed honestly, with the reason.
At delivery, our commitment applies to every page in your report.
Then we draft your accessibility statement.
In the US a statement is not a named legal requirement, but it gives customers a clear way to reach you: it says what was made accessible, the standard you work to, and how to report a problem or ask for an accessible version.
6. After launch: updates are where accessibility breaks.
A new page, a plugin update, a theme change or a new campaign banner can quietly bring barriers back.
The law looks at your site as it is today, not as it was on the day of the audit.
If you choose ongoing monitoring, we re-scan on a schedule, re-test the key journeys, fix regressions, and keep your statement current.
If someone reports a barrier, act on it quickly: fix it, and in the meantime offer that person another way to get the service.
A prompt, documented response is part of taking accessibility seriously.
What we need from you, and what we don’t do.
Very little. We do the work; you give us three things:
- Access to the site: admin access to your CMS or code, ideally with a staging copy.
- Someone who can answer content questions, for example what an image is meant to say.
- The names of the third-party services on the site (booking, payment, chat, maps).
We are not lawyers and this is not legal advice.
Nobody can honestly promise that a site is immune to claims: sites change, standards are interpreted, and third-party parts are outside anyone’s full control.
What we do commit to is in writing: our commitment at delivery, with its scope next to it.