Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →The European Accessibility Act (EAA), Directive (EU) 2019/882, does not apply to every website. Its requirements apply to specified products and services, including e-commerce and certain transport, banking, communications, e-book and audiovisual services. The rules have applied since 28 June 2025, but national laws implement and enforce them. First determine whether your service is covered under the law of the Member State relevant to it; then make accessibility part of the service’s information, interface and core tasks—not a cosmetic layer added afterward.
Does the European Accessibility Act apply to my website?
Start with what the website or mobile service does, not the label on the business or the technology it uses. The EAA covers specified service categories. For developers, e-commerce is an especially important one: the Directive defines it as a service provided at a distance, by electronic means, through a website or mobile service, at a consumer’s individual request, with a view to concluding a consumer contract. Its recitals clarify that accessibility obligations cover online sales of any product or service.
As an Amazon Associate I earn from qualifying purchases.
That means an online purchase journey may be in scope even when the operator does not think of itself as a technology company. Conversely, the fact that a website exists does not by itself establish EAA coverage. Identify the service being provided, who provides it, and whether it falls into a category in the Directive; then check the relevant national implementing law.
Service categories named by the Directive
From 28 June 2025, the EAA’s scope includes specified services such as:
#1 Best Overall
- Electronic communications services and access to audiovisual media services.
- Specified elements of passenger transport, including relevant websites, mobile services, ticketing and travel information, subject to qualifications. Urban, suburban and regional transport provisions differ; do not assume that every transit website is covered in the same way.
- Consumer banking services.
- E-books and dedicated software.
- E-commerce services.
- Answering emergency communications to 112.
The Directive also covers specified products, including consumer general-purpose computer hardware and operating systems, certain self-service terminals, some consumer communications and audiovisual terminal equipment, and e-readers. Whether product rules affect a particular web service or its components depends on the applicable provisions; assess the service and product questions separately where relevant.
Dates and national rules
Member States were required to transpose the Directive by 28 June 2022 and apply their measures from 28 June 2025. The EAA includes transitional arrangements: some products already being used to provide services may continue to be used, and some transitions may extend to 28 June 2030. Certain self-service terminals may remain in use until the end of their economically useful life, subject to the Directive’s limit. These are not blanket extensions for every website or service. Check the national law and the precise transitional provision that applies to your case.
What do developers need to make accessible?
For a covered service, the obligation concerns accessible service information and functionality. The Directive requires websites, related online applications and mobile services to be accessible in a consistent and adequate way, applying the principles of perceivability, operability, understandability and robustness. It also addresses accessible support services where available.
Information and interface
Make information and interface components available in ways users can perceive, including when they rely on assistive technologies. Users must be able to operate interface components and navigation, understand information and how to use the service, and access content that works robustly with a variety of user agents. Treat those as outcomes to verify across real service journeys, not as a checklist that a single automated scan can certify.
E-commerce journeys
For covered e-commerce, accessibility work must reach the steps that let a consumer identify themselves, complete security checks and pay—not stop at the landing page. The Directive also addresses accessibility information about goods or services when that information is supplied by the responsible operator. Include these functions and information in the scope of implementation and testing.
Translate outcomes into engineering work
Use the four principles to organize the work, while checking the full legal requirements that apply to your service:
- Perceivable: can users access the information and interface components through the means available to them?
- Operable: can users navigate and complete each task through the controls and input methods they use?
- Understandable: can users understand the content, controls, feedback and steps in the process?
- Robust: does the service work with a variety of user agents, including assistive technologies?
Map these questions to the complete customer journey, including sign-in, security checks, error recovery, support and payment where present. A flow that is accessible until its final confirmation step is not an accessible end-to-end service.
Is WCAG or EN 301 549 required?
The EAA states accessibility outcomes; it should not be reduced to a claim that one checklist, tool or standard automatically settles compliance. 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 gives a presumption of conformity only for the requirements that standard covers. Verify the currently applicable standard and published references, and confirm which requirements apply to your service.
Use a relevant standard to guide and document implementation, but do not treat it as a blanket safe harbour. The legal question remains whether the applicable requirements are met by the service in scope.
What exclusions and exemptions might matter?
The Directive contains specific content exclusions and limited exemptions. These need to be assessed against the actual content, service and operator; they do not automatically remove an entire website from scope.
Specific content exclusions
The EAA excludes specified website and mobile-service content, including:
Recommended Free Tools
- Pre-recorded time-based media and office file formats published before 28 June 2025.
- Online maps when essential information is provided accessibly for navigational maps.
- Third-party content that is not funded, developed or controlled by the relevant economic operator.
- Qualifying archived content that is not updated or edited after 28 June 2025.
Check whether the particular content meets the conditions. An excluded item does not by itself exempt the surrounding service or other content.
Rank #4
Microenterprises providing services
Microenterprises providing services are exempt from the EAA’s service accessibility requirements. The Directive defines a microenterprise as an enterprise that employs fewer than 10 people and has annual turnover or an annual balance sheet total not exceeding EUR 2 million. Confirm the definition and how the exemption is implemented in the relevant Member State before relying on it.
Fundamental alteration or disproportionate burden
The Directive allows requirements not to apply where compliance would cause a fundamental alteration or disproportionate burden, subject to a documented assessment process. This is not a general opt-out. AccessibleEU guidance says that lack of priority, time or knowledge is not a legitimate reason for claiming disproportionate burden. If you consider an exception, follow the relevant assessment and documentation requirements in the applicable law rather than treating it as an informal project decision.
How should a development team implement and test accessibility?
Build accessibility into the service itself, then test the service’s information and tasks with a combination of appropriate technical checks and user testing. The Commission advises fixing issues at source and involving people with disabilities in testing.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems- Confirm scope. Document the service category, relevant Member State, national implementing law, and any specific transitional provision or exclusion you believe applies.
- Inventory user journeys. Include the information, controls, support and transaction steps users need—not just the public landing pages. For e-commerce, include identification, security and payment.
- Assess the four principles throughout each journey. Check whether content can be perceived, navigation and tasks operated, information understood, and the service used robustly with assistive technologies.
- Fix issues in the implementation. Correct the underlying content, interface or function. Do not treat an overlay or a separate accessibility widget as a substitute for making the service itself accessible.
- Combine testing methods. Automated checks can be one part of an engineering workflow, but an automated result alone does not establish that statutory requirements are met. Involve people with disabilities in testing and assess actual task completion.
- Keep evidence and revisit changes. Record what was assessed and how identified issues were addressed. Reassess affected journeys when the service changes; consult the applicable national law for any formal documentation duties.
A useful review spans the whole journey: can users find and perceive essential information, operate navigation and controls, understand instructions and feedback, recover from errors, and complete the relevant task using their assistive technology and user agent? This is a practical engineering framework derived from the Directive’s principles, not a substitute for checking all legal requirements.
Best Value
Are accessibility overlays enough?
No. The Commission says overlays or other tools that do not ensure the website itself meets detailed standard criteria are not an appropriate solution; it recommends fixing problems at source. A tool can support a workflow, but it cannot by itself establish that the service meets its legal obligations. Automated scans and visual inspection also cannot replace testing with people with disabilities.
How does the EAA differ from the Web Accessibility Directive?
The Web Accessibility Directive (Directive (EU) 2016/2102) concerns websites and mobile applications of public-sector bodies. The Commission says it includes public-sector accessibility statements, a user feedback mechanism and regular monitoring by Member States. The EAA covers specified products and services, including parts of the private sector. The directives complement one another: a public-sector website may have Web Accessibility Directive duties and also fall under the EAA for a covered activity such as e-commerce or passenger transport.
Use screenshots as visual evidence, not as an accessibility verdict
Rendered screenshots can help a team review visual changes or document what a page looked like at a particular point, but they do not show whether a person can operate the page with a keyboard or use it with assistive technology. ScreenshotNeo is a website screenshot API and MCP server for developers; it can capture pages as images or PDFs. Its cookie-consent, popup and chat-widget removal can be turned off step by step, which matters if the review is specifically about those interface elements. Do not treat a screenshot, or any screenshot service, as proof of EAA compliance. See ScreenshotNeo.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteFor example, this cURL request captures a page for visual review; see the ScreenshotNeo API documentation for the API parameters:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo says bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and responses identify page verdict and billing status in headers. It offers an MCP server with screenshot, page-information and PDF-capture tools for AI agents. Its free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Sign up for 1,000 free screenshots a month, with no card required.
What should a developer do next?
- Decide whether the service—not merely the website—falls within an EAA category.
- Check the national implementing law and the provisions that apply to the relevant service and Member State.
- Map the complete service journey, with special attention to sign-in, security and payment for e-commerce.
- Implement accessibility in the service itself, use applicable technical criteria carefully, and test with people with disabilities.
- Assess exclusions or exemptions narrowly and document any disproportionate-burden or fundamental-alteration assessment required by law.
Frequently Asked Questions
Does the EAA require the same implementation from every covered business in every EU country?
The Directive establishes EU-level requirements, but Member States transpose and enforce them through national law. For a specific service, check the rules in the Member State relevant to it rather than assuming that implementation details or enforcement are identical everywhere.
Can an accessibility scan certify that a website complies with the EAA?
No single automated scan establishes that a service meets all applicable legal requirements. Use automated checks as one part of testing, alongside assessment of real user journeys and testing with people with disabilities.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
