Our ServicesPlatform & Support

Website accessibility audits and WCAG compliance remediation

Roughly one in six people lives with a significant disability, and most inaccessible websites lock them out through small, fixable things: unlabelled buttons, invisible focus states, text over images at 2:1 contrast, forms that only work with a mouse. We audit against WCAG 2.2 AA, fix the code, and show you how to keep it accessible as content changes.

What You Get

Included as standard on every engagement — not an upsell list.

Audit against WCAG 2.2 level AA

Automated scanning finds perhaps a third of real issues, so we combine it with manual testing: full keyboard-only navigation, screen reader passes, 200 percent zoom and reflow at 320 pixels, colour contrast measurement, and motion and animation review against reduce-motion preferences.

Prioritised remediation plan

Every finding is recorded with the failing WCAG success criterion, the affected pages or components, the severity in terms of who is blocked, the recommended fix and a realistic effort estimate — so you can sequence the work rather than face an undifferentiated list of hundreds of items.

Code-level fixes, not an overlay

We fix the markup: semantic landmarks and heading order, correct form labels and error associations, accessible names on icon-only controls, ARIA used only where native HTML cannot do the job, visible focus indicators, and skip links that actually move focus.

Keyboard and focus management

Every interactive element reachable and operable by keyboard in a logical order, no keyboard traps, focus moved deliberately when a drawer or modal opens and returned when it closes, and dropdowns, accordions, carousels and tabs rebuilt to the expected interaction patterns.

Colour, contrast and typography repair

Text and interface contrast measured and corrected to at least 4.5:1 for body copy and 3:1 for large text and interface components, colour never used as the only carrier of meaning, and type sizing and spacing that survive zoom and user stylesheet overrides.

Multilingual and RTL accessibility

Correct lang attributes per page and per inline language change, proper dir handling and mirrored layouts for right-to-left content, and reading-order checks. Our Hebrew RTL e-learning work and German, Polish, Dutch and Norwegian builds mean this is a routine part of how we work.

Accessibility statement and editor training

A published accessibility statement documenting your conformance level, known limitations and contact route, plus practical guidance for whoever edits the site on writing alt text, meaningful link text, structured headings and accessible PDFs.

How We Deliver It

Stage by stage, with the approval points marked. Accessibility & Compliance follows the same rhythm on every project.

  1. Scope the audit

    We select a representative sample: homepage, key templates, the main conversion path, forms, and any custom interactive components. Auditing every page is wasteful when most issues live in shared templates and repeat everywhere.

  2. Test automatically and manually

    Axe and Lighthouse runs establish the machine-detectable baseline, then a human works through keyboard-only navigation, screen reader output, zoom and reflow, contrast measurement and focus behaviour to find what tools cannot detect.

  3. Report and prioritise

    Findings are documented with criterion references, screenshots, reproduction steps and recommended fixes, grouped into critical blockers, serious barriers and refinements, so remediation starts where it removes the most harm.

  4. Remediate

    We implement the fixes in your templates and components — most repairs live in shared code and clear many pages at once — retesting each item as it is closed rather than leaving verification to the end.

  5. Verify and maintain

    A retest confirms closure, the accessibility statement is published, and we agree an ongoing rhythm: checks after significant releases, editor guidance, and periodic reviews as WCAG and platform behaviour evolve.

What You Receive

The concrete artefacts handed over at the end — files, access and documentation you keep.

  • WCAG 2.2 AA audit report with criterion-level findings
  • Prioritised remediation backlog with severity and effort estimates
  • Keyboard navigation and screen reader test notes
  • Colour contrast analysis with corrected palette values
  • Implemented code fixes across templates and components
  • Accessible form patterns with correct labels and error handling
  • Published accessibility statement for your site
  • Editor guidance covering alt text, headings and link text
  • Post-remediation verification report

Ideal for

If two or three of these sound like your situation, this is the right place to start.

  • You sell to public sector, education or enterprise buyers who ask for conformance
  • You have received an accessibility complaint or legal notice
  • Someone installed an overlay widget and you suspect it is not enough
  • Your site is being redesigned and you want accessibility built in, not retrofitted
  • You ship in multiple languages, including right-to-left content
  • Your forms or booking flow cannot be completed without a mouse

Tools we use

Standard, portable tooling. The licences, accounts and source stay in your name, so nothing here is a reason you cannot leave.

  • WCAG 2.2
  • WAI-ARIA
  • axe DevTools
  • Lighthouse
  • NVDA
  • VoiceOver
  • WordPress
  • Breakdance
  • React
  • Next.js
  • WPML
  • Figma

Live projects where this work did the heavy lifting:

Frequently Asked Questions

The questions we get asked most about Accessibility & Compliance.

No, and disability advocacy groups have been consistent about that for years. Overlays sit on top of broken markup and guess at intent; they cannot invent a meaningful alt text or fix a form field with no label. They frequently interfere with the assistive technology a user has already configured, and they have not prevented legal claims. We fix the underlying code, which is the only durable answer.
WCAG 2.2 level AA is the practical target and the level referenced by most legislation, including the European Accessibility Act, the EN 301 549 procurement standard, and interpretations of the ADA and UK Equality Act. Level A alone is too low to be meaningful and AAA is not realistic across a whole site. We audit against AA and note AAA items where they are cheap wins.
The audit typically takes one to two weeks depending on how many unique templates and custom components exist. Remediation depends on the findings: a well-built WordPress site usually needs one to three weeks because most fixes sit in shared templates and propagate everywhere. A site built on a page builder with heavy custom widgets, or one with bespoke interactive components, takes longer.
Mostly not. Visible focus indicators appear, some text or button colours shift to reach contrast thresholds, and occasionally a font size or line height increases. Those changes are small and can be designed to fit your brand rather than imposed as browser defaults. Accessible design is generally clearer design, and the same fixes usually improve conversion for everyone, not only assistive technology users.
That is the part most projects miss, because accessibility decays with every new page an editor publishes. We include editor guidance on alt text, heading structure and link wording, build accessible patterns into your component library so new pages inherit them, and can add accessibility checks to maintenance releases so regressions are caught while they are still one page rather than fifty.

Ready to start on Accessibility & Compliance?

Send us the brief — or just the problem. You will get a written scope, a timeline and a fixed price, usually within one working day.