European Accessibility Act: A Developer’s Guide to Web Accessibility Requirements

Direct answer: The European Accessibility Act (EAA), Directive (EU) 2019/882, does not impose one universal accessibility rule on every website. It applies to specified products and services, including e-commerce and certain passenger-transport, banking, electronic-communications, audiovisual-media, and e-book services. Its measures have applied since 28 June 2025. Whether a particular website is covered depends on what service it provides and the national law implementing the Directive.

If your service is covered, treat accessibility as a property of the complete service: information, interface, navigation, and the functions people need to complete tasks. For e-commerce, that includes identification, security, and payment. Start by checking the relevant Member State’s implementing law and the exact service category before turning requirements into engineering work.

Does the European Accessibility Act apply to my website?

Ask what the website or mobile service does for consumers, rather than relying on the operator’s industry label. The EAA covers named product and service categories. A site that supports a covered service may be in scope even if its operator primarily describes itself as a technology company.

The Directive defines an e-commerce service as a service provided at a distance through a website or mobile service, by electronic means, at a consumer’s individual request, with a view to concluding a consumer contract. Its recitals clarify that the accessibility obligations cover online sales of any product or service. A site that enables consumers to buy online is therefore an important scope case to assess.

Area	Examples named by the Directive	Developer’s first scope question
E-commerce	Online sales of products or services that enable a consumer contract	Can a consumer use this site or mobile service to conclude a contract?
Passenger transport	Specified elements of passenger transport, including related digital services	Which transport mode and service element are involved? Special rules apply to urban, suburban, and regional transport.
Banking	Consumer banking services	Does the digital journey provide a covered consumer banking service?
Electronic communications	Electronic communications services	Is the service itself within the Directive’s category?
Audiovisual media	Access to audiovisual media services	Does the interface provide access to a covered service?
E-books	E-books and dedicated software	Is the product or software within the specified category?
Other specified products and services	Consumer general-purpose computer hardware and operating systems, certain self-service terminals and consumer communications or audiovisual terminal equipment, e-readers, and answering emergency communications to 112	Is the product or service expressly covered, and which requirements apply to this part?

This is a screening aid, not a legal conclusion. In particular, do not assume every transit website is covered in the same way: the transport provisions have qualifications, including a distinct rule for urban, suburban, and regional transport. Check the Directive and national implementing legislation for the activity and jurisdiction at issue. The [text of Directive (EU) 2019/882 on EUR-Lex](https://eur-lex.europa.eu/eli/dir/2019/882/oj) is the primary source.

When did the EAA take effect?

Member States were required to transpose the Directive into national law by 28 June 2022. They apply the resulting measures from 28 June 2025. The EAA also includes transitional arrangements. Some products already used to provide services may continue to be used during a transition, and certain transitions may run to 28 June 2030. Some self-service terminals may remain in use until the end of their economically useful life, subject to the Directive’s limit.

These dates do not tell you which national authority enforces the rules, what local procedure applies, or whether a particular transition covers your deployment. Verify those details in the relevant Member State’s law rather than treating an EU-wide summary as country-specific advice. The Commission-hosted [AccessibleEU guide](https://accessible-eu-centre.ec.europa.eu/content-corner/digital-library_en) also advises checking national rules.

What do developers need to change?

For covered services, Annex I addresses accessible information about the service and its accessibility features. Service websites, related online applications, and mobile services must be accessible in a consistent and adequate way. The statutory outcomes are commonly expressed through four principles: perceivable, operable, understandable, and robust.

Perceivable: Present information and interface components in ways users can perceive.
Operable: Make controls, navigation, and tasks usable through available interaction methods.
Understandable: Make information and operation understandable.
Robust: Ensure content works with a variety of user agents, including assistive technologies.

These principles apply to the service’s real tasks, not just its landing page. Review the complete journey: account creation, sign-in, search, product or service selection, forms, confirmation, error recovery, and support. Which journeys matter depends on the service you provide.

E-commerce requires attention to the transaction

For covered e-commerce services, the requirements include accessible identification, security, and payment functionality. If the responsible operator supplies information about goods or services, the e-commerce provisions address the accessibility of that information as well. Include authentication challenges, security prompts, payment fields, and confirmation steps in your review; an accessible catalogue followed by an unusable checkout does not make the whole task accessible.

Build accessibility into the service itself

Fix issues in the interface and underlying implementation. The European Commission says accessibility overlays or other tools that do not ensure the website itself meets detailed criteria are not an appropriate solution, and recommends fixing issues at source. It also recommends involving people with disabilities in testing. An automated scan can help find some defects, but it cannot by itself establish that every legal requirement is met.

For a practical engineering plan, map each important user task to the four principles, identify the relevant requirements in the applicable law and technical standard, and assign owners for remediation and retesting. Include people with disabilities in usability and assistive-technology testing. This workflow is an implementation aid, not a substitute for a complete legal assessment.

Is WCAG or EN 301 549 required?

The Directive sets accessibility outcomes and provides for technical standards. The European Commission identifies EN 301 549 v3.2.1 as the technical-criteria standard underpinning EU legal accessibility requirements. Under Article 15, conformity with a harmonised standard whose reference has been published in the Official Journal creates a presumption of conformity only to the extent that the standard covers the relevant requirements.

That is not a blanket safe harbour. Before relying on a standard, verify the currently applicable edition and its Official Journal reference, identify which legal requirements it covers, and check the national implementation relevant to your service. Do not describe a particular checklist, WCAG version, automated scan, or conformance report as a complete legal determination without that analysis. The Commission’s [web accessibility policy](https://digital-strategy.ec.europa.eu/en/policies/web-accessibility) explains the relationship between standards and EU accessibility policy.

What is excluded, and what exemptions may apply?

The Directive has content-specific exclusions and limited exemptions. Establish whether a provision applies to the particular content or service; an exclusion from one requirement does not automatically exempt an entire website or business.

Provision	What it covers	How to apply it carefully
Older media and office documents	Pre-recorded time-based media and office file formats published before 28 June 2025	Check the content type and publication date; do not infer a service-wide exemption.
Online maps	Online maps where essential information is provided accessibly for navigational maps	Confirm the accessible alternative provides the essential information.
Third-party content	Content not funded, developed, or controlled by the relevant economic operator	Check the funding, development, and control facts for that content.
Archived content	Qualifying archived content that is not updated or edited after 28 June 2025	Confirm it is genuinely archived and has not been updated or edited after the date.
Microenterprise service providers	Microenterprises providing services are exempt from the service accessibility requirements	The Directive defines a microenterprise as employing fewer than 10 people and having annual turnover or annual balance sheet total not exceeding EUR 2 million. Check the definition and national implementation for the specific business.
Fundamental alteration or disproportionate burden	Requirements need not apply where they would cause a fundamental alteration or disproportionate burden, subject to a documented assessment process	Document the assessment and follow the applicable law. This is not a general opt-out.

AccessibleEU guidance states that lack of priority, time, or knowledge is not a legitimate reason for claiming disproportionate burden. Because the result depends on evidence and applicable law, do not infer that a cost or staffing concern automatically qualifies.

How does the EAA relate to the Web Accessibility Directive?

The Web Accessibility Directive (WAD), Directive (EU) 2016/2102, addresses websites and mobile applications of public-sector bodies. The Commission says it requires public-sector accessibility statements, a user feedback mechanism, and regular monitoring by Member States. The EAA covers selected products and services, including parts of the private sector.

A public-sector website can therefore have WAD obligations and also fall within the EAA for a covered activity, such as e-commerce or passenger transport. Determine which directive applies to each service and obligation; do not assume one replaces the other. See the Commission’s [web accessibility policy](https://digital-strategy.ec.europa.eu/en/policies/web-accessibility) for its overview of the WAD and EAA.

A developer’s implementation checklist

Establish scope. Record the service, intended consumers, contract or transaction flow, product or service category, Member States served, and relevant national law.
Inventory the service. Include the website, mobile service, related online applications, support paths, third-party components, and every step in important user journeys.
Map requirements. Translate the applicable legal provisions and relevant technical criteria into testable requirements. Record which standard edition and published reference you relied on.
Review all four principles. Assess information, controls, navigation, forms, identity verification, security, and payment for perceptibility, operability, understandability, and robustness.
Fix at source. Correct the component, content, or process that causes the barrier. Do not rely on an overlay that leaves the underlying service inaccessible.
Test with people and technology. Combine suitable automated checks with manual review and testing involving people with disabilities and assistive technologies.
Document conclusions. Keep the scope analysis, technical mapping, findings, remediation decisions, retests, and any claimed exclusion or burden assessment together.
Reassess changes. New checkout flows, identity systems, content, vendors, or service territories can change the accessibility picture or scope analysis.

The Commission estimates that 100 million people in the EU have some form of disability; the consulted policy page does not state a year alongside that estimate. Accessible services also make core tasks available to more people, but legal coverage still turns on the Directive and national rules.

Using screenshots in accessibility review

A screenshot can preserve a visual state for a bug report, design review, or before-and-after comparison. It cannot establish keyboard operability, meaningful screen-reader output, understandable error recovery, or compatibility with assistive technologies. Use screenshots as one artifact in a broader assessment, and record the interaction steps and assistive technology involved when reporting a barrier.

For repeatable visual captures of a web page, [ScreenshotNeo](https://screenshotneo.com) is a website screenshot API and MCP server for developers. It can capture full pages or selected elements, use device presets or a custom viewport, and apply custom CSS or JavaScript. Those capture options support visual review; they do not determine whether a service complies with the EAA.

Or skip the browser setup

For a screenshot of a page during visual review, ScreenshotNeo provides an API call. The API is not an accessibility checker and a screenshot is not proof of compliance. See the [ScreenshotNeo API documentation](https://screenshotneo.com/docs/) for options and parameter details.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
with open("shot.webp", "wb") as f:
    f.write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));

Cookie banners, popups, and chat widgets are removed before the shot, and each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing; response headers report the page verdict and billing status. An MCP server provides screenshot tools for AI agents, including Claude, Cursor, and other MCP clients. The free plan includes 1,000 shots a month with no card; paid plans start at $5 for 3,000 shots. [Create a free ScreenshotNeo account](https://screenshotneo.com/account/sign-up/) to get started.

Performance, reliability, and cost considerations

Performance: Accessibility work should be part of component and journey design, not a last-minute overlay. For screenshot capture, full-page rendering and waiting for delayed content can take longer than capturing an initial viewport; choose waits based on the page’s actual behavior.
Reliability: Repeatable reviews need a stable URL, viewport, and page state. Dynamic content, consent state, authentication, and delayed rendering can change what a capture shows. Keep screenshots alongside interaction-based findings rather than treating them as the whole test record.
Cost: The EAA’s legal applicability is not determined by a testing tool’s price. For ScreenshotNeo, the free plan has 1,000 shots per month with no card; paid plans are Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan. Only clean shots are billed.

Common mistakes and troubleshooting

Problem	Why it happens	What to do
Assuming every website is covered	The EAA specifies product and service categories; it is not a universal website rule.	Classify the service and check the relevant national implementing law.
Assuming an online store is outside scope because it is a technology business	Coverage turns on the service and consumer contract function, not the company’s label.	Assess whether consumers can conclude a contract through the site or mobile service.
Applying the same transport rule to every transit site	The transport provisions have qualifications, including a distinct rule for urban, suburban, and regional transport.	Identify the transport mode and service element, then check the specific provision and national rules.
Calling a site compliant because it passes an automated scan	A scan does not demonstrate every legal outcome or user task.	Use automation as one input; add manual and assistive-technology evaluation and testing with people with disabilities.
Installing an overlay instead of fixing barriers	An overlay may not make the underlying website meet detailed criteria.	Fix the relevant content, component, or process at source.
Treating a listed exclusion as a site-wide exemption	Several exclusions concern particular content, dates, or conditions.	Document the specific content and condition; assess the rest of the service separately.
Assuming a microenterprise exemption based on a rough headcount	The definition includes both fewer than 10 employees and a turnover or balance-sheet threshold, and national implementation matters.	Check both limbs of the definition and the relevant national law before relying on it.
Claiming disproportionate burden without evidence	The Directive provides a documented assessment process; it is not an informal opt-out.	Follow the applicable law and retain the assessment and supporting information.
A screenshot misses content or shows the wrong state	Delayed rendering, consent state, or dynamic content may affect capture output.	Use an appropriate wait condition, make the desired state reproducible, and separately test interactions.

Frequently asked questions

Does the EAA apply to a business-to-business website?

The e-commerce definition concerns concluding a consumer contract. Whether a particular service falls within that or another category depends on its users, function, and the applicable national law.

Does the EAA require a particular accessibility overlay?

No. Commission guidance says overlays that do not ensure the website itself meets detailed criteria are not an appropriate solution. The focus is accessible service outcomes and fixing issues at source.

Can a public-sector site have duties under both directives?

Yes. The WAD applies to public-sector websites and mobile applications, while the EAA can also apply to a covered service the body provides. Assess each obligation separately.

Does a screenshot prove that a checkout is accessible?

No. It records visual appearance at a point in time. Keyboard use, assistive-technology behavior, understandable errors, and task completion need appropriate interaction testing.

Where can I find the rules for my country?

Start with the official Directive, then check the national law and guidance for each relevant Member State. This guide does not provide country-by-country enforcement or penalty analysis.

Sources

This is a technical overview, not a country-specific legal opinion. Confirm coverage and obligations under the national law relevant to your service.