Accessibility

Accessibility for the organisations we work with — governments, regulators, healthcare bodies, public-facing platforms — is statutory, not aspirational. WCAG 2.1 AA in the UK under the Equality Act. WCAG 2.2 AA increasingly required across Australian government. Section 508 / ADA patterns in US-facing work. We've been delivering accessible software for these audiences for 20 years and offer accessibility as a discrete service where the brief calls for it.

What we ship

Accessibility audits — full WCAG 2.1 or 2.2 AA audit against the target standard, with categorised findings, severity ratings, and a prioritised remediation plan.
Remediation work — fixing existing sites, with editor-side training so the content team doesn't reintroduce issues after handover.
Accessibility-first new builds — greenfield projects where accessibility is baked into the editor experience, the design system, and the CI pipeline.
Independent accessibility statements — for sites that need to publish compliance under government regulation.
Ongoing accessibility partnership — automated checks in CI plus periodic manual reviews so compliance doesn't quietly drift after launch.

How we test

Automated checks in CI on every commit — axe-core and Lighthouse — with serious or critical violations blocking merge. Manual assistive-technology testing before release: VoiceOver on macOS / iOS, NVDA and JAWS on Windows, TalkBack on Android. Keyboard-only navigation testing for every interactive flow. Periodic external audits for organisations whose compliance status is publicly published (their accessibility statement gets independently signed off rather than self-declared).

Where this work has landed

Most of our flagship case studies depend on accessibility being right. The HM Land Registry 1862 Register upgrade was independently audited to WCAG 2.2 AA before launch. The NSW Digital Design System reference build is accessibility-first by construction. The Law Enforcement Conduct Commission's publications search is accessibility-compliant including faceted filtering. Justice Health NSW serves an audience where accessibility isn't a compliance checkbox — it's the entire reason the platform exists. The Multicultural Health Communication Service handles language-specific accessibility markup (the lang attribute, voice-of-document, right-to-left scripts) that most multilingual builds quietly get wrong.

Accessibility as a transversal capability

Accessibility is also baked into every other offering on this page. The headless-CMS migration service includes a baseline WCAG audit. The multilingual platform service handles the language-and-accessibility intersection. The Plone editor we run for government clients enforces semantic content structure at authoring time so editors can't accidentally produce inaccessible HTML. Accessibility-as-a-standalone-service is for the cases where there's an existing site that needs to reach compliance, or where the audience makes accessibility the entire point — not just a defensible checkbox.