Skip to article
The Design Office of Nick Sloggett
WorkWritingExperimentsResumeEmail
Back
Note·Jun ’25·3 min read

Accessibility just became a ship gate

The European Accessibility Act applies from June 28, 2025. What it covers, what standard it points to, and why design teams should fix components first.

Typeface

The European Accessibility Act has applied since Saturday, June 28. If you sell a covered digital product or service to people in the EU, accessibility is now a legal requirement, enforced by each member state.

What does the European Accessibility Act cover?

The directive covers products and services most people use every day:

  • Products: consumer computers and their operating systems, phones, e-readers, and self-service terminals such as ATMs, ticket machines and check-in kiosks.
  • Services: e-commerce, consumer banking, e-books, electronic communications, access to audiovisual media, and parts of air, bus, rail and ferry passenger transport, including their websites and apps.

Microenterprises providing services, meaning fewer than 10 staff and no more than €2 million in turnover, are exempt. There are transition periods: service contracts agreed before June 28 can run unchanged for up to five years, and self-service terminals already in use can stay for up to 20 years. Penalties are set country by country. Germany’s law, for example, allows fines of up to €100,000.

What standard does it point to?

Not one designed for the act, yet. A harmonised standard written for the EAA is still being revised. In practice, teams are working to EN 301 549, the European standard already used for public-sector sites, which follows WCAG 2.1 at levels A and AA. If your product meets WCAG 2.1 AA, you’re working to the benchmark most teams are using.

Why components first

Most accessibility work I’ve seen is done screen by screen, after launch, from an audit spreadsheet. It never finishes, because every new screen brings the same problems back.

The work that lasts lives in the components: the button that always has a name, the text field that always has a label and an error read aloud, the color pair that always passes contrast, the focus order that always follows the reading order. Fix those once and every screen built from them inherits the fix.

At Apple I designed the Abbott Patient Controller, an iPhone app that people with neurostimulation implants use to adjust their therapy. They live with Parkinson’s disease, essential tremor or chronic pain, and they open it on a bad day, sometimes with a tremor. So each screen has one main action in large type, and at the maximum the increase button dims where it is instead of moving, so nothing under the thumb shifts. A control that’s hard to read or hard to hit there isn’t a polish issue. It decides whether someone can manage their own treatment.

The EAA makes that frame a legal one. The person who has the hardest time with your interface is now a user you’re required to serve.

What to do this week

  1. Find out whether your product is in scope, and in which countries you sell.
  2. Audit your component library against WCAG 2.1 AA before auditing screens.
  3. Write an accessibility statement that says honestly where you stand.
  4. Add accessibility checks to the definition of done, so new work doesn’t add debt.
Previous← An eval asks if it’s good. An experiment asks if it helped.NextArc published its novelty tax →

© 2026 Nick Sloggett

EmailLinkedIn (opens in new tab)ResumeRSS