EN 301 549 Clause 11 Overview
Published
Clause 11: Software
Clause 11 covers all non-web software, including:
- Desktop and mobile apps
- Software with a graphical or auditory user interface
- Assistive technologies
- Platform software like operating systems and user agents (e.g., browsers, media players)
It doesn't apply to:
- Web pages or software embedded in/rendered with web pages (see Clause 9)
- Command line interfaces (only mentioned informatively)
Clause 11.1-11.5 aligns with WCAG2ICT interpretations, but for software instead of web content.
Structure and Approach
Just like Clause 10 (documents), Clause 11 adapts WCAG 2.1 SCs to suit software contexts. It provides separate clauses for:
- Perceivable (11.1)
- Operable (11.2)
- Understandable (11.3)
- Robust (11.4)
- Caption/audio timing (11.5)
- Platform interoperability (11.6)
- User preferences (11.7)
- AT interoperability (11.8)
11.0 General Notes
- UAAG 2.0 is recommended for software that behaves like user agents.
- WCAG applies only to web content, so this clause takes care of standalone software.
- Success Criteria follow WCAG2ICT, but adapt "web page" to "software" or "user interface component".
11.6 Platform Accessibility Services
Software must expose UI components, text, and content structures via platform APIs (like MSAA, UIA, AX API). For example: Focusable components must be detectable via keyboard/AT, Labels must be exposed to screen readers.
11.7 User Preferences
Basically: Don't override OS/system-wide accessibility settings. Software should honor user settings for:
- Color, contrast, font size, screen orientation
- Keyboard, pointer, voice input
- Captions/subtitles
11.8 Assistive Technology Compatibility
Software must not interfere with AT functionality (like intercepting keyboard events, suppressing output). It must work well with assistive technologies like screen readers, magnifiers, speech recognition, etc. This includes:
- Text-to-speech
- Braille output
- Voice recognition (input)