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]

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)

The WCAG 3 Working Draft update is ready for your review. For background and up-to-date information on W3C Accessibility Guidelines (WCAG) 3, please see:    WCAG 3 Introduction    https://lnkd.in/d8mqtuFk The Accessibility Guidelines Working Group (AG WG) published an updated WCAG 3 Working Draft at:    https://lnkd.in/gNMZ9_g This draft includes potential outcomes that we are exploring. The final set of outcomes in WCAG 3 will be different from this draft. Outcomes will be edited, added, combined, and removed. The purpose of this draft is to: * better understand the scope of user needs and how they could be addressed in an accessibility standard, * request assistance in identifying gaps, and * request assistance locating and conducting research to validate or invalidate the drafted outcomes. Some of the outcomes are marked as needing research. We are particularly interested in assistance identifying or conducting research to support or refute them. For your review: When reviewing this update, please focus on the Guidelines section. We did not make changes to conformance related sections. Please consider the following questions when reviewing the outcomes in this draft: * What outcomes needed to make web content accessible are missing? * What research supports or refutes these outcomes? * Are any of these outcomes out of scope for accessibility standards? If so, please explain why. To provide input, please file GitHub issues at:    https://lnkd.in/eyd-HefV Or, if you are unable to use GitHub, send email to public-agwg-comments@w3.org Please create separate GitHub issues or email messages for each topic (rather than putting multiple topics in a single issue or email). Thank you in advance for your contributions to WCAG 3. This draft reflects ongoing work on WCAG 3. If you have questions or concerns, please contact the AG Chairs via email to: group-ag-chairs@w3.org

We're #hiring a new Web Technical Specialist in United States. Apply today or share this post with your network.

We're #hiring a new Web Technical Specialist in United States. Apply today or share this post with your network.

W3C WAI open positions! We are excited to announce two immediate job openings to join the highly-collaborative international World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI) team: * Accessibility Content Specialist for full-time remote work on digital accessibility materials. The application deadline is 2 April 2024. See https://lnkd.in/g2JXQP4i * Web Technical Specialist for full-time remote work in the USA on a project developing the technical infrastructure to support digital accessibility materials development and delivery. The application deadline is 13 April 2024. See https://lnkd.in/ggdAyH2G We seek diversity and strongly encourage applications from individuals from all identities and backgrounds.

It's almost time -- the Ability Summit is Thursday 7 March 2024. It's free online. https://lnkd.in/gRFTftrE At 12:40 pm PT / 20:40 UTC, W3C Web Accessibility Initiative (WAI) is participating in Build - Empowering the Tech Community for an Accessible Future. We'll share how our international Web Consortium works with organizations and individuals around the world to develop accessibility standards *and* a wide range of free supporting resources to help you make digital technology accessible. You'll also hear a bit about lived experiences with disabilities and digital technology from Daniel Montalvo and Shawn Lawton Henry.