The European Accessibility Act covers telecommunications services offered to consumers in the EU, including voice calling, messaging, and real-time text. Providers must meet accessibility requirements under EN 301 549, the harmonized standard the EAA points to for digital products and services. This covers consumer-facing apps, web portals, account management interfaces, and the telecommunications service itself. Compliance went into effect on June 28, 2025. Providers serving EU consumers, regardless of where the company is headquartered, fall within scope. Documentation of conformance is expected, and market surveillance authorities in each member state enforce the rules.
| Item | Detail |
|---|---|
| Covered services | Consumer voice, messaging, real-time text, and total conversation services |
| Covered products | Consumer terminal equipment used for telecommunications |
| Standard referenced | EN 301 549, which incorporates WCAG 2.1 AA for web content |
| Effective date | June 28, 2025 |
| Documentation | Conformance evidence retained and produced on request from authorities |
| Enforcement | Market surveillance authorities in each EU member state |
Which telecommunications services fall under the EAA?
The Act applies to electronic communications services offered to consumers in the EU. That includes voice calling, SMS and instant messaging, video calling, and the broader category of real-time text and total conversation services where supported.
The scope is consumer-facing. Business-to-business telecommunications arrangements sit outside the Act, though the line can blur when the same product serves both audiences. The safer read is that any service marketed to consumers in any EU member state is covered.
Coverage extends to the digital interfaces consumers use to access these services. Mobile apps, web account portals, self-service flows, billing dashboards, and customer support interfaces all qualify as part of the service for EAA purposes.
What does conformance look like in practice?
EN 301 549 is the harmonized standard the EAA points to. For web content and mobile apps, EN 301 549 incorporates WCAG 2.1 AA. For hardware and software with specific functional needs, EN 301 549 adds requirements that go beyond WCAG, including support for hearing aid compatibility, real-time text, and access to emergency services.
Real-time text is a key requirement for telecommunications providers. Where voice is offered, an equivalent real-time text option must be available, and total conversation (voice, text, and video together) should be supported where technically feasible.
Emergency communications also carry specific obligations. Access to the single European emergency number, 112, must work for people with disabilities, including through text-based and video-based methods.
What documentation should providers keep?
The EAA requires providers to keep records that show how the service meets the accessibility requirements. This typically takes the form of a conformance report, supporting audit evidence, and a public accessibility statement describing the level of conformance and any known issues.
For digital interfaces, an accessibility audit against WCAG 2.1 AA produces the evidence most authorities will want to see. The audit identifies issues, the provider remediates, and the documentation reflects current status. Accessible.org clients in the telecommunications space typically pair a WCAG audit of consumer-facing web and mobile interfaces with a separate review of the service itself against the additional EN 301 549 requirements.
How does enforcement work across member states?
Each EU member state designates a market surveillance authority. These authorities can request documentation, evaluate services against the requirements, and impose penalties for nonconformance. Penalties vary by country but can include fines, mandatory corrective action, and in some cases removal from the market.
Consumers and advocacy groups can file complaints with national authorities. Cross-border services often face questions from more than one authority, which is why consistent documentation across markets matters.
What about non-EU telecommunications companies?
A US, UK, or other non-EU telecommunications company that offers consumer services to people in the EU is within scope. The Act applies based on where the consumer is, not where the company is headquartered. Roaming agreements, internet-based calling services, and messaging apps with EU users all qualify.
For larger providers, the practical approach is a single conformance baseline across the product, mapped to EN 301 549, with country-specific statements where required by national rules.
FAQs
Do telecommunications providers need a separate audit for the EAA?
A WCAG 2.1 AA audit covers the digital interface requirements. The additional EN 301 549 requirements specific to telecommunications, real-time text, total conversation, and emergency service access, are evaluated separately against those clauses. Most providers need both.
Does the EAA require WCAG 2.2 AA?
The current harmonized version of EN 301 549 references WCAG 2.1 AA. WCAG 2.2 AA is not required by the Act as written, though some providers choose to evaluate against 2.2 AA to stay ahead of future updates.
What happens if a telecommunications provider misses the deadline?
The compliance date of June 28, 2025 has passed. Providers not yet in conformance should prioritize an audit of consumer-facing interfaces, address the EN 301 549 telecommunications-specific clauses, and publish an accessibility statement that reflects current status and the path to full conformance.
Are MVNOs and resellers covered?
Yes, if they offer telecommunications services to EU consumers under their own brand. The obligations attach to the entity placing the service on the market, which includes mobile virtual network operators and resellers.
Telecommunications sits at the center of how people communicate, and the EAA reflects that by setting a consistent accessibility baseline across EU markets. Providers that treat conformance as part of product quality, not a separate compliance project, tend to move through the work faster and with cleaner documentation.
Contact Accessible.org for a quote on EAA audit and documentation work: Contact Accessible.org.
