Skip to main content
EAA A11y Hub

Clause 6 — ICT with two-way voice communication

Clause 6 applies to ICT that supports two-way voice calls — think business phone systems, video conferencing platforms, or any product where a real-time voice conversation is a core feature.

What it covers

  • Real-time text (RTT) — the ability to send and receive text character-by-character as it's typed, alongside or instead of voice, so a deaf or hard-of-hearing user (or someone who can't speak) can participate in a live call.
  • Interoperability with captioned telephony — the product shouldn't block or degrade the use of captioned-relay services that transcribe the other party's speech in real time.
  • Alerting — incoming call alerts must be perceivable both visually and non-visually, not relying on sound alone.
  • Voice quality — where voice is the medium, audio quality requirements exist so speech (and lip-reading cues in video) remain intelligible.

Who this applies to

Products whose core function is two-way voice communication: PBX and softphone systems, video-conferencing tools, and similar. It generally doesn't apply to closed, dedicated systems with no voice-communication element at all.

Read the standard

This page is a plain-language summary, not the normative text. For the full requirement wording, see EN 301 549 V3.2.1 (2021-03) directly:

Download EN 301 549 V3.2.1 (PDF, ETSI)

V3.2.1 (WCAG 2.1 AA) is the version cited in the EU Official Journal and currently has legal effect for EAA presumption of conformity. A newer edition, V4.1.1 (WCAG 2.2 AA), has been published but is not yet cited — see what's coming in V4.1.1 for what's changing and when it's expected to take effect.