Accessibility usually shows up in a project plan as a line near the end: “accessibility audit,” scheduled somewhere between QA and launch. It’s a well-meant instinct: make sure nothing’s been missed before it goes live. It’s also exactly the wrong point in the process to be asking the question for the first time.

What an audit at the end can actually fix

A pre-launch accessibility audit is good at catching things like missing alt text, poor colour contrast, or a form field without a label. These are real issues, worth fixing. But by that point, the interaction design is finished. If the actual problem is a custom dropdown that can’t be operated by keyboard, or a multi-step flow that’s confusing for a screen-reader user because of how it’s structured, an end-of-project audit can only really document the problem, not solve it without reopening design decisions that were supposed to be closed.

What we do differently

Accessibility gets treated as a design constraint from the first prototype, not a compliance pass at the end:

  • Keyboard and focus behaviour designed in from the start: every interactive element gets a visible, deliberate focus state as it’s built, not retrofitted later. It’s a small detail, but it’s the difference between a site that’s usable without a mouse and one that only looks like it is.
  • Colour and contrast checked at the point colours are chosen, not after a brand palette is locked in and suddenly hard to adjust.
  • Structure that makes sense out loud: heading order, landmark regions and reading order get checked the way a screen-reader user would actually experience them, while the structure is still easy to change.
  • Automated scanning as a safety net, not a strategy: tools like axe-core catch what’s measurable, but they can’t tell you whether a flow makes sense; that still takes a human check.

Why this matters even if you’re not required to comply with anything

Most accessibility problems that get caught late are also just usability problems for everyone: an unclear focus state, a confusing tab order, low contrast text in bright daylight. Building it in from the start avoids an awkward pre-launch scramble, and it tends to produce a better product for every user, including the ones an audit is designed to protect.

Building something new and want accessibility handled properly from day one, not bolted on at the end? Get in touch.

← Back to all insights