Telecom Accessibility and EAA Compliance

Telecoms under the EAA

Electronic communications — phone, broadband, and internet services — are explicitly listed in the European Accessibility Act as a covered sector. Telecommunications companies providing services to EU consumers have been required to comply since June 28, 2025.

This is not limited to large carriers. Mobile virtual network operators (MVNOs), regional broadband providers, and business telecoms services are all within scope if they serve EU consumers and are not classified as microenterprises (fewer than 10 employees and under €2 million turnover).

The practical scope of what must be accessible is broad: not just your main website, but mobile apps, customer portals, billing systems, product catalog pages, self-service terminals, and support channels.

The customer journey in telecoms is long and complex

One of the challenges of telecoms accessibility is the length and complexity of the customer journey. A customer signs up, manages their account, tracks usage, pays bills, changes plans, troubleshoots issues, and sometimes returns equipment — all across a digital estate that often spans multiple platforms, some legacy.

Every touchpoint where a disabled user encounters a barrier is a compliance failure, not just the most public-facing one. EAA compliance requires examining the complete journey, not just the homepage.

Where telecoms platforms most commonly fail

Missing semantic markup and screen reader incompatibility

Telecom websites are often complex single-page applications with dynamic content — plan comparisons, coverage maps, real-time usage data. Complex JavaScript-heavy UIs are where screen reader compatibility most often breaks down.

Common failures:

• Tab panels and accordions built with <div> elements that have no role attribute — screen readers can’t tell these are interactive
• Loading states that appear visually but aren’t announced to screen readers via live regions
• Plan comparison tables that use CSS positioning to create visual layouts that don’t match the DOM reading order — screen reader users hear the table content in the wrong sequence

Unlabeled form fields in service flows

Sign-up flows, plan changes, address updates, and payment entry all involve forms. The failures are the same as in other sectors but with specific complexity:

• Account number and reference fields with placeholder text only — the label disappears when the user starts typing
• Coverage checker inputs — postcode or address fields that use custom autocomplete components without ARIA support
• SIM card activation flows with multi-part numeric fields (IMEI numbers, SIM serial numbers) where the relationship between fields isn’t programmatically communicated

Inaccessible PDF billing documents

Bills, invoices, and usage summaries distributed as PDFs are routinely inaccessible. The tables within usage summaries — which are the dense, data-rich part of the bill — are among the hardest PDF content to make accessible, and among the most commonly broken.

For a user who cannot access their bill, the fundamental transparency of the service relationship is broken. Our PDF accessibility guide covers what accessible PDF documents require.

Video content without captions or transcripts

Telecoms companies produce significant volumes of video content: product walkthroughs, feature announcements, customer support videos, promotional content. Videos without captions exclude deaf and hard-of-hearing users and anyone watching in a sound-sensitive environment.

WCAG 1.2.2 Captions (Prerecorded) (Level A) requires captions for all prerecorded audio in synchronized media. This is a Level A requirement — the baseline level, not optional. Auto-generated captions on platforms like YouTube are a starting point but typically require review and editing for accuracy, particularly with technical terms.

Complex account management portals

Customer self-service portals — where users manage contracts, track data usage, pay bills, and change plans — are among the most complex digital environments telecoms companies operate. They tend to have:

• Custom data visualization components for usage graphs that aren’t keyboard accessible and don’t provide accessible text alternatives
• Plan management UI with custom toggles and selectors that don’t communicate state correctly to assistive technology
• Document download sections with inadequate link descriptions (“Download” with no indication of which document)

Inaccessible chatbots and support interfaces

Support chatbots are increasingly the primary customer service channel for telecoms providers. Most are not accessible. Common failures include:

• Chat input fields without proper labels
• Message history not announced to screen readers as new messages arrive (requires aria-live regions)
• Keyboard traps within the chat widget — tab key doesn’t exit the widget, stranding keyboard users
• Touch targets on mobile too small for users with motor disabilities

Our guide on chatbot accessibility covers these patterns in detail.

What EAA compliance requires for telecoms

The technical standard is WCAG 2.1 Level AA across all digital customer touchpoints: websites, mobile apps, and the interactive components within them.

The EAA also requires:

• An accessibility statement documenting current conformance, known exceptions, and a feedback mechanism
• A process for providing accessible alternatives where content is temporarily non-compliant
• Response to user accessibility complaints within a reasonable timeframe

Prioritizing remediation

A telecoms digital estate is too large to fix all at once. Start with the highest-traffic, highest-impact flows:

1. Sign-up and plan selection — this is revenue. Inaccessibility here costs customers.
2. Bill viewing and payment — core transactional function
3. Account management: view data usage, change plan, update details
4. Support: chatbot and contact options
5. Video content audit for captioning completeness

For each area, combine automated scanning (fast, catches structural and contrast issues) with manual testing (essential for keyboard navigation and screen reader behavior). Automated tools alone cannot verify that complex data tables announce correctly or that the chat widget allows keyboard exit.

Run a free automated scan of your public-facing site to see the current baseline. For the comprehensive assessment your EAA compliance program requires, contact our team about a structured audit across your full digital customer journey.