惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

N
News and Events Feed by Topic
GbyAI
GbyAI
博客园 - Franky
宝玉的分享
宝玉的分享
Blog — PlanetScale
Blog — PlanetScale
Google DeepMind News
Google DeepMind News
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
人人都是产品经理
人人都是产品经理
Microsoft Azure Blog
Microsoft Azure Blog
The Register - Security
The Register - Security
腾讯CDC
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
I
InfoQ
The Cloudflare Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Engineering at Meta
Engineering at Meta
MongoDB | Blog
MongoDB | Blog
有赞技术团队
有赞技术团队
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
F
Full Disclosure
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Vercel News
Vercel News
博客园 - 【当耐特】
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
S
Schneier on Security
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Project Zero
Project Zero
量子位
M
MIT News - Artificial intelligence
Stack Overflow Blog
Stack Overflow Blog
C
Cyber Attacks, Cyber Crime and Cyber Security
美团技术团队
Attack and Defense Labs
Attack and Defense Labs
C
Cybersecurity and Infrastructure Security Agency CISA
T
The Blog of Author Tim Ferriss
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
T
Troy Hunt's Blog
Google Online Security Blog
Google Online Security Blog
罗磊的独立博客
P
Proofpoint News Feed
Schneier on Security
Schneier on Security
Spread Privacy
Spread Privacy
S
SegmentFault 最新的问题
L
LINUX DO - 最新话题
Simon Willison's Weblog
Simon Willison's Weblog
爱范儿
爱范儿
博客园 - 聂微东
A
About on SuperTechFans
PCI Perspectives
PCI Perspectives
D
Docker

TetraLogical Blog

Designing for people with reading disabilities - TetraLogical Designing for people who are D/deaf - TetraLogical Designing accessible documents - TetraLogical Introduction to creating accessible documents - TetraLogical Inclusive user research: vulnerable people - TetraLogical Designing for people who are blind - TetraLogical Designing for people with low vision - TetraLogical Meet the team: Niamh Madden - TetraLogical Designing for people with anxiety - TetraLogical Designing for people with disabilities - TetraLogical Accessible building blocks for the web videos - TetraLogical Common accessibility misconceptions - TetraLogical Common misconceptions about testing accessibility - TetraLogical Common misconceptions about implementing accessibility - TetraLogical Common misconceptions about WCAG - TetraLogical Common misconceptions about disability - TetraLogical Meet the team: Grace Snow - TetraLogical Sustainable accessibility in complex organisations: strategic foundations - TetraLogical Sustainable accessibility in complex organisations: organisational realities - TetraLogical Sustainable accessibility in complex organisations: external factors - TetraLogical Common misconceptions about screen readers - TetraLogical Guide to the Inclusive Design Principles - TetraLogical Meet the team: Ian Lloyd - TetraLogical Annotating designs using common language - TetraLogical Meet the team: Catriona Morrison - TetraLogical Championing inclusive language - TetraLogical Press release: TetraLogical launches accessible self-led training courses to help digital teams build confidence in accessibility - TetraLogical Why inclusive products are green products - TetraLogical Accessible Recruitment - TetraLogical Accessibility and the agentic web - TetraLogical Meet the team: Craig Abbott - TetraLogical Foundations: types of assistive technology and adaptive strategies - TetraLogical Screen reader HTML support tables - TetraLogical Interview with Lola Odelola - TetraLogical Understanding EN 17161 Design for All - TetraLogical Inclusive user research: building rapport - TetraLogical Foundations: Keyboard accessibility - TetraLogical Can generative AI write contextual text descriptions? - TetraLogical Understanding the European Accessibility Act (EAA) - TetraLogical Meet Josh: a sportsman who has spinal muscular atrophy - TetraLogical Meet Jonathan: a photographer who has ADHD - TetraLogical Foundations: grouping forms with `<fieldset>` and `<legend>` - TetraLogical XR Accessibility: for people with moving disabilities - TetraLogical Meet Andre: a music producer and blind screen reader user - TetraLogical Foundations: types of disability - TetraLogical Meet Lauren: a film editor who has ADHD - TetraLogical Meet Steve: a photographer who is deaf and low vision - TetraLogical Foundations: form validation and error messages - TetraLogical Meet Hasmukh: a blind cricketer and screen reader user - TetraLogical XR Accessibility: for people with hearing disabilities - TetraLogical XR Accessibility: for people with thinking disabilities - TetraLogical XR Accessibility: for people with seeing disabilities - TetraLogical Introduction to XR Accessibility - TetraLogical Foundations: labelling text fields with input and label - TetraLogical Design patterns and WCAG - TetraLogical Does WCAG 2.2 apply to native apps - TetraLogical Why are my live regions not working? - TetraLogical Building a culture of accessibility - TetraLogical When to use tabindex= Accessibility foundations - TetraLogical Meet the team: Demelza Feltham - TetraLogical Can generative AI help write accessible code? - TetraLogical Meet the team: Steve Faulkner - TetraLogical Meet the team: Gez Lemon - TetraLogical Keyboard accessibility myths and WCAG - TetraLogical Amendment to the Public Sector Accessibility Regulations - TetraLogical What Considerations for TV user interface accessibility - TetraLogical Meet the team: Alistair Duggin - TetraLogical Sticky content: focus in view - TetraLogical The only accessibility specialist in the room - TetraLogical Meet the team: Ian Pouncey - TetraLogical Meet the team: Dean Holden - TetraLogical Meeting WCAG Level AAA - TetraLogical Foundations: accessible names and descriptions - TetraLogical Inclusive XR: accessible augmented reality experiences - TetraLogical Foundations: pointer gestures - TetraLogical Meet the team: Graeme Coleman - TetraLogical Adding sign language to videos - TetraLogical Foundations: introduction to WAI-ARIA - TetraLogical Meet the team: Joe Lamyman - TetraLogical Inclusive XR: accessible 3D experiences - TetraLogical Foundations: visible focus styles - TetraLogical Foundations: target sizes - TetraLogical Meet the team: Henny Swan - TetraLogical Meet the team: Ela Gorla - TetraLogical Foundations: native versus custom components - TetraLogical Foundations: HTML semantics - TetraLogical Accessibility and supporting Internet Explorer - TetraLogical Meet the team: Felicity Miners-Jones - TetraLogical Accessibility and QR codes - TetraLogical Inclusive user research: recruiting participants - TetraLogical Research insight: accessibility of images - TetraLogical Meet the team: Léonie Watson - TetraLogical Android accessibility: roles and TalkBack - TetraLogical Accessible design systems - TetraLogical Meet the team: Patrick H. Lauke - TetraLogical Inclusive user research: analysing findings - TetraLogical How to write user stories for accessibility - TetraLogical Triaging WCAG 2.1 Level AAA - TetraLogical
European Accessibility Act (EAA) FAQ - TetraLogical
2025-07-18 · via TetraLogical Blog

Posted on by Ela Gorla in Standards

The European Accessibility Act (EAA) came into effect on 28 June 2025. Many of our customers have asked what impact that may have on the digital services they offer.

This post provides information on the application of the EAA in the context of websites and mobile apps.

Understanding any new legislation can be challenging. The nature of the European Accessibility Act as a directive and its wide scope can make it particularly difficult to fully understand.

While our Understanding the European Accessibility Act (EAA) post provides a review of the entire directive, this post focuses on digital content only, to make it easier for organisations offering websites, mobile apps, and other digital content to find the information they need.

What is the difference between a directive and a law?

The EAA is a directive, not a law. It sets the overall goals that organisations must achieve, but it does not contain details about how these goals are enforced and monitored. This is decided at a national level by each European Union (EU) member state.

Over the past few years, all EU member states have transposed the EAA into national law. Organisations operating in EU markets must comply with the relevant national law in order to comply with the EAA.

Does the EAA apply to my organisation's websites and apps?

This depends on many factors, including the size of your organisation, the countries it operates in, and the types of digital services it offers.

The following decision tree may help you understand whether your organisation's websites and apps are covered by the EAA:

  1. Does your organisation have 10 employees or more AND an annual turnover of 2 million Euros or more?
  2. Does your organisation operate in EU markets?
  3. Do the digital services your organisation offers fall into any of the following categories?
    • Digital communication services: communication apps like Zoom and WhatsApp
    • TV and video streaming services: platforms like Netflix and YouTube
    • Transport services: websites and apps to book or access air, rail, bus, or water transport
    • Financial services: consumer banking websites and apps
    • Digital books and reading applications: eBooks and eBook reading apps
    • E-commerce platforms: consumer facing marketplaces such as Amazon and eBay

If you answered Yes to all of these questions, the EAA most likely applies to your organisation's digital services.

Even if your organisation does not provide services directly to customers but sell web or native content to other organisations that make it available to the public, it still needs to consider the requirements of the EAA. Unless its content is compliant, organisations covered by the EAA may be unable to purchase or integrate it into their services.

What are the requirements my organisation needs to meet?

There are three sets of requirements your organisation need to consider:

  • The general requirements that apply to all digital services, as described in the EAA
  • The additional service-specific requirements, also set out in the EAA
  • The country-specific requirements, outlined in national law

The general requirements your organisation must meet are set in the EU "harmonised standard" EN 301 549 (PDF). According to the EN 301 549, digital services must meet WCAG 2.1 compliance. Note that this is due to be updated to reference WCAG 2.2 soon.

Your organisation must then check whether the services it provides are subject to the additional service-specific requirements described in Annex I Section IV of the EAA. For example, one of the requirements in the EAA for consumer banking services is:

Ensuring that the information is understandable, without exceeding a level of complexity superior to level B2 (upper intermediate) of the Council of Europe’s Common European Framework of Reference for Languages.

Finally, organisations must comply with the country-specific requirements in the national law of the countries they operate in.

Does all web content need to comply with the EAA?

No, the EAA lists a number of exemptions:

  • Pre-recorded time-based media published before 28 June 2025;
  • Office file formats published before 28 June 2025;
  • Online maps and mapping services, if essential information is provided in an accessible digital manner for maps intended for navigational use;
  • Third-party content that is neither funded, developed by, or under the control of, the economic operator concerned;
  • Content of websites and mobile applications qualifying as archives, meaning that they only contain content that is not updated or edited after 28 June 2025.

The EAA also contains a section about disproportionate burden; if an organisation believes that making some of its content compliant would result in a disproportionate burden, it can request for it to be exempt. However, very few cases are likely to meet the criteria for disproportionate burden. For example, a small organisation offering self-help eBooks might qualify if the cost of full compliance would genuinely threaten its ability to operate. A larger company with greater resources, however, is unlikely to meet that threshold.

How can my organisation reach compliance?

The steps that organisations should take as they work towards reaching compliance are described in another EU harmonised standard referenced by the EAA: EN 17161 Design for All

As described in Understanding EN 17161 Design for All, this standard explains how organisations can integrate accessibility in their processes and practices across the following areas:

  • Context of the organisation
  • Leadership
  • Planning
  • Support
  • Operation
  • Performance evaluation
  • Improvement

How is compliance with the EAA monitored?

Monitoring compliance is responsibility of the individual EU member states. Each state has its own monitoring processes and has appointed one or more market surveillance authorities to carry them out.

The market surveillance authorities are ultimately responsible for ensuring that organisations operating in their country follow the EU harmonised standards EN 301 549 and EN 17161 and any additional country-specific requirements, thus complying with the EAA requirements.

They are also tasked with reviewing the applications for disproportionate burden claims.

How can my organisation document compliance?

Your organisation's websites and apps must be assessed against WCAG and their compliance level must be described in a publicly available accessibility statement.

Currently, the EAA does not provide details on the contents or format of this statement. However, in 2022 the European Commission (EC) requested the harmonised standard EN 301 549 be updated and part of this update will be to include "a model accessibility statement in accordance with Directive (EU) 2016/2102". Many organisations are therefore already using the model accessibility statement template from Directive (EU) 2016/2102 to document the compliance level of their digital services.

Article 13 of the EAA also requires organisations to inform the relevant market surveillance authorities of non-compliant services:

In the case of non-conformity, service providers shall take the corrective measures necessary to bring the service into conformity with the applicable accessibility requirements. Furthermore, where the service is not compliant with applicable accessibility requirements, service providers shall immediately inform the competent national authorities of the member states in which the service is provided, to that effect, giving details, in particular, of the non-compliance and of any corrective measures taken.

Since each member state is ultimately responsible for monitoring conformance, your organisation should also check any country-specific requirements around documenting compliance.

What are the consequences of non-compliance?

The penalties for non-compliance are set by the individual EU member states; they may include fines or prohibition on selling services altogether.

According to Article 13 of the EAA, if you are contacted by a market surveillance authority you must:

Provide it with all information necessary to demonstrate the conformity of the service with the applicable accessibility requirements. [You] shall cooperate with that authority, at the request of that authority, on any action taken to bring the service into compliance with those requirements.

Based on this, it is likely that market surveillance authorities will first ask organisations to rectify any existing issues and make their services compliant. However, if issues are not acted upon promptly, organisations are likely to face penalties.

Next steps

To learn more about the EEA and associated standards, you can read our Understanding the European Accessibility Act (EAA) and Understanding EN 17161 Design for All posts. We can also provide EAA Assessments and Consultancy services to help you meet your goals.