Accessibility (ADA/WCAG)
audited by a human.
Audits and remediation that make the product usable for everyone and defensible on paper.
- — You have received an accessibility complaint or legal letter
- — Public-sector or enterprise procurement is asking for a VPAT
- — Your site is unusable with a keyboard alone
The work should
change the numbers.
Around one in five people has a disability that affects how they use software. Long before it is a legal question, accessibility is the difference between a site that serves your whole market and one that quietly excludes a fifth of it.
Automated tools find roughly a third of real issues. The rest need a human with a keyboard and a screen reader, which is why our audits are manual first and tooling second. Findings come prioritised by user impact, not by how easy they are to close.
We remediate as well as report, and we train your team, because an audit that produces a PDF and no change is an expense rather than an improvement.
What the engagement
actually contains.
Manual audit against WCAG 2.2 AA
Keyboard, focus order, screen-reader and zoom testing across your key journeys.
Assistive technology testing
NVDA, VoiceOver and TalkBack passes on the flows that carry your conversions.
Prioritised remediation plan
Findings ranked by user impact and effort, mapped to specific components rather than pages.
Implementation of fixes
Semantic markup, ARIA where genuinely needed, focus management and accessible form patterns.
Automated regression gates
Axe checks in CI so closed issues stay closed as the product changes.
Team training and statement
A working session for designers and developers, plus a published accessibility statement.
- Audit report mapped to WCAG 2.2 AA criteria
- Prioritised remediation backlog
- Implemented component-level fixes
- Axe checks wired into CI
- Accessibility statement for publication
- Training session and internal guidance
- You have received an accessibility complaint or legal letter
- Public-sector or enterprise procurement is asking for a VPAT
- Your site is unusable with a keyboard alone
- An overlay widget was installed and nothing actually improved
What usually went wrong
before we were called.
- 01Installing an overlay widget and believing the problem is solved
- 02Auditing page by page instead of grouping findings by component
- 03Prioritising quick wins over the issues that block a task entirely
- 04Closing issues with no CI check, so they return within two releases
- WCAG 2.2 AA criteria passed
- Keyboard-only completion of key journeys
- Automated violations in CI
- Accessibility complaints received
1–2 weeks audit, 2–4 weeks remediation for a marketing site
What week one
actually looks like.
A manual pass with keyboard and screen reader across your key journeys. Findings arrive grouped by component rather than by page, which is what makes remediation finishable.
- Staging or production access
- A list of the journeys that matter most
- Design system or component library access
- A developer contact for fixes
- Legal advice or certification
- Remediating third-party embeds we do not control
- Producing captions or transcripts
- VPAT authoring, unless scoped
Scope boundaries stated up front rather than discovered in a change request.
Four stages, visible throughout.
Assess
A baseline across performance, security, accessibility and dependency risk, with findings ranked by consequence.
Stabilise
The urgent items closed first: exposed surfaces, failing checks, missing backups, unpatched dependencies.
Automate
Budgets, scans and alerts moved into CI and monitoring, so regressions are caught by machines rather than customers.
Review
A quarterly session on what changed, what is drifting and what deserves next quarter’s attention.
Where this has paid off.
Turning complexity into a category leader.
A new website and patient portal made a specialist healthcare network easier to choose, understand and trust.
A site everyone could actually use.
An accessibility-led rebuild and performance overhaul gave a public-interest organisation the reach its work deserved.
Accessibility (ADA/WCAG), answered.
No, not for the problems that matter. They cannot fix a bad heading structure, an unlabelled form field or a keyboard trap, and disability advocacy groups have consistently opposed them. Fixing the underlying markup is the only approach that holds up in practice or in court.
WCAG 2.2 Level AA. It is the level referenced by the European Accessibility Act, UK public-sector regulations and most ADA settlements, and it is achievable without compromising design.
A marketing site is typically two to four weeks of engineering after the audit, because most findings are component-level and fixing one component fixes it everywhere. Complex applications take longer and are best staged by journey.
QA & testing
Manual and automated coverage that finds the failure before your customers volunteer to.
UI/UX design
Product-focused design: flows, states and interfaces judged on whether the job gets done.
Web development
Custom, WordPress and Shopify builds for teams who need a site that sells, not just one that exists.
Website & app maintenance
Ongoing updates, monitoring and a senior person to reach when something needs deciding.
Make accessibility (ada/wcag) useful.
Bring us the hard thing. We will bring a point of view, a senior team and a clear next step.