01
Accessibility fixes
A scan gives you a list. This is the part that comes after it: someone works through the list, changes the markup, the CSS and the templates, tests the result with a keyboard and a screen reader, and writes down both what was fixed and what still needs a person.
Start a briefAsk a question first
Want to know how bad it is before you talk to anyone? AccessibilityBrief is our own checker and it will do one page of your site free, no account. Bring the report with you.
What you actually receive
- An audit of your site against WCAG 2.2 A and AA — automated checks across the site, then a manual pass over the pages that matter.
- The fixes themselves, in your theme, templates and plugins, delivered as a pull request or on staging for you to review.
- Keyboard and screen reader testing on the paths that earn money: navigation, forms, checkout.
- A written report: every issue, the criterion it breaks, what we changed, and what we could not.
- An accessibility statement that says what is true about your site, with the known gaps named.
- A rescan afterwards, so the before and the after are both on record.
What a scan can settle, and what it cannot
Automated checks are cheap and fast, and on their own they are weak evidence. Knowing which half of the problem you are looking at is most of this job.
- A tool settles
- Contrast ratios, images with no alternative text, fields with no label, heading order, ARIA used where it is not allowed. Thousands of elements in seconds, with no argument about the result.
- A person settles
- Whether the alternative text says the right thing, whether the focus order follows the page, whether an error message tells you how to recover, whether a custom menu behaves the way a screen reader user expects it to.
- Be wary of
- Any tool or agency quoting a precise share of WCAG that automation covers. It depends on the site and on how you count, and a confident percentage is a sales device.
- So the work runs
- Scan, fix what the scan is right about, then walk the paths that earn money by keyboard and by screen reader. The second half is where the complaints come from.
What this is not
- We do not install an overlay or an accessibility widget. They sit on top of the problem and leave it where it was.
- We will not call your site compliant, certified or guaranteed. Conformance is a claim you make about your own site, and anyone promising it in a sales page is selling you the wrong thing.
- We do not hand over a PDF of problems and leave. The deliverable is changed code.
- Typical duration
- 1 to 4 weeks
- Starts with
- A fixed-price audit
- Engagement
- Audit first, then fixes by scope
- Proof of approach
- Both our accessibility tools are ours
Four stages, start to handover
- 01
A brief, then a conversation
You send four short answers. We read them and reply within one working day, either with questions or with a straight answer about whether we are the right studio for it.
- 02
Scope written down
What is being built, what is not, what it costs and when. If we cannot describe it clearly enough to price it, that is a sign the scope is not ready — and we will say so.
- 03
Build, in the open
Work lands in your repository from the first week. You see progress as commits and working previews, not as a status meeting.
- 04
Handover that survives us
Documentation for the next developer, the accounts in your name, and a walkthrough with whoever has to run it. Then a support window while you settle in.
Ready when you are.
Four short questions, about two minutes. A reply within one working day.