The European Accessibility Act (EAA) requires that emergency communications to the single European emergency number 112 be accessible to people with disabilities. This means public safety answering points must be reachable through synchronous voice, real-time text, and total conversation services (video where provided), so people who cannot use traditional voice calls can still reach emergency services. The requirements apply to the answering of 112 calls and the routing of those calls, with conformance generally measured against EN 301 549 and WCAG 2.1 AA where digital interfaces are involved.
| Area | Requirement |
|---|---|
| Emergency number | Access to 112 must be accessible to people with disabilities. |
| Communication modes | Voice, real-time text, and total conversation (voice, text, video) where supported. |
| Who is responsible | Member States, through public safety answering points (PSAPs) and providers of electronic communications services. |
| Conformance standard | EN 301 549, which references WCAG 2.1 AA for web and mobile interfaces. |
| Effective date | EAA requirements went into effect on June 28, 2025. |
What the EAA Says About Emergency Communications
The EAA treats emergency communications as a distinct category from consumer products and services. Article 4 of the directive requires Member States to confirm that answering of emergency communications to 112 by the most appropriate PSAP is accessible to people with disabilities, consistent with national arrangements for emergency services.
The directive frames this around two-way access. A person with a disability must be able to reach 112 using a method that works for them, and the PSAP must be able to receive, route, and respond to that communication.
What Counts as Accessible Emergency Communication?
The EAA points to total conversation as the model. Total conversation combines voice, real-time text, and video in a single call, letting the caller and the operator switch between modes or use them together.
In practice, this means a Deaf or hard of hearing user can reach 112 through real-time text without a third-party intermediary. A user who relies on sign language can connect through video where video relay is supported. A user with a speech disability can type to the operator while still receiving spoken responses if useful.
Real-time text is the key technical piece. Unlike SMS, real-time text transmits character by character as it is typed, which keeps the pace of the exchange close to a voice conversation. That speed matters when seconds count.
Who Has to Comply?
Two groups carry the weight of EAA emergency communications requirements.
Member States are responsible for setting up PSAPs that can receive accessible 112 communications. They decide the operational model, the technology stack, and how calls are routed.
Providers of electronic communications services have obligations to support the transmission of accessible emergency communications across their networks. If a carrier supports real-time text or video calling, those modes must be usable for reaching 112.
Public bodies and private operators that build the software or web interfaces involved in emergency access also fall within scope when their products are placed on the EU market.
How Conformance Is Measured
EN 301 549 is the harmonized European standard that maps the EAA’s accessibility requirements to specific technical criteria. For any web page, mobile app, or digital interface tied to emergency communications, EN 301 549 references WCAG 2.1 AA.
That includes the public-facing portions of PSAP services: a citizen-facing app that places a 112 call, an emergency alert subscription page, a real-time text gateway. These need to meet WCAG 2.1 AA criteria to be considered conformant.
A manual accessibility evaluation is the only way to confirm WCAG conformance for these interfaces. Automated scans flag approximately 25% of issues and cannot evaluate items like meaningful sequence, keyboard operability across complex flows, or the accuracy of accessible names on custom controls.
What This Looks Like in Practice
A Member State might run a centralized PSAP that accepts voice calls to 112 from any phone, real-time text sessions initiated from a native dialer or a dedicated app, video calls routed to operators trained in national sign language, and location data passed through advanced mobile location to speed dispatch.
On the digital side, the citizen-facing components, registration portals, app interfaces, and any pages that explain how to reach emergency services need accessible structure, keyboard support, visible focus, and screen reader compatibility.
How Does the EAA Connect to Broader Accessibility Work?
For most organizations, emergency communications sit alongside the rest of their EAA scope. A telecom operator dealing with EAA conformance for its consumer apps will also have obligations tied to how those apps interact with 112. A government body managing public safety infrastructure will face similar accessibility expectations across its civic digital services.
The path is the same: identify the digital assets in scope, evaluate them against WCAG 2.1 AA, address the issues identified, and document conformance. The Accessible.org approach for EAA work follows that sequence.
Frequently Asked Questions
Do private companies need to provide accessible 112 access?
Private companies do not run 112, but electronic communications providers must support the transmission of accessible emergency calls. If a carrier’s network or calling app is involved in placing a 112 call, accessibility expectations apply to that link in the chain.
Is SMS to 112 enough to meet EAA requirements?
SMS alone is generally not enough. The EAA points toward real-time text and total conversation because SMS lacks the speed and back-and-forth structure needed during an emergency exchange. Some Member States may keep SMS as a supplemental option, but it is not a substitute for real-time text.
How does WCAG 2.1 AA apply to a 112 service?
WCAG 2.1 AA applies to the digital interfaces connected to emergency communications. The phone call itself is governed by telecom standards and EN 301 549’s communication clauses, but any website, app, or web-based dashboard tied to the service needs to meet WCAG 2.1 AA.
When did these requirements take effect?
The EAA went into effect on June 28, 2025. Member States transposed the directive into national law in advance of that date, and emergency communication obligations have been part of that implementation.
What documentation should an organization keep?
Organizations should keep evaluation reports, conformance statements tied to EN 301 549 and WCAG 2.1 AA, records of remediation work, and any policies governing how accessibility is maintained over time. Accessible.org issues this documentation as part of its EAA work.
Emergency communications are where accessibility shifts from a service expectation to a safety one. Getting the technical pieces right, real-time text, total conversation, and conformant digital interfaces, is what the EAA asks of the parties responsible.
Contact Accessible.org to discuss EAA conformance for your digital assets: Contact Accessible.org.
