Skip to content

Technology

· 1 min read

Why we build accessibility in first

A portrait of Daniel Okonkwo

Written by

Treating accessibility as a pass at the end is how it becomes expensive. Built in from the first commit, it is mostly free.

Accessibility work has a reputation for being slow and expensive, and when it is bolted on at the end it deserves that reputation. The cost is not in the requirements themselves. It is in unpicking decisions that were made without them.

The cost curve is the whole argument

A button that should have been a button costs nothing on the day it is written. The same fix three months later means finding every place that div was copied, re-testing the keyboard path through each, and explaining to a client why a finished feature is being reopened.

A keyboard focus ring visible on a form control
A focus ring that survives the design, rather than one removed by it.

What we do on day one

  1. Real elements. Anything clickable is a button or a link, never a div with a handler.
  2. A visible focus ring that is part of the design rather than something the design removes.
  3. Colour is never the only thing carrying meaning.
  4. Reduced motion respected globally, not per component.
An audit report on a laptop screen showing passing checks
The audit nobody had to schedule a fortnight of remediation for.
Our audit came back with nothing to fix, which has never happened before.
Daniel Okonkwo, CTO, Meridian Transit

That is the whole trick, and it is not really a trick. Decide once, at the start, that the work is for everyone, and the expensive version of this conversation never happens.