Quality & delivery · E.ON Next

Making accessibility routine instead of an expensive yearly audit

saved versus traditional audit-led testing
£10,000s
WCAG 2.1 conformance as a product requirement, not an afterthought
AA

The situation

E.ON Next needed its app to meet WCAG 2.1 AA, the accessibility standard, as a core product requirement rather than a compliance afterthought.

The problem

  • The default approach, commissioning full-journey audits over and over, was slow, expensive, and found issues after they were built.
  • A third-party accessibility toolbar was on the table: cheap, visible, and a way of signalling 'accessibility handled' without fixing the underlying issues.

What I did

  • Onboarded a specialist accessibility team and defined the operating model, including how the work was priced.
  • Moved testing down to component level, so issues were caught once, early, instead of rediscovered in every journey that used the component.
  • Held the line against the toolbar shortcut, and steered the organisation toward accessibility built into how it designs and ships: automated and manual checks in the build pipeline, with remediation in the code.
Accessibility isn't an audit you buy. It's a discipline you build into how you ship.

Contact

Got a problem like this?

A few lines is enough. Every enquiry comes straight to me, and you’ll get a considered reply: a straight answer, a question or two, or an honest “I’m not the right fit”.

Prefer email? hello@firstniyyah.com