Skip to main content
WCAG Auditor · EAA Resource Center

Electronic communications

Electronic communications services and the consumer terminal equipment that goes with them. Access to emergency communications is included.

This overview is informational, not legal advice. Whether a given product or service is in scope is a legal call for your organization to make.

What the EAA covers here

Electronic communications services — the connectivity a consumer actually buys, from telephony to messaging to internet access — are covered alongside the consumer terminal equipment tied to them: routers, modems, and similar devices with interactive computing capability that a provider supplies or requires. The two are named together because a customer’s experience of the service runs through both: an accessible account portal attached to a router setup screen nobody can operate is only half solved.

The account and billing surfaces a provider runs — sign-up, plan changes, bills, support — sit inside this scope as much as the underlying connectivity does.

The service and its terminal equipment

Providers typically run two distinct kinds of surface here, and a review has to treat them separately. The service side is mostly web and app: account portals, plan management, billing, and support/contact flows. The equipment side is embedded software running on physical hardware — router admin interfaces, set-up wizards, and on-device status displays — which sits under a different part of the EN 301 549 catalog than a web page does, closer to how any other consumer software product is reviewed.

Emergency communications

The EAA gives particular weight to equivalent access to emergency communications: where a provider offers real-time text or total conversation alongside voice, a deaf, hard-of-hearing, or speech-impaired consumer needs an equivalent way to reach emergency services, not a degraded fallback. That’s a narrower, more specific requirement than general service accessibility, and it’s worth treating as its own line item rather than folding it into a general web or app review.

What auditors look at first

A first pass usually separates the two surfaces cleanly: on the service side, whether account and billing information is exposed through real markup rather than colour or icon alone, and whether support channels offer a genuine text-based path alongside voice; on the equipment side, whether setup and status screens on the device itself can be operated by keyboard or an equivalent input, and whether status is ever conveyed only through a small icon or a single colour with no accompanying text.

What typically fails here

Recurring accessibility failures in this area. Illustrative — an audit reports what your own surfaces actually do.

  • Router and modem setup screens that can't be operated without a mouse or touchscreen.
  • Account portals that announce a plan or billing change only through a colour-coded badge.
  • Support and IVR flows with no text-based or relay alternative to a voice call.
  • Bills and contract documents delivered as unstructured, untagged PDFs.
  • Terminal equipment status indicators shown only as small icons with no text equivalent.

EN 301 549 clauses this maps to

Clauses from our v3.2.1 report catalog — a curated subset of the standard, not the complete list of clauses that may apply to you.

  • 9.1.3.1 Info and Relationships
  • 9.4.1.2 Name, Role, Value
  • 11.1.4.3 Contrast (Minimum) — software
  • 11.2.1.1 Keyboard (software)
  • 5.1.3.2 Auditory output delivery including speech
  • 4.2.4 Usage without hearing
  • 4.2.6 Usage with no or limited vocal capability

Next: what a conformance report contains, or run the 2-minute readiness check.

Check your EAA readiness

A 2-minute, browser-only questionnaire. No answers are sent anywhere.