The European Accessibility Act (EAA) has applied in EU member states since 28 June 2025. It covers certain consumer-facing digital services, including online shops, and exempts microenterprises providing services. If you sell to EU consumers, plan for WCAG-level accessibility, an accessibility statement, and fixes to your theme, forms and images.
What the European Accessibility Act is
The EAA is Directive (EU) 2019/882. It sets accessibility requirements for a defined list of products and services so that people with disabilities can use them. Member states had to transpose it into national law by June 2022, and the rules apply from 28 June 2025. You can read the overview on the European Commission's EAA page.
For WordPress owners, the relevant part is digital services offered to consumers. An online shop, a booking system, or a site that sells subscriptions is the typical case. A brochure site for a business that sells nothing online is less clear-cut, and the research I worked from did not settle whether a purely personal, non-commercial blog is in scope. Check your national law or ask a lawyer if you are in that grey area.
The Act is a directive, so each country wrote its own law. That is why you will see different names, fine levels and enforcement bodies depending on where you operate. The technical goal is the same everywhere: people using screen readers, keyboards, magnification or voice control must be able to use your service.
Who must comply, including outside the EU
The obligation follows the customer, not your office address. One source states that it applies to websites and digital services sold to consumers in any EU member state, regardless of where the business is headquartered. If you run a WooCommerce store in the UK or the US and ship to EU customers, treat the Act as relevant to you.
The main exemption is size. Services provided by a microenterprise are exempt, according to the European Disability Forum. Check the legal definition of a microenterprise in the country you serve, because it depends on headcount and turnover, and I cannot confirm those thresholds here.
Freelancers and agencies should think about it from two sides:
- Your own site: if you sell services online to consumers, you may be a service provider yourself.
- Client sites: clients who run shops or booking tools will ask you whether the theme and forms are compliant. Writing accessibility into the scope avoids disputes later.
If you are unsure whether you are in scope, building to WCAG 2.2 AA anyway is a safe default. It also improves usability for everyone, and much of it overlaps with good SEO practice.
Germany: the BFSG
Germany implemented the Act through the Barrierefreiheitsstärkungsgesetz (BFSG), which took effect on 28 June 2025, as Bird & Bird reports. It is the law that German-facing shops and service providers are measured against.
Two details matter in practice. First, existing service contracts concluded before 28 June 2025 can remain unchanged until they end, but no later than 27 June 2030. That is a transition rule for contracts, not a general pause for your website. Second, enforcement is developing. The market surveillance authority published its enforcement strategy in January 2026, and some sources say the first fine proceedings began in the first quarter of 2026. Another source says no fines had been imposed as of April 2026. Treat that as unresolved.
Fine figures also vary by source. Some sources report a substantial maximum fine for Germany, and one secondary source reports a fine level in the Netherlands from 1 January 2026. Verify the exact amounts against the national laws before quoting them to a client. The safer message is that penalties exist, differ by country, and enforcement is picking up.
What WCAG 2.2 AA means in practice
The EAA itself does not name a specific standard in the text most sources summarize. Countries and market authorities point to the harmonized standard EN 301 549, which the Commission asked European standards bodies to revise. Sources disagree on the exact version of WCAG that applies: some cite WCAG 2.1 AA, and one claims a move to WCAG 2.2 that I could not confirm officially.
The practical answer is to build to WCAG 2.2 AA. It includes everything in 2.1 AA, so you will satisfy either reading. AA is the middle conformance level, and it is the one most regulators expect.
In plain terms, WCAG is organized around four ideas:
- Perceivable: text alternatives for images, enough color contrast, captions for video.
- Operable: everything works with a keyboard, focus is visible, targets are not too small.
- Understandable: clear labels, predictable navigation, helpful error messages.
- Robust: valid, semantic markup that assistive technology can read.
For a deeper walk-through, see the WordPress accessibility guide on WCAG 2.2 and the EAA.
Checklist for themes, forms and images
Use this table as a working audit. It covers the areas most WordPress sites get wrong, and each item maps to a WCAG principle.
| Area | Check | Why it matters |
|---|---|---|
| Theme | Skip link to main content works | Keyboard users avoid tabbing through the menu |
| Theme | Visible focus outline on links and buttons | Keyboard users see where they are |
| Theme | Heading order is logical (one H1, then H2, H3) | Screen reader users navigate by headings |
| Theme | Text contrast meets AA (4.5:1 for normal text) | Low-vision readability |
| Theme | Menus and modals work with keyboard only | No keyboard traps |
| Forms | Every field has a visible, associated label | Placeholders alone disappear and are not reliable labels |
| Forms | Errors are described in text, not color alone | Clear correction path |
| Forms | Required fields are marked in text | Predictable completion |
| Images | Meaningful images have descriptive alt text | Screen readers read it |
| Images | Decorative images use empty alt | Avoids noise |
| Images | Text is not baked into images | Cannot be resized or read aloud |
WCAG 2.2 also added requirements such as larger minimum target sizes and rules that stop focused elements being hidden behind sticky headers. Test your sticky menus and cookie banners for that second point. Check the full success criteria in the official WCAG text before certifying anything, since I am summarizing rather than quoting them.
Images and alt text in WordPress
Images are the easiest area to fix and the most common failure. In the media library, each image has an alt text field. Write what the image communicates in context, not a keyword list. A product photo needs the product name and key attribute; a chart needs its main finding; a purely decorative flourish gets an empty alt.
Optimizing images for speed does not conflict with accessibility, but check that your workflow keeps alt text intact when files are converted or replaced. Our guide on alt text, file names and size covers the writing side, and the Erdo Image Optimizer is a free plugin for compressing and converting images when you handle the performance side.
Also review sliders and hero banners. If a headline lives only inside a JPEG, move it into real text. If a video autoplays, give users a way to pause it.
Statement, testing and a sensible plan
Service providers must publish information on how their service meets the requirements, usually as an accessibility statement, according to Halfaccessible. Put it in the footer, describe the standard you test against, list known gaps, and give a contact address for reporting barriers.
A realistic plan looks like this:
- Audit key journeys first: homepage, product page, cart, checkout, contact form.
- Run an automated scan, then test manually with keyboard only and a screen reader. Automated tools catch only part of the issues.
- Fix the theme-level problems, since they affect every page.
- Publish the statement and set a review date.
- Re-test after theme, plugin or builder updates.
In short, treat accessibility as maintenance, not a one-off project. The key takeaway for agencies is to put it in the contract: define the target (WCAG 2.2 AA), the pages tested, and who is responsible after launch. If you also deal with other EU rules, compare it with the EU Cyber Resilience Act guide.


