W3C Web Accessibility Initiative (WAI)

We encourage you to subscribe to Get WAI News by e-mail or social media, as you prefer. See: https://lnkd.in/gSUkBWMS [ALT: W3C Web Accessibility Initiative WAI. Accessibility: Essential for some, useful for all. icons of hand, eye, brain, ear, voice, body]

WCAG2ICT is Guidance on Applying Web Content Accessibility Guidelines (WCAG) 2 to Non-Web Information and Communications Technologies (ICT). WCAG2ICT describes how WCAG principles, guidelines, and success criteria can be applied to non-web ICT, specifically to documents and software. Today we published the updated the WCAG2ICT W3C Group Note that includes guidance for WCAG 2.0, 2.1, and 2.2 success criteria and glossary terms. 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 the WCAG2ICT Overview at https://lnkd.in/gA_mfbTY

Stay Informed on WCAG 2.2 Updates at M-Enabling Summit2024! Following the keynote by W3C CEO Seth Dobbs, join us for a crucial session on the latest updates to WCAG 2.2. This presentation, led by Shawn Lawton Henry, WAI Program Lead at W3C, will provide a comprehensive overview of the new standards. Engage in a Town Hall Q&A with the W3C-WAI team to dive deeper into how these updates will impact web accessibility. Speaker: Shawn Henry - Web Accessibility Initiative (WAI) Program Lead, W3C For more Information, visit: https://lnkd.in/gwkubidi Register here: https://lnkd.in/eduDVw6A #WCAG #WebAccessibility #mEnabling24

In case you missed this announcement: W3C CEO Seth Dobbs to Deliver Keynote at M-Enabling Summit 2024! Seth Dobbs, CEO of the World Wide Web Consortium (W3C), will deliver the keynote address at the 12th Annual M-Enabling Summit. Event Details: Date: October 15-17, 2024 Location: Washington, DC Theme: "Transformations, Disruptions, and Opportunities for Digital Accessibility" Why Attend: Stay ahead of accessibility trends, learn from global digital inclusion innovators and Network with industry leaders Early Bird Savings: 1. Private Sector: Save $150 2. NGOs: Save $100 3. IAAP members: Additional $75 off For more information about #mEnabling24, visit our website: https://m-enabling.com/ Don't wait, secure your spot now and save. Register now: https://lnkd.in/esg2f5Rv IAAP EU IAAP Nordic IAAP D-A-CH IAAP UK Chapter IAAP India Chapter IAAP MEXICO CHAPTER G3ict - The Global Initiative for Inclusive ICTs IAAP - International Association of Accessibility Professionals #mEnabling24 #DigitalAccessibility #WebAccessibility

Stay Informed on WCAG 2.2 Updates at M-Enabling Summit2024! Following the keynote by W3C CEO Steve Dobbs, join us for a crucial session on the latest updates to WCAG 2.2. This presentation, led by Shawn Lawton Henry, WAI Program Lead at W3C, will provide a comprehensive overview of the new standards. Engage in a Town Hall Q&A with the W3C-WAI team to dive deeper into how these updates will impact web accessibility. Speaker: Shawn Henry - Web Accessibility Initiative (WAI) Program Lead, W3C For more Information, visit: https://lnkd.in/gwkubidi Register here: https://lnkd.in/esg2f5Rv #WCAG #WebAccessibility #mEnabling24

W3C CEO Seth Dobbs to Deliver Keynote at M-Enabling Summit 2024 We're very excited to announce Seth Dobbs, CEO of the World Wide Web Consortium (W3C), as our Keynote Speaker for the 12th Annual M-Enabling Summit. Don't miss this opportunity to gain invaluable insights on the future of web accessibility from a true industry leader. 📅 October 15-17, 2024 | Washington, DC 🏷️ Early Bird Registration Now Open! Join us for "Transformations, Disruptions, and Opportunities for Digital Accessibility." This premier event brings together global innovators in digital inclusion. For more information about the event, visit our website: https://m-enabling.com/ Early Bird Savings: •    Private Sector attendees save $150 •    NGOs save $100 from their already reduced registration fee •    IAAP members can save an additional $75. Email info@accessibilityassociation.org for your discount code Secure your spot today and save! Register now: https://lnkd.in/esg2f5Rv IAAP EU IAAP Nordic IAAP D-A-CH IAAP UK Chapter IAAP India Chapter IAAP MEXICO CHAPTER G3ict - The Global Initiative for Inclusive ICTs IAAP - International Association of Accessibility Professionals #mEnabling24 #DigitalAccessibility #WebAccessibility

W3C WAI invites you to comment on a Draft W3C Group Note: Collaboration Tools Accessibility User Requirements https://lnkd.in/gygX7m69 This is the planned last draft before we publish it as a W3C Group Note.  Overview: Collaboration Tools Accessibility User Requirements ("CTAUR") covers accessibility user needs, requirements, and scenarios for collaborative content creation and development tools. It addresses features and capabilities unique to interactive, real-time, or asynchronous collaborative applications. This includes co-editing, revision tracking, and in-line comments. The solutions identified in this document are intended to influence the evolution of future accessibility guidelines, technical specifications, or features of collaboration tools and assistive technologies. They are relevant to software developers who contribute to developing the collaborative experience. (the acronym CTAUR we pronounce as: see-tower) Seeking input: We encourage broad review from a cross-disability perspective. This draft incorporates substantial revisions made in response to comments on the previous Working Drafts by various stakeholders, including W3C's Cognitive and Learning Disabilities Accessibility Task Force (COGA). These comments led to adding significant requirements and clarifying the document's scope. We especially request comments on the following issues and questions: * We came to understand the collaborative editing environment in terms of managing complexity. We observed that many word processing, spread sheet, software development, and media development environments are themselves intrinsically complex. To this, collaborative tooling adds a further layer of complexity: the management of proposed, accepted, and rejected edits from multiple participants. Does this framing make sense? Is its importance clearly communicated by the document? * Do we delineate between the content creation elements of software and those relating to managing collaboration sufficiently? Is the distinction meaningfully communicated? Do you agree with this scoping? * We inserted a section in our Introduction on Social Considerations. This brief section is included to communicate which stakeholders we regard responsible for which aspects of collaborative efforts. Is this helpful? * We created a glossary to define the term "WYSIWYG" in response to a comment. Are there other terms we use you would like defined in the glossary? Comments: To comment, please open a new issue in the document's GitHub repository: https://lnkd.in/gejkN6JU Please create separate GitHub issues for each topic, rather than commenting on multiple topics in a single issue. If it's not feasible for you to use GitHub, send comments in e-mail to: public-rqtf@w3.org Please: * put your comments in the body of the message, not as an attachment * start your e-mail subject line with: [CTAUR] Please send comments by 30 September 2024. Thank you.

📣 We are opening today the W3C TPAC Inclusion Fund applications, until 31 July. This is designed for people from an under-represented group who wouldn’t be able to attend or meaningfully contribute to TPAC without financial support. We are grateful to this year’s sponsors W3C and an anonymous donor. https://lnkd.in/eACWnWas #w3ctpac #w3c #inclusion #diversity #webstandards

W3C WAI encourages you to review the updated Draft W3C Group Note:     Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)     https://lnkd.in/g6J875A4 We expect this document will impact future ICT standards worldwide. This is the planned last draft before we publish it as a W3C Group Note. Overview: WCAG2ICT provides guidance on applying WCAG 2 to non-web documents and software. This draft includes guidance for WCAG 2.0, 2.1, and 2.2 success criteria and glossary terms. For an introduction to WCAG2ICT, see:    WCAG2ICT Overview    https://lnkd.in/gA_mfbTY For review: We would particularly like your comments on: * Guidance for new and changed WCAG 2.2 success criteria and glossary definitions listed in the Comparison with the 2013 WCAG2ICT Note section * Updates to the Comments on Closed Functionality and Appendix A: Success Criteria Problematic for Closed Functionality sections * Sections with Editor’s notes that pose specific questions or request specific input Comments: To comment, please open a new issue in the WCAG2ICT GitHub repository:       https://lnkd.in/gj6unYMh Create separate GitHub issues for each topic, rather than commenting on multiple topics in a single issue. If it's not feasible for you to use GitHub, send comments in e-mail to: public-wcag2ict-comments@w3.org Please put your comments in the body of the message, not as an attachment. Start your e-mail subject line with: [Public Comment] Please send comments by 6 August 2024. If you need more time, please request an extension by sending an e-mail to public-wcag2ict-comments@w3.org Thank you in advance for your review.

"Accessibility: It's about people" is illustrated in W3C WAI's updated resource:    How People with Disabilities Use the Web   🎦 New videos and updated user stories ('personas') introduce how disabled people use digital technology. The multi-page resource describes tools and approaches that disabled people use to interact with technology and it covers barriers that people experience because of inaccessible digital technology. The resource helps developers, designers, content creators, and others understand the reasons behind creating accessible digital products. To quote the new videos: Whatever your role, "You can help make technology accessible to me." You are welcome to use the videos in your presentations, training, etc. per Using WAI Material: Permission to Use with Attribution.   (links in comments)