Skip to content

Odduel

We put the odds in your favour

Insights

European Accessibility Act: what it means for your website

Whether the European Accessibility Act applies to your website, who owns which part of the work, where to start, how to measure it and what to ask your agency.

A developer tests a website using only the keyboard, with a screen magnifier and notes on a desk

The European Accessibility Act requires websites that deliver certain consumer services in the EU, above all online shopping, consumer banking, e-books, passenger transport and communications services, to be accessible to people with disabilities since 28 June 2025. For a business, that turns accessibility from a good intention into a product requirement that touches design, content, code, third-party tools, contracts and the information you publish. This guide explains how to tell whether your website is in scope, who in the business owns what, how to plan the work and how to keep the site accessible after the first fixes.

Last updated: 9 November 2026.

What is the European Accessibility Act?

The European Accessibility Act is an EU directive that sets shared accessibility requirements for selected products and services sold to consumers across the single market. Its legal text is Directive (EU) 2019/882, and its requirements apply from 28 June 2025. Each member state has written it into national law, so the obligations sit in your own country’s legislation as well as in the Directive.

For websites, the Act works through services. If your website is the channel through which consumers use a covered service, the website must meet the accessibility requirements. It does not cover every website on the internet.

At Odduel, a creative and technology agency in Barcelona and São Paulo, accessibility is planned into every site in our website development service, from the first wireframe to the last release check.

In short: the European Accessibility Act covers websites that deliver services such as e-commerce, consumer banking, e-books, passenger transport and communications to consumers. In-scope sites must be perceivable, operable, understandable and robust, which in practice means meeting the harmonised standard based on WCAG. Confirm scope, audit, fix key journeys, adapt your process and contracts, and publish the required accessibility information.

Does the European Accessibility Act apply to your website?

Most businesses can answer this with four questions.

  1. Do you sell to consumers? The Act is about services for consumers. A website that only serves business buyers is generally outside its scope, though many B2B sites also sell to individuals.
  2. Does your website deliver a covered service? The main ones for websites are e-commerce (selling products or services online to consumers), consumer banking, e-books, electronic communications, access to audiovisual media, and elements of air, bus, rail and waterborne passenger transport.
  3. Are you a microenterprise? Microenterprises that provide services, as defined in the Directive, are exempt from the service requirements. Check the definition carefully: it depends on headcount and financial thresholds.
  4. Are you a public body? Public sector websites follow a separate law, the Web Accessibility Directive, rather than this Act.
Website typeLikely position under the EAANote
Online store selling to consumersIn scopeThe whole buying journey matters, from search to payment
Booking site for consumer servicesOften in scopeDepends on whether booking counts as an e-commerce service in your case
Consumer banking websiteIn scopeCovers sign-in, account and payment journeys
Transport operator websiteIn scope for covered elementsTicketing, booking and travel information
Brochure site with no online salesUsually outsideAccessibility remains good practice and widens your audience
B2B-only portalUsually outsideCheck whether any consumers use it
Public sector websiteSeparate lawWeb Accessibility Directive applies
How common website types are likely to be treated under the European Accessibility Act

This table is a starting point, not legal advice. Edge cases are common, and national laws may add details, so confirm your position with a legal adviser in your main market.

Does the EAA apply to apps?

Yes. The Act explicitly includes services delivered through mobile applications, so an app that delivers a covered service is in scope just like the website. Our article on app accessibility under the European Accessibility Act covers the app side in detail.

What does the European Accessibility Act involve in practice?

The Directive sets functional requirements: information must be perceivable, operable, understandable and robust, and the service must work with assistive technologies such as screen readers, magnifiers and voice control. Businesses meet them by following the harmonised standard EN 301 549, whose web criteria come from the W3C Web Content Accessibility Guidelines.

For a business owner, the practical work falls into six areas.

AreaWhat it coversWho usually owns it
DesignContrast, layout at large text sizes, focus visibility, touch targets, error statesDesigners and the agency
ContentHeadings, link text, alt text, plain language, captions, accessible PDFsMarketing and content editors
CodeSemantic HTML, keyboard support, labels, landmarks, ARIA used correctlyDevelopers
Third-party toolsCookie banners, chat widgets, payment forms, maps, booking enginesDevelopers, with suppliers
InformationAccessibility information for users, as the Directive requiresLegal, product and the website owner
ProcessTesting in each release, training, feedback channel, fixing reported issuesProduct owner or digital lead
The six areas of website accessibility work and who usually owns them

The detailed criteria for each are explained in our guide to website accessibility and what the European Accessibility Act asks. This article focuses on how a business organises the work.

Why do third-party tools matter so much?

A site can be built carefully and still fail because of one widget. Cookie banners that trap keyboard focus, chat windows that screen readers cannot reach, embedded payment fields without labels and booking engines with inaccessible date pickers are common blockers. You remain responsible for the service even when a supplier provides part of it, so ask each supplier for their accessibility conformance information and test their components inside your site.

Where should a company start?

A clear sequence turns the Act into a manageable project.

  1. Confirm scope. Use the questions above and get legal confirmation for edge cases.
  2. Name an owner. One person accountable for accessibility across the website, with authority to prioritise fixes.
  3. Audit the site. Combine automated testing with manual checks: keyboard only, screen reader, zoom to large text, contrast and forms.
  4. List key journeys. Search, product page, basket, checkout, sign-in, account, contact and any booking flow.
  5. Fix by severity. First anything that blocks a key journey completely, then serious difficulties, then minor issues.
  6. Fix at the source. Repair templates, components and the design system rather than individual pages.
  7. Review suppliers and contracts. Add accessibility requirements to contracts with agencies, platforms and widget providers.
  8. Publish accessibility information. Explain how the service meets the requirements, as the Directive asks of service providers, usually in an accessibility statement linked from every page.
  9. Train content editors. Most new barriers come from everyday content: images without alt text, vague links, inaccessible PDFs.

If you are about to commission a new site, put these requirements in your website brief from the start; accessibility built in costs far less than accessibility added later.

How do you measure whether it works?

Accessibility is measured in two ways: conformance with the standard and real usability.

  • Conformance audits against EN 301 549 and WCAG, at launch and at least once a year, plus after major changes.
  • Automated monitoring to catch regressions such as missing alt text or labels between audits.
  • Release testing of key journeys with keyboard and screen reader before each significant release.
  • User testing with people who use assistive technologies, which reveals problems that audits miss.
  • Feedback through a clear contact route in the accessibility statement, with a target time to respond and fix.

Useful indicators for management include open issues by severity, the share of key journeys passing manual tests and the average time to fix reported barriers.

What happens if a website does not comply?

Each member state enforces the Act through its own market surveillance authorities, which can check services, require corrective action and apply penalties set in national law. The details differ by country. Beyond enforcement, inaccessible websites lose customers who cannot complete purchases, generate avoidable support requests and can damage reputation. Accessible sites also tend to be clearer for everyone, including people on small screens or in bright sunlight.

What should you ask your agency or developer?

  1. Which standard will you design and test against?
  2. How do you test: automated tools, keyboard, screen readers, real users?
  3. How will you check third-party components such as payment, booking and cookie tools?
  4. Will our content editors be trained to keep pages accessible?
  5. Will you help us write the accessibility statement and set up a feedback route?
  6. How will accessibility be kept in each future release?

Questions people ask

Does the European Accessibility Act apply to my website?

It applies if your website delivers a covered service to consumers, such as e-commerce, consumer banking, e-books, passenger transport or electronic communications, and you are not a microenterprise as defined in the Directive. Brochure sites without online sales and B2B-only portals are usually outside, but check edge cases with a legal adviser.

Does the EAA apply to apps?

Yes. The European Accessibility Act explicitly includes services delivered through mobile applications. If an app is how consumers access a covered service, such as shopping, banking or travel booking, it must meet the same accessibility requirements as the website, including support for screen readers, scalable text and accessible controls.

Where should a company start with the European Accessibility Act?

Start by confirming whether your website is in scope, then name one owner and audit the site with automated and manual tests. Fix barriers on key journeys such as search, checkout and sign-in first, repair shared templates, review suppliers, publish accessibility information and train content editors.

Which standard should a website meet under the EAA?

Businesses generally follow EN 301 549, the harmonised European standard for digital accessibility. Its web requirements draw on the W3C Web Content Accessibility Guidelines. Meeting the harmonised standard gives a presumption of conformity with the corresponding requirements of the Act, which makes it the practical benchmark for audits and development.

How do you measure website accessibility?

Combine a conformance audit against EN 301 549 and WCAG with automated monitoring, release testing of key journeys using keyboard and screen readers, and testing with people who use assistive technologies. Track open issues by severity, the share of journeys that pass manual tests and how quickly reported barriers are fixed.

Start with the scope questions and an audit of your key journeys; they show the size of the task. If you want a website designed and built to be accessible from the start, read more about our website development service or contact us. This article is general information, not legal advice.

More articles

More from our Insights.

Explore all insights

Get in touch

Let’s change your odds.

Odds do not change on their own. If you have something to build, launch or fix, tell us about it and we will show you how we would approach it.

    Need an NDA before you share details? Start a project

    Chat with us