Short answer: the European Accessibility Act has applied since 28 June 2025 to businesses selling certain products and services to consumers in the EU, including online shops and booking services. In practice, your website and checkout should meet WCAG 2.1 level AA, the standard behind the EU's technical requirements. Microenterprises that provide services, meaning fewer than 10 staff and no more than €2 million in annual turnover or balance sheet, are exempt from the service requirements. UK businesses are covered when they sell to EU consumers.
I am not a lawyer, and this is not legal advice. If you sell into the EU at any real volume, check your position with a specialist. What I can tell you is what the work looks like on a WordPress or WooCommerce site, because most of it is ordinary good practice that should have been done anyway.
Who does the European Accessibility Act cover?
The Act, Directive (EU) 2019/882, covers a defined list of products and services sold to consumers. For most small businesses, the relevant ones are e-commerce, online booking for transport, banking services, e-books and some communications services. A brochure site that only describes your services is in a greyer area than a shop or booking system that customers complete a purchase through.
Does it apply to UK businesses after Brexit?
Where you sell matters, not where you are based. A UK shop that ships to customers in Ireland, France or Germany is providing an e-commerce service to EU consumers. Separately, UK businesses already have duties under the Equality Act 2010 to make reasonable adjustments, so accessibility work pays off on both sides of the Channel.
What does "accessible" mean in practice?
The yardstick is WCAG 2.1 level AA. Stripped of jargon, it asks whether people can use your site if they cannot see well, cannot use a mouse, use a screen reader, or need more time. The checklist below covers where WordPress sites most often fall short.
A practical European Accessibility Act checklist for WordPress and WooCommerce
1. Test with a keyboard
Put the mouse away and try to use your site with Tab, Shift+Tab and Enter. Can you reach the menu, open the dropdown, fill in the contact form and complete checkout? Can you always see where you are on the page? A visible focus outline is one of the most commonly removed and most important features.
2. Check colour contrast
Light grey text on white and white text on pale brand colours are the usual culprits. Body text needs a contrast ratio of at least 4.5:1 with its background. Free contrast checkers will tell you in seconds.
3. Fix forms
Every field needs a proper label, not just placeholder text that disappears when you type. Error messages should say what went wrong and how to fix it, in text, not only by turning a box red.
4. Describe images and media
Meaningful images need alt text that says what they show. Decorative ones should have empty alt text so screen readers skip them. Videos need captions.
5. Check headings and structure
One H1 per page, then headings in order. Screen reader users jump between headings the way sighted users scan, so a page built from styled paragraphs instead of real headings is hard to navigate. Page builders make this mistake easy.
6. Look hard at checkout and booking
These are the flows the Act cares about most. Test the whole journey with a keyboard and a screen reader, including address lookups, payment fields and any pop-ups. Third-party payment widgets are part of your checkout even if you did not build them.
7. Publish an accessibility statement
Say which standard you aim to meet, what you know does not yet comply, and how people can contact you if they hit a barrier. Then keep it up to date.
Do accessibility overlay plugins solve it?
No. Overlay tools that add a toolbar or claim to fix everything automatically do not repair the underlying code, and many disabled users find them get in the way. Automated scanners are useful for finding obvious problems, but they miss a large share of real issues, which is why the keyboard and screen reader testing above matters. Fix the site itself.
Overlay, scan-and-patch or proper remediation?
ApproachWhat it doesOur view Overlay pluginAdds a widget on top of the existing siteDoes not fix the code; avoid relying on it Automated scan and quick fixesFinds and fixes obvious issues like contrast and missing alt textA useful start, not the finish Manual audit and remediationTests real journeys with keyboard and screen reader, fixes templatesThe approach that actually meets the standard
Does accessibility help SEO?
Indirectly, yes. Clear headings, descriptive link text, alt text and fast, stable pages help search engines understand your content as much as they help people. Good design and accessibility also overlap heavily with conversion, which we touch on in the psychology of UI and UX for conversions.
How to plan European Accessibility Act work on a small budget
Most small businesses cannot fix everything at once, and they do not need to. The sensible order is to start where a barrier stops someone from buying or booking, then work outwards.
Start with the money pages
Your checkout, booking form, contact form and product pages matter more than your blog archive. If a keyboard user cannot complete a purchase, that is the problem a complaint will focus on, and it is lost revenue whether or not anyone complains. Test these journeys first and fix whatever blocks them.
Fix templates, not individual pages
On WordPress, most issues live in the theme or page templates: missing form labels, low-contrast buttons, focus outlines removed by a designer years ago. Fixing the template repairs every page that uses it, which is why proper remediation often costs less than people fear.
Train whoever adds content
Accessibility slips back the moment someone uploads an image without alt text or uses bold text instead of a heading. A short session for the people who edit the site, covering alt text, headings, link wording and video captions, stops the work being undone.
Keep a simple record
Write down what you tested, when, what you found and what you fixed. If a customer or regulator ever asks, a dated record of reasonable effort counts for a lot, and it makes the next review quicker. The W3C's WCAG overview is the reference to test against.
None of this needs a new website. For most SMEs selling into the EU, the European Accessibility Act is met through a focused audit, a round of template fixes and a habit of checking new content. The businesses that struggle are the ones that wait for a complaint before starting.
Questions businesses ask us
Are microenterprises completely exempt?
Microenterprises providing services are exempt from the service requirements. The exemption does not cover products in the same way, and national rules can vary, so check if you are close to the thresholds or growing fast.
What happens if a site does not comply?
Enforcement is handled by each EU country, and penalties vary between them. The more practical risk for a small shop is losing customers who cannot complete a purchase.
Do I need to rebuild my site?
Usually not. Most fixes are in templates, forms, colours and content. A site built with heavy page builder layouts may need more work on structure, which is one of the reasons we cover builder clean-ups in our page builder speed guide.
How often should we re-check?
Whenever you change templates, forms or checkout, and at least once a year. New content added without alt text or proper headings slowly undoes the work.
Need an audit?
Accessibility fixes are part of how we approach small business website development and UI and UX design. If you sell into the EU and want to know where your site stands, send us the URL through the contact page.
