What Changed In EN 301 549 Version 4.1.1?

Of course, I did not read and compare version 3.2.1 and version 4.1.1 myself. My friend Claude created a detailed change history for me, as shown below. I checked the result and made a few edits. I think we got a correct result. Here you go.

EN 301 549 v4.1.1 brings the standard in line with WCAG 2.2 and, more significantly, was revised specifically to bring it into alignment with the European Accessibility Act (Directive (EU) 2019/882). Here are the whole changes:

• WCAG alignment : Web, non-web document, and non-web software requirements (clauses 9, 10, 11) now reflect WCAG 2.2 instead of 2.1 — supporting both the EAA and the Web Accessibility Directive.
• EAA coverage : The standard now formally supports the EAA itself, not just the Web Accessibility Directive, with new conformity-evaluation tables added specifically for this purpose (Annex ZB, clause A.2).
• Real-Time Text expansion : RTT support gained new technical requirements (clause 6.2), tied to the EAA's requirement for electronic communications services (Annex I).
• Total Conversation : Combining voice, text, and video moved from a passing informative mention to a fully normative requirement (clause 6.7) — "total conversation" is named explicitly in the EAA text for electronic communications services.
• Emergency communication : Deepened with new scenarios covering roaming and cross-border use (clause 6.0), fulfilling the EAA's requirement for synchronized emergency communications to reach the appropriate emergency call center (PSAP).
• Hardware contrast : Hardware must now meet a minimum visual contrast standard (clause 8.8), required by the EAA's general product accessibility requirements.
• Kiosk/stationary ICT ergonomics : Precise new rules for screen height and control placement (clause 8.3), fulfilling the EAA's requirement to avoid operation modes needing excessive reach or strength.
• Closed functionality : Must now expose the purpose of input fields (clause 5.1.8), supporting the EAA's general requirement for multi-sensory product access.
• User preferences : Web pages and non-web documents themselves must now respect platform-level accessibility preferences (clauses 9.7 and 10.7), fulfilling the EAA's service-level requirement for adjustable font size, contrast, and spacing.
• Electronic Programme Guides : A brand-new scope area (clauses 12.4 and 12.5), added because the EAA explicitly requires EPGs for audiovisual media services to be accessible and to surface accessibility information like subtitles and audio description.