For years, website accessibility was treated by many businesses as optional: a nice idea, something to get to eventually. That’s changing. Accessibility laws in many countries now cover websites and apps, and the European Accessibility Act, which applies from 28 June 2025, extends requirements to many private businesses selling to consumers in the European Union, including online stores.
Even if your business isn’t in the EU, these changes matter. If you sell to EU customers, the rules may apply to you. And accessibility laws elsewhere, along with growing awareness, mean that accessible websites are increasingly expected everywhere.
Here’s what the European Accessibility Act means for websites, how to write a useful accessibility statement and how to make real progress on a WordPress site. As always with legal topics, this is practical guidance, not legal advice. Check your specific obligations with a qualified adviser.
Why accessibility matters
Accessible websites work for people with a wide range of abilities, including those who:
- Use screen readers because they’re blind or have low vision.
- Navigate with a keyboard or switch devices because of motor impairments.
- Need captions because they’re deaf or hard of hearing.
- Benefit from clear language and consistent layouts because of cognitive disabilities.
- Zoom in, increase text size or use high contrast settings.
A large share of people live with some form of disability, and many more experience temporary or situational limitations, like a broken arm, bright sunlight on a phone screen or a noisy environment. Accessibility improvements usually make sites better for everyone.
What the European Accessibility Act is
The European Accessibility Act is an EU directive setting accessibility requirements for a range of products and services. Each member state implements it in national law. It covers services including:
- E-commerce services, meaning websites and apps selling products or services to consumers.
- Consumer banking services.
- Electronic communications and some transport services.
- E-books and dedicated reading software.
For many businesses, the e-commerce category is the most relevant. If you sell to consumers in the EU through a website or app, your online shop may need to meet the accessibility requirements.
Who’s exempt
Microenterprises providing services, generally businesses with fewer than 10 employees and annual turnover or balance sheet total not exceeding 2 million euros, are exempt from the service requirements. Other exemptions may apply where requirements would impose a disproportionate burden, though these need to be justified and documented. Rules and enforcement details vary by country.
What standard applies
The Act sets functional requirements rather than naming a specific technical standard in the text itself. In practice, the harmonised European standard for ICT accessibility, EN 301 549, is the reference, and for web content it aligns with WCAG 2.1 level AA. WCAG 2.2, the latest version, builds on 2.1 with additional criteria, so aiming for WCAG 2.2 AA is a sensible target.
What an accessibility statement is
An accessibility statement is a public page explaining how accessible your website is, what you’re doing to improve it and how people can get help. Under the European Accessibility Act, service providers need to provide information about how their services meet accessibility requirements, and an accessibility statement is a common way to do that. Public sector bodies in the EU and UK have had specific accessibility statement requirements for some time.
Even where not strictly required, a good statement shows commitment, sets honest expectations and gives users a way to report problems.
What to include
A useful accessibility statement typically covers:
Commitment
A short statement of your commitment to accessibility and the standard you aim for, such as WCAG 2.2 level AA.
Conformance status
An honest summary: fully conformant, partially conformant or not conformant. Most sites are partially conformant. Being honest is better than claiming full compliance you can’t support.
Known limitations
List known accessibility issues, like older PDF documents that aren’t fully accessible, embedded third-party content you don’t control or specific features still being improved. Explain workarounds and timelines where possible.
Measures taken
Describe what you do to support accessibility: testing methods, staff training, accessibility in your design and development process and regular audits.
Feedback and contact
Provide clear ways for people to report problems or request content in alternative formats: an email address, phone number and form. Commit to a response time.
Enforcement information
Where relevant, mention how users can escalate complaints to the appropriate authority in their country.
Date
When the statement was prepared and last reviewed. Review it regularly, at least annually and after major changes.
Keep the statement in plain language, and link to it from your site footer.
Making real progress on a WordPress site
A statement is only meaningful if you’re actually improving accessibility. Here’s how I approach it for WordPress sites.
Step 1: Audit
Combine automated and manual testing:
- Automated tools catch issues like missing alt text, low contrast, missing form labels and empty links. They typically find only a portion of accessibility problems.
- Keyboard testing: navigate the whole site using only the keyboard. Can you reach every link, button and form field? Is focus visible? Can you open and close menus and dialogs?
- Screen reader testing: use free screen readers like NVDA or VoiceOver on key pages and flows.
- Zoom and reflow: check pages at 200 percent zoom and on narrow screens.
- Key journeys: test the paths that matter most, like browsing products, adding to cart, checkout, contact forms and account login.
For larger stores or high-risk sites, a professional accessibility audit gives a thorough, documented assessment.
Step 2: Prioritise
Fix issues that block people from completing key tasks first: checkout problems, inaccessible forms, keyboard traps and missing labels on essential controls. Then move to less critical issues.
Step 3: Fix the theme and templates
Many accessibility issues come from the theme: missing skip links, poor heading structure, low contrast colours, inaccessible menus and removed focus styles. Fixing them in templates fixes them across every page.
Check that your theme:
- Has a skip to content link.
- Uses semantic landmarks, like header, nav, main and footer.
- Has accessible, keyboard-operable navigation menus.
- Keeps visible focus styles.
- Meets colour contrast requirements.
- Uses headings logically.
Step 4: Review plugins
Plugins often introduce barriers: sliders, pop-ups, form builders, cookie banners and chat widgets. Test them, configure them for accessibility, ask vendors about accessibility support and replace problem plugins where needed.
Step 5: Train content editors
Editors create much of a site’s content. Train them to:
- Write meaningful alt text.
- Use headings in order.
- Write descriptive link text.
- Avoid conveying information through colour alone.
- Add captions to videos.
- Create accessible documents, or provide accessible alternatives to PDFs.
Step 6: Build accessibility into your process
Accessibility isn’t a one-time project. Include it in design reviews, development testing and content publishing. Test after major changes, theme updates and new features.
Avoid accessibility overlays
Accessibility overlay widgets claim to make sites compliant automatically. They don’t fix underlying code problems, and many disabled users find them unhelpful or obstructive. Regulators and accessibility experts generally don’t consider overlays a substitute for real accessibility. Invest in fixing your site instead.
WooCommerce stores and the EAA
For online stores selling to EU consumers, key areas include:
- Accessible product pages, with alt text, clear structure and accessible variation selectors.
- Accessible cart and checkout, including form labels, error messages and payment steps.
- Accessible account areas and order information.
- Accessible information about products and services, including terms and policies.
- Support channels that people with disabilities can use.
The block-based WooCommerce checkout has been developed with accessibility in mind, but customisations, themes and extensions can introduce problems, so test your actual checkout.
Frequently asked questions
Does the European Accessibility Act apply to my website?
If you provide e-commerce services to consumers in the EU and aren’t a microenterprise, it may apply. Check national implementation rules and get advice for your situation.
Do I need an accessibility statement?
Public sector bodies in many countries must have one. Under the European Accessibility Act, service providers must provide accessibility information, and a statement is a common way to do it. It’s good practice for all sites.
Which WCAG level should I aim for?
WCAG 2.1 level AA is the common legal reference in Europe. Aiming for WCAG 2.2 AA covers it and adds newer criteria.
Can an accessibility plugin make my site compliant?
Some plugins help with specific fixes, but no plugin or overlay can make a site compliant automatically. Real accessibility requires fixing themes, content and functionality.
Final thoughts
Accessibility is becoming a legal expectation as well as the right thing to do. Understand whether the European Accessibility Act and similar laws apply to you, aim for WCAG 2.2 AA, audit your WordPress site with automated and manual testing, fix barriers in key journeys first, improve your theme and plugins, train editors and publish an honest accessibility statement with a clear way to get help. Progress, documented and continuous, matters more than perfection.




