Skip to main content
EAA A11y Hub

Clause 11 — Software

Clause 11 is the software equivalent of Clause 9 — it covers native mobile apps, desktop applications, and operating systems, restating WCAG-equivalent success criteria in software terms via the “WCAG2ICT” mapping.

What it covers

  • Platform accessibility APIs — the software must correctly expose its UI through the platform's accessibility layer, so tools like VoiceOver, TalkBack, and desktop screen readers can interpret it.
  • Keyboard and switch-equivalent operability — all functionality must be operable without a mouse or touch alone.
  • Closed functionality — software with genuinely no accessible interface (some dedicated ticket-machine software, for example) still needs an alternative means of access, per Clause 5.
  • Includes web apps that behave like software (e.g. complex single-page applications), alongside the web-content requirements of Clause 9.

Who this applies to

Native mobile apps, desktop applications, and operating systems in scope of the EAA and the Web Accessibility Directive's mobile app requirements.

For the fuller narrative on native apps, kiosks and related non-web scope, see the Non-web overview.

Read the standard

This page is a plain-language summary, not the normative text. For the full requirement wording, see EN 301 549 V4.1.1 (2026-09) directly:

Download EN 301 549 V4.1.1 (PDF, ETSI)

V4.1.1 is the newest published edition, aligned with WCAG 2.2 AA. It is not yet cited in the EU Official Journal, so V3.2.1 (WCAG 2.1 AA) remains the version with current legal effect for EAA presumption of conformity — see the timeline for the expected citation date.