Two pieces landed on my desk this week that, read together, tell an important story about accessibility. One looks back at the first year of the European Accessibility Act. The other looks at what happens to accessibility when AI makes us build websites faster than ever. If you run a business with customers in Europe, or you are a designer using AI tools, both are worth your time.

What happened in year one of the EAA

The European Accessibility Act came into force in June 2025. It sets shared accessibility rules across the EU for things like online shops, banking and e-books. On 12 November, the London accessibility consultancy TetraLogical published a review of the Act’s first year, and a few points stood out to me.

  • It is about your customers, not your address. The Act applies based on where your customers are, not where your company is based. So a UK business selling to people in France or Ireland can’t simply assume it’s out of scope.
  • Courts are looking at real use. In France, the supermarket chain Carrefour argued that its site met 71% of the national standard. The court gave it six months to fix things anyway. As the article puts it, the case was about “whether people could use the site, not whether the company had worked hard”.
  • The bar has gone up. In September 2026, the standard the Act points to moved from WCAG 2.1 to WCAG 2.2, adding nine more success criteria.
  • Very small firms are exempt. Businesses with fewer than 10 staff and turnover under 2 million euros are excluded, though I would never treat that as a reason to ignore accessibility.

Meanwhile, AI is speeding up the build

On 17 November, Smashing Magazine published an article by Andrew Chung of Level Access (it’s a sponsored piece, so bear that in mind when he mentions his company’s tools). He cites survey figures showing far more teams say AI has sped up their design and development than say it has sped up testing. His summary is that testing practices “haven’t kept up”.

He also points to a WebAIM scan of the top million home pages, which found that automatically detected accessibility errors per page rose by around 10% in a year. WebAIM suggested AI-assisted coding may be one of the reasons. That worries me. Faster isn’t better if it means more people can’t book, buy or sign up.

His suggested fix is sensible: don’t add a big new step at the end, but build human checks into the work as it happens. Spell out accessibility details at handoff, run automated checks on every change, have a person actually test with a keyboard, and add a test for each fix so the problem can’t quietly come back.

Why it matters for small businesses

Put these two stories together and you get a clear message. The rules are being enforced on whether real people can use your website. At the same time, the tools many of us now use to build websites can quietly make them harder to use. A site can look lovely in a demo and still be impossible to use with a keyboard or a screen reader.

Accessibility is also just good business. The same changes that help disabled visitors usually help everyone: clearer labels, readable text, bigger buttons, forms that explain what went wrong.

A practical checklist

Here’s what I would do if I were reviewing a small business website this month:

  • Try it with only a keyboard. Press Tab through your homepage, contact form and checkout. Can you always see where you are, and can you finish the task?
  • Check your contrast. Pale grey text on white looks stylish but is hard for many people to read.
  • Look at your forms. Every field needs a visible label, and error messages should say what to fix.
  • Ask your web designer about WCAG 2.2. If they look blank, that’s useful information.
  • If you use AI to build or edit pages, test the output. Run a free automated checker, then have a real person try the key journeys.

Designers, the lesson for us is to bake accessibility into our components and our AI prompts, so the fast path is also the accessible one. Speed is great. Leaving people behind isn’t.