Tools for collaborative development of documents, code, and more need to be accessible to people with disabilities. Here to help with that is:
Collaboration Tools Accessibility User Requirements https://www.w3.org/TR/ctaur/
Today we published it as a W3C Group Note. We've taken to referring to it as CTAUR pronounced 'see-tower'.
For more accessibility user requirements, see Digital Accessibility User Requirements https://www.w3.org/WAI/research/user-requirements/
=> More informations about this toot | View the thread
WCAG 3 Draft for review:
An updated W3C Accessibility Guidelines (WCAG) 3.0 Working Draft is available for review. For a summary of changes, new content for review, and how to comment, see the WCAG 3 Introduction section 'Status: In-progress drafts' at https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/#status-in-progress-drafts
(Note that WCAG 3 is years away from being complete. For information on the current Web Content Accessibility Guidelines (WCAG) 2 standard, see the WCAG 2 Overview. https://www.w3.org/WAI/standards-guidelines/wcag/ )
=> More informations about this toot | View the thread
Today we published the updated WCAG2ICT for WCAG 2.0, 2.1, and 2.2.
WCAG2ICT is Guidance on Applying Web Content Accessibility Guidelines (WCAG) 2 to Non-Web Information and Communications Technologies (ICT).
WCAG2ICT has been a key resource for including WCAG in ICT accessibility regulation, legislation, and standards around the world. This update facilitates further adoption of WCAG 2.1 and WCAG 2.2 in non-web contexts.
To learn more, start from https://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/
=> More informations about this toot | View the thread
=> This profile with reblog | Go to wai@w3c.social account This content has been proxied by September (3851b).Proxy Information
text/gemini