Websites
European Accessibility Act: what small-business websites must fix
Who the European Accessibility Act covers, which micro-enterprises are exempt, what an online shop must fix, and how to decide between repairing and rebuilding.
The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025. For small businesses, the key question is whether you sell to consumers online. If your website or app lets consumers buy, book or sign a contract, it counts as an e-commerce service and must be perceivable, operable, understandable and robust for people with disabilities, including the checkout, login and payment steps. The main exception: micro-enterprises providing services, defined as fewer than 10 employees and annual turnover or balance sheet total of no more than EUR 2 million, are exempt from the service requirements. Everyone else needs an accessible site, a public statement explaining how it meets the requirements, and a process to keep it that way.
This is a practical summary, not legal advice. The directive is enforced through each member state's national law, which can add detail and sets the penalties.
Who is covered
The directive lists the services it covers, including consumer banking, e-books, passenger transport services, electronic communications and e-commerce services. For most small businesses, e-commerce is the one that matters. The directive defines e-commerce services as services provided at a distance, through websites and mobile apps, by electronic means and at the individual request of a consumer, with a view to concluding a consumer contract.
In practice:
- An online shop selling to consumers is covered.
- Online booking or ordering that ends in a consumer contract (a hotel, a course, a paid appointment) is very likely covered.
- A brochure website that only presents your business, with a contact form and no way to buy or book, generally falls outside the e-commerce definition. National laws or other rules may still apply, so check before assuming.
- Business-to-business sales only are outside the consumer definition, which covers people buying for purposes outside their trade or profession.
The directive covers services offered to consumers in the EU, so a non-EU company selling to EU consumers should expect the same rules.
The micro-enterprise exemption
The directive states that micro-enterprises providing services are exempt from the service accessibility requirements and the related obligations. A micro-enterprise employs fewer than 10 people and has an annual turnover not exceeding EUR 2 million, or an annual balance sheet total not exceeding EUR 2 million.
Three cautions:
- The exemption is for services. Micro-enterprises that manufacture, import or distribute covered products (such as computers, phones or e-readers) don't get the same exemption, only lighter documentation duties.
- Growth ends it. A business that crosses the threshold needs to comply from then on, so plan the next site rebuild with accessibility built in.
- Customers don't check your headcount. People with disabilities, older customers and anyone on a small phone screen benefit from an accessible shop. An exempt business can still lose sales to an unusable checkout.
Member states must also provide guidelines and tools to help micro-enterprises apply the rules.
What the law asks of a covered website
The directive's general requirements for services include making websites and mobile apps accessible "in a consistent and adequate way by making them perceivable, operable, understandable and robust". Those four words come from the Web Content Accessibility Guidelines (WCAG), which is how accessibility is measured in practice. The W3C lists WCAG 2.2 as the relevant standard for the Act; the EU's public-sector rules rely on EN 301 549, which includes WCAG 2.1 level AA. Aiming for WCAG 2.2 level AA covers both.
For e-commerce specifically, the directive adds three requirements:
- provide accessibility information about the products and services you sell, when the producer supplies it
- make identification, security and payment functions accessible when they are part of your service
- make identification methods, electronic signatures and payment services perceivable, operable, understandable and robust
Service providers must also publish information, in their general terms and conditions or an equivalent document, describing the service in accessible formats and explaining how it meets the accessibility requirements. This is usually published as an accessibility statement linked from the footer and referenced in the terms.
The small-business checklist
These are the issues that most often block real customers, and the ones to fix first.
Navigation and structure
- Every function works with a keyboard alone, with a visible focus indicator
- Headings follow a logical order, and each page has a meaningful title
- Menus, filters and pop-ups can be opened and closed without a mouse
- No keyboard traps in chat widgets, cookie banners or modals
Content
- Text contrast meets WCAG minimums, including on buttons and over images
- Text can be enlarged to 200% without breaking the layout
- Images that carry information have useful alternative text; decorative images are hidden from screen readers
- Videos made or updated after June 2025 have captions
- Links say where they go ("View delivery options", not "Click here")
Forms and checkout
- Every field has a visible label, not only placeholder text
- Errors are explained in text, next to the field, and not only by colour
- Time limits can be extended
- The payment step, including any third-party payment page you control or choose, works with a keyboard and a screen reader
- CAPTCHA has an accessible alternative
Product information
- Product descriptions include the accessibility information producers supply
- Size guides, comparison tables and image galleries work without a mouse
Documentation
- An accessibility statement explaining how the service meets the requirements, with a contact for problems
- Information in your terms and conditions as Annex V of the directive requires
- A record of any "disproportionate burden" assessment if you rely on that exception
Exceptions and transition periods
- Disproportionate burden: a business may rely on this exception only after assessing it against the criteria in the directive, documenting it and renewing it at least every five years. A business that receives funding meant for accessibility can't rely on it.
- Old content: pre-recorded video and office files published before 28 June 2025, archived content not updated after that date, and third-party content you don't fund or control are excluded.
- Contracts and products in use: service contracts agreed before 28 June 2025 can continue unchanged until they expire, for no more than five years, and products already used to deliver a service may continue to be used until 28 June 2030.
These exceptions don't cover your current shop pages, checkout or new content.
Don't read silence as compliance either. AccessibleEU, the Commission-backed resource centre, noted in September 2026 that people who hit barriers usually leave or switch to a competitor rather than complain, and that "a lack of complaints should never be taken as evidence that a digital service is accessible."
Fix or rebuild
The right choice depends on the site, not the law.
Fixing usually makes sense when:
- the site runs on a maintained platform with an accessible theme or a theme that can be corrected
- the problems are mainly content: alt text, headings, link text, contrast in a few places
- the checkout and payment provider are already accessible
Rebuilding usually makes sense when:
- the theme or custom code is the source of the problems (inaccessible menus, sliders, filters, forms)
- the site is old and due for a redesign anyway
- you'd be paying to fix templates you plan to replace within a year
What drives the cost either way: the number of templates (not pages), custom components, the checkout and any third-party plugins, the volume of images and video needing text alternatives and captions, and whether you need testing with assistive technology. An audit against WCAG on a sample of key templates and the full checkout is the cheapest way to get a reliable estimate before deciding.
Avoid "accessibility overlay" widgets sold as a one-line fix. They add a toolbar but don't repair the underlying code, and they can interfere with the assistive technology people already use.
How PNE fits in
PNE Solutions designs and builds websites with accessibility planned in from the first template, and can audit an existing shop to tell you whether repair or a rebuild is the better spend. We build sites in several languages, which matters when your customers are spread across EU markets.
Sources
- European Accessibility Act (EAA) — European Commission
- Directive (EU) 2019/882 on the accessibility requirements for products and services, full text — legislation.gov.uk
- Directive (EU) 2019/882, Article 4: Accessibility requirements — legislation.gov.uk
- Directive (EU) 2019/882, Article 31: Transposition — legislation.gov.uk
- European Union web accessibility laws and policies — W3C Web Accessibility Initiative
- Why accessibility complaints remain rare despite widespread digital barriers — AccessibleEU