The European Accessibility Act: What UK Businesses Must Do Now

Most conversations about website accessibility have been about doing the right thing. That argument is sound and it has been available for twenty years, which tells you how persuasive it has been on its own. The European Accessibility Act changes the conversation, because from June 2026 it is enforceable, and the people it applies to include a large number of UK businesses who have not realised it yet.

Why this matters now

The European Accessibility Act is EU law designed to give consumers, including disabled consumers, equal access to goods and services. It covers online shops, banking, transport, e-books, smartphones and payment terminals. Individual member states transposed it into national law, and enforcement began in June 2026 with monitoring authorities expected to increase their auditing activity across the rest of the year.

The part UK businesses keep missing is the jurisdictional test. The EAA is not scoped by where your company is registered. It is scoped by where your customers are. If you sell to consumers in the EU, you are within scope, and Brexit provides no exemption whatsoever. A Manchester business shipping to Dublin, an agency retaining clients in Amsterdam, a training provider selling course access to someone in Madrid: all in scope.

There is a genuine exemption, but it is narrower than people hope. Microenterprises, defined as fewer than ten employees and under two million euro in annual turnover, have limited relief. If you are above either of those thresholds, you comply. A fifteen-person firm turning over a million pounds is not a microenterprise for these purposes, and a great many UK service businesses sit exactly in that gap.

The consequences of non-compliance are the usual mix: fines, restrictions on operating in a market, and the commercial cost of losing business you did not know you were disqualified from. That last one is the underrated risk. Procurement processes increasingly ask about accessibility conformance, and an honest negative answer removes you from consideration before any human reads your proposal.

None of this is an argument for panic. It is an argument for finding out where you stand, which most businesses have not done, and which takes about a day.

Common mistakes to avoid

Accessibility attracts a specific class of mistake: confident action that achieves nothing. These are the ones that cost real money without improving anything.

Installing an accessibility overlay widget. The floating icon that offers font resizing and contrast toggles does not make a site conformant, and disability advocacy organisations have been consistently critical of them. Several thousand US lawsuits have been filed against sites that had an overlay installed at the time. You are buying the appearance of compliance.
Treating an automated scan as the finish line. Automated tools reliably catch about a third of WCAG issues. They are excellent at missing contrast and absent alt text, and they cannot assess whether your alt text is meaningful, whether your focus order makes sense, or whether your error messages are comprehensible.
Assuming your website platform handles it. Platforms provide accessible components. What you build with them is your responsibility, and the most common failures live in custom work: a bespoke booking flow, a carousel, a modal that traps focus.
Fixing the homepage and stopping. Conformance applies to the journey a customer actually takes. A perfect homepage leading to an unusable checkout fails, and the checkout is where the legal exposure concentrates.
Aiming at WCAG 2.2 because it is newer. EN 301 549 currently incorporates WCAG 2.1 Level AA, and that is the harmonised benchmark. Targeting 2.2 is not wrong, but do not let the newer standard delay conformance with the one that is actually operative.

The subtler mistake is treating this as a one-off remediation project. A site that conforms today and ships an inaccessible booking form in November is non-conformant in November. Accessibility is a property of your release process, not a certificate you obtain once. Building the check into how you ship changes is cheaper than an annual audit and far more effective.

If you want the commercial case rather than the legal one, we covered that separately in accessibility as a competitive advantage. Both arguments point at the same work. This one just has a deadline attached.

Quick Strategic Tip

Unplug your mouse and try to complete your own enquiry form using only the keyboard. Tab through it, fill it in, submit it. If you get stuck, lost, or cannot see which field you are on, you have found a real conformance failure in under two minutes, and you have found it the way an actual user would.

Step-by-step compliance plan

This sequence takes a small team roughly six weeks. It is ordered by legal exposure and user impact, so if you stop early you have still fixed the things that matter most.

Determine whether you are in scope, and write the answer down. Do you sell to consumers in the EU? Are you above the microenterprise threshold on either headcount or turnover? Record the reasoning and the date. If you are ever asked, a documented assessment is far better than a recollection.
Identify your critical journeys. Not your whole site. The specific paths a customer takes to give you money or make an enquiry: homepage to service page to contact form, or product to basket to checkout. Conformance effort concentrates here because this is where exclusion becomes commercial harm.
Run an automated scan as a baseline. Use any reputable free checker on those journeys. This gives you the mechanical failures cheaply: missing alt text, insufficient contrast, unlabelled form fields, missing page language. Fix everything it finds before spending money on anything else.
Do the keyboard pass. Navigate each critical journey using only Tab, Shift+Tab, Enter and Space. You are checking three things: that you can reach everything interactive, that you can always see where you are, and that focus never gets trapped. This single test catches more real-world failures than any tool.
Check your colours properly. Body text needs a contrast ratio of at least 4.5 to 1 against its background, large text 3 to 1. Brand palettes are a frequent offender here, particularly light greys and mid-tone brand colours used for links. If your palette fails, this is a design decision that needs making once and applying everywhere.
Fix forms and error handling. Every input needs a programmatically associated label, not just placeholder text. Errors must be described in text, identify the specific field, and explain how to fix the problem. Colour alone cannot indicate an error.
Test with a screen reader. VoiceOver is built into macOS and iOS, NVDA is free on Windows. You do not need expertise. Turn it on, close your eyes, and try to complete your enquiry form. What you learn in twenty minutes will reshape your priority list.
Write an accessibility statement and publish it. State your conformance level, list known issues honestly, give a contact route for accessibility problems, and date it. An honest statement documenting known gaps and a remediation timetable is a materially better position than silence.
Build the check into your release process. Add keyboard navigation and contrast to whatever review you do before shipping changes. This is the step that stops you paying for the same audit again next year.
Re-test the critical journeys quarterly. Sites drift. A quarterly pass on the paths that matter is enough to catch regressions before they become exposure.

Six weeks is realistic for a typical brochure or small commerce site. A complex application takes longer, and the honest answer is that you should start with the critical journeys and accept that full conformance is a programme rather than a sprint. Partial progress that is documented and improving is a defensible position. Doing nothing is not.

Conformance checklist

Run this against each critical journey. Every item maps to a WCAG 2.1 Level AA requirement.

Every image conveying information has meaningful alt text. Decorative images have empty alt attributes.
Body text meets 4.5 to 1 contrast, large text meets 3 to 1.
Every interactive element is reachable and operable by keyboard alone.
The focus indicator is always visible and never removed by CSS.
Every form input has a properly associated label, not a placeholder standing in for one.
Error messages identify the field and explain the fix in text.
Headings are in a logical order and describe the content beneath them.
The page has a language attribute set.
Video has captions. Audio has a transcript.
Nothing conveys meaning through colour alone.
The site is usable at 200% zoom without horizontal scrolling.
An accessibility statement is published and dated.

How to measure progress

Accessibility resists a single headline number, and any tool offering you a percentage score is simplifying something that does not simplify well. Measure it as coverage and trajectory instead.

Track issues by severity, not by count. One keyboard trap in your checkout matters more than forty missing alt attributes on decorative images. Categorise each finding as blocking, serious or minor, and drive the blocking count to zero before anything else.

Measure journey coverage. What percentage of your critical journeys have been through a keyboard pass and a screen reader pass? This is the number that reflects genuine risk reduction, and it is the one to report.

Log accessibility contacts. Once your statement is published you will occasionally hear from users. Every one of those is free, high-quality testing from someone with direct experience. Track them, respond to them, and fix what they raise.

Watch form completion rates. Accessibility fixes frequently improve conversion for everyone, because clearer labels and better error handling help all users. If your enquiry form completion rate rises after remediation, that is not a coincidence. Our piece on why contact forms get ignored covers the same ground from the conversion side.

Key terms in plain English

EAA: The European Accessibility Act. EU legislation requiring specified products and services to be accessible, enforceable from June 2026.

EN 301 549: The European harmonised standard for accessibility. It incorporates WCAG 2.1 Level AA and is the benchmark that presumes conformance.

WCAG: The Web Content Accessibility Guidelines. The international technical standard, organised into levels A, AA and AAA. AA is the legal target.

Microenterprise: Fewer than ten employees and under two million euro annual turnover. Limited exemptions apply. Exceed either threshold and you are in scope.

Screen reader: Software that reads page content aloud, used by blind and low-vision users. VoiceOver and NVDA are the common ones and both are free.

Focus indicator: The visible outline showing which element the keyboard is currently on. Frequently removed by designers who consider it ugly, which is a conformance failure.

Accessibility statement: A published page setting out your conformance level, known issues and contact route. Required in practice and useful in principle.

Conclusion and next move

The EAA has turned a twenty-year ethical argument into an operational requirement with a date attached. For most UK businesses selling into the EU, the honest position today is that they do not know whether they conform, which is a worse place to be than knowing you do not.

Spend one day this week finding out. Confirm your scope in writing, run an automated scan on your enquiry journey, and do the keyboard test. Those three things cost nothing and will tell you whether you have a small tidying job or a genuine programme of work. Either answer is more useful than the uncertainty you have now.