Blank checklist, printable form
Emergency Services Accessibility Checklist
EN 301 549 Chapter 13 Compliance Checklist
Blank checklist for offline completion.
Tick one box per row. Add comments and evidence references in the Notes column as needed.
Emergency Access Methods
EN 301 549 §13.2-§13.3, Emergency services must be reachable through multiple communication methods. Note: §13.1 covers general relay services (not emergency-specific); §13.2 covers emergency service access including RTT and location; §13.3 covers total conversation for emergency calls.
| Ref | Severity | Requirement | Status | Notes / Evidence |
|---|---|---|---|---|
| EN 301 549 §13.2 | Critical | Emergency calling supports voice communication to emergency services.The primary voice path to 112/911 must function reliably. This is the baseline requirement. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EN 301 549 §13.2 | Critical | Emergency calling supports real-time text (RTT) alongside voice.Deaf and hard-of-hearing users must be able to contact emergency services via RTT. The RTT path must reach the same emergency centre as voice. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EN 301 549 §13.3 | Major | Emergency calling supports total conversation (voice + video + RTT simultaneously).Total conversation allows sign language users to communicate via video while also having voice and RTT available. This is the most inclusive emergency communication mode. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EN 301 549 §13.2 | Major | Emergency text communication is available via SMS where RTT is not yet supported.As an interim measure, SMS to emergency services should be supported in jurisdictions where RTT infrastructure is not yet deployed. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A |
Location & Identification
Caller location and identification must be transmitted accessibly.
| Ref | Severity | Requirement | Status | Notes / Evidence |
|---|---|---|---|---|
| EN 301 549 §13.1 | Critical | Caller location information is automatically transmitted with emergency calls.E-112 and AML (Advanced Mobile Location) must be supported. Location data helps emergency services reach users who cannot verbally describe their location. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EN 301 549 §13.1 | Major | Caller identification is transmitted in text form to emergency services.The caller's number and identity must be available as text data, not just audio announcement, so emergency operators can call back via RTT or text if needed. This falls under the general emergency communication requirements of Chapter 13. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A |
Multi-Modal Communication
Emergency communication must not depend on a single sensory channel.
| Ref | Severity | Requirement | Status | Notes / Evidence |
|---|---|---|---|---|
| EN 301 549 §13.1 | Critical | Emergency communication is not dependent on a single sensory modality.Users must be able to reach emergency services whether they can hear, speak, or see. Voice-only emergency services exclude deaf users; text-only excludes users with motor impairments. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EN 301 549 §13.3 | Major | Video relay to emergency services is available for sign language users.Where total conversation infrastructure exists, sign language users should be able to connect to a video relay interpreter who communicates with the emergency operator. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EN 301 549 §13.1 | Critical | Emergency app or device interface is accessible (keyboard-operable, screen reader compatible).If you provide an emergency calling app or device, its interface must be accessible, large buttons, clear labels, screen reader support, and simple navigation under stress. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EN 301 549 §13.2 | Major | A fallback communication channel exists if RTT or total conversation is unavailable.Network outages or unsupported infrastructure should not leave users without any way to contact emergency services. SMS fallback must be available where RTT is not yet deployed. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 1.4.3 | Critical | Emergency UI elements meet high contrast requirements (4.5:1 minimum).Emergency buttons, alert text, and status messages must have maximum contrast. Users in distress may have reduced visual acuity. Err on the side of higher contrast. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 2.5.5 | Critical | Emergency SOS buttons meet minimum 44x44px touch target size.Emergency activation buttons must be large and easy to tap under stress. WCAG AAA recommends 44x44 CSS pixels, for emergency UI, treat this as a minimum, not a target. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A |