Links

The EN 301 549 adoption map shows where it is used, which includes many places outside Europe.

Version 4.1.0 (PDF link) of EN 301 549, the European standard used for WAD and from this version onwards also EAA conformance, was “adopted” by EU Member States.

(Source: ETSI timetable towards EN 301 549 publication)

There's lots of changes, the most significant for web teams:

• references to WCAG are now to WCAG 2.2.
• the “User Preferences” requirement has been reworded and spread out over 9.7, 10.7 and 11.7 (instead of just 11.7)
• authoring tools requirement in clause 11 moved to clause 5, and was made more specific. I also sneaked in examples in the authoring tool definition (my most tangible contribution lol).
• adds an EAA mapping in addition to the existing WAD mapping, so that it can be referred to as the standard to use to comply with EAA requirements, as soon as the European Journal refers to it for that purpose.

I blogged on the W3C site about the meetup we organised when the AB was in Rotterdam: CSS animations, human rights, and big accessibility at the AB Web Meetup | 2026 | Blog | W3C

The W3C published Privacy Principles as a Statement, meaning a document the Members approved.

It has definitions, meant to aid policy, as well as principles, to be more precise:

a set of privacy principles that should guide the development of the web as a trustworthy platform

(From: Privacy Principles)

What can we do to make apps for real time collaboration, like Google Docs, more accessible?

This month, W3C published a new document called CTAUR (Collaboration Tools Accessibility User Requirements). Previous docs in this ‘series’ include XAUR (on XR), NAUR (on natural language interfaces like voice agents and chatbots), SAUR (on synchronisation in media, like that of captions and video) and RAUR (on RTC). The Accessible Platform Architectures (APA) Working Group bas been busy in the last few years. Note, these are all non-normative.

CTAUR covers a number of aspects that go beyond WCAG:

• Real-time and asynchronous co-editing (including things like where are other people in the document currently)
• Annotation of content with comments
• Comparing revisions
• Suggested changes
• Access controls

For each, it describes users needs and corresponding requirements.

Hadley Beeman of the Technical Architecture Group:

After reading Google’s announcement that they no longer plan to deprecate third-party cookies, we wanted to make our position clear.

(From: Third-party cookies have got to go | 2024 | Blog | W3C)