<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.2.0">Jekyll</generator><link href="https://www.w3.org/WAI/feed.xml" rel="self" type="application/atom+xml" /><link href="https://www.w3.org/WAI/" rel="alternate" type="text/html" /><updated>2021-08-06T16:25:29+00:00</updated><id>https://www.w3.org/WAI/feed.xml</id><title type="html">Web Accessibility Initiative (WAI)</title><subtitle>The Website of the World Wide Web Consortium’s Web Accessibility Initiative.
</subtitle><author><name>W3C Web Accessibility Initiative (WAI)</name></author><entry><title type="html">RTC Accessibility User Requirements (RAUR) Note Published</title><link href="https://www.w3.org/WAI/news/2021-05-25/RAUR/" rel="alternate" type="text/html" title="RTC Accessibility User Requirements (RAUR) Note Published" /><published>2021-05-25T00:00:00+00:00</published><updated>2021-05-25T00:00:00+00:00</updated><id>https://www.w3.org/WAI/news/2021-05-25/RAUR</id><content type="html" xml:base="https://www.w3.org/WAI/news/2021-05-25/RAUR/">&lt;p&gt;&lt;a href=&quot;https://www.w3.org/TR/raur/&quot;&gt;RTC Accessibility User Requirements (RAUR)&lt;/a&gt; is published as a Working Group Note. Real-time communication (&lt;abbr&gt;RTC&lt;/abbr&gt;) provides real-time   peer to peer audio, video, and data exchange directly between supported   user agents. This enables instantaneous applications for video and audio   calls, text chat, file exchange, screen sharing, and gaming. RAUR describes various accessibility related user needs,   requirements, and scenarios for real-time communication (RTC)   applications. These user needs should drive accessibility requirements   in various related specifications and the overall architecture that   enables RTC.&lt;/p&gt;</content><author><name>W3C Web Accessibility Initiative (WAI)</name></author><summary type="html">RTC Accessibility User Requirements (RAUR) is published as a Working Group Note. Real-time communication (RTC) provides real-time peer to peer audio, video, and data exchange directly between supported user agents. This enables instantaneous applications for video and audio calls, text chat, file exchange, screen sharing, and gaming. RAUR describes various accessibility related user needs, requirements, and scenarios for real-time communication (RTC) applications. These user needs should drive accessibility requirements in various related specifications and the overall architecture that enables RTC.</summary></entry><entry><title type="html">Accessibility Translations: Getting the ‘Global’ in GAAD</title><link href="https://www.w3.org/WAI/news/2021-05-20/gaad/" rel="alternate" type="text/html" title="Accessibility Translations: Getting the ‘Global’ in GAAD" /><published>2021-05-20T00:00:00+00:00</published><updated>2021-05-20T00:00:00+00:00</updated><id>https://www.w3.org/WAI/news/2021-05-20/gaad</id><content type="html" xml:base="https://www.w3.org/WAI/news/2021-05-20/gaad/">&lt;p&gt;&lt;a href=&quot;https://www.w3.org/WAI/translations/&quot;&gt;All WAI Translations&lt;/a&gt; now lists translations in 35 languages. Thanks to the translators. (If you know anyone who might be interested in contributing to more accessibility translations, please point them to: &lt;a href=&quot;https://www.w3.org/WAI/about/translating/&quot;&gt;Translating WAI Resources&lt;/a&gt;)&lt;/p&gt;</content><author><name>W3C Web Accessibility Initiative (WAI)</name></author><summary type="html">All WAI Translations now lists translations in 35 languages. Thanks to the translators. (If you know anyone who might be interested in contributing to more accessibility translations, please point them to: Translating WAI Resources)</summary></entry><entry><title type="html">For Review: Specification for Spoken Presentation in HTML</title><link href="https://www.w3.org/WAI/news/2021-05-18/pronunciation/" rel="alternate" type="text/html" title="For Review: Specification for Spoken Presentation in HTML" /><published>2021-05-18T00:00:00+00:00</published><updated>2021-05-18T00:00:00+00:00</updated><id>https://www.w3.org/WAI/news/2021-05-18/pronunciation</id><content type="html" xml:base="https://www.w3.org/WAI/news/2021-05-18/pronunciation/">&lt;p&gt;&lt;a href=&quot;https://www.w3.org/TR/2021/WD-spoken-html-20210518/&quot;&gt;Specification for Spoken Presentation in HTML&lt;/a&gt; Working Draft is ready for review. This document is part of &lt;a href=&quot;https://www.w3.org/WAI/pronunciation/&quot;&gt;W3C work on pronunciation&lt;/a&gt; to provide normative specifications and best practices guidance so that   text-to-speech (TTS) synthesis can properly pronounce HTML content. This Draft specification describes two possible   technical approaches for author-controlled pronunciation. W3C is    seeking more input on these approaches, particularly from content   authors and implementors. Please send comments by &lt;strong&gt;18 June 2021&lt;/strong&gt;.&lt;/p&gt;</content><author><name>W3C Web Accessibility Initiative (WAI)</name></author><summary type="html">Specification for Spoken Presentation in HTML Working Draft is ready for review. This document is part of W3C work on pronunciation to provide normative specifications and best practices guidance so that text-to-speech (TTS) synthesis can properly pronounce HTML content. This Draft specification describes two possible technical approaches for author-controlled pronunciation. W3C is seeking more input on these approaches, particularly from content authors and implementors. Please send comments by 18 June 2021.</summary></entry><entry><title type="html">For Wide Review: WCAG 2.2 Working Draft</title><link href="https://www.w3.org/WAI/news/2021-05-13/wcag22/" rel="alternate" type="text/html" title="For Wide Review: WCAG 2.2 Working Draft" /><published>2021-05-13T00:00:00+00:00</published><updated>2021-05-13T00:00:00+00:00</updated><id>https://www.w3.org/WAI/news/2021-05-13/wcag22</id><content type="html" xml:base="https://www.w3.org/WAI/news/2021-05-13/wcag22/">&lt;p&gt;&lt;a href=&quot;https://www.w3.org/TR/WCAG22/&quot;&gt;WCAG 2.2 Working Draft&lt;/a&gt; is ready wide review before finalizing WCAG 2.2. This draft has 9 new &amp;ldquo;success criteria&amp;rdquo; (requirements) since WCAG 2.1. The new success criteria and changes since the previous 2.2 draft are introduced in &lt;a href=&quot;https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/&quot;&gt;What's New in WCAG 2.2&lt;/a&gt;. The new success criteria address user needs of people with cognitive or learning disabilities, users of mobile devices, and users of ebooks.   Please submit comments by 11 June 2021.&lt;/p&gt;</content><author><name>W3C Web Accessibility Initiative (WAI)</name></author><summary type="html">WCAG 2.2 Working Draft is ready wide review before finalizing WCAG 2.2. This draft has 9 new &amp;ldquo;success criteria&amp;rdquo; (requirements) since WCAG 2.1. The new success criteria and changes since the previous 2.2 draft are introduced in What's New in WCAG 2.2. The new success criteria address user needs of people with cognitive or learning disabilities, users of mobile devices, and users of ebooks. Please submit comments by 11 June 2021.</summary></entry><entry><title type="html">Making Content Usable for People with Cognitive and Learning Disabilities - Note Published</title><link href="https://www.w3.org/WAI/news/2021-04-29/COGA/" rel="alternate" type="text/html" title="Making Content Usable for People with Cognitive and Learning Disabilities - Note Published" /><published>2021-04-29T00:00:00+00:00</published><updated>2021-04-29T00:00:00+00:00</updated><id>https://www.w3.org/WAI/news/2021-04-29/COGA</id><content type="html" xml:base="https://www.w3.org/WAI/news/2021-04-29/COGA/">&lt;p&gt;&lt;a href=&quot;https://www.w3.org/TR/coga-usable/&quot;&gt;Making Content Usable for People with Cognitive and Learning Disabilities&lt;/a&gt; is a Working Group Note that helps you make web content, including applications, more accessible to more people. It provides informative &quot;supplemental guidance&quot; beyond the requirements of WCAG 2. It is not required for conformance to WCAG. To learn about this document and other W3C work on accessibility for people with cognitive and learning disabilities, see: &lt;a href=&quot;https://www.w3.org/WAI/cognitive/&quot;&gt;Cognitive Accessibility at W3C&lt;/a&gt;.&lt;/p&gt;</content><author><name>W3C Web Accessibility Initiative (WAI)</name></author><summary type="html">Making Content Usable for People with Cognitive and Learning Disabilities is a Working Group Note that helps you make web content, including applications, more accessible to more people. It provides informative &quot;supplemental guidance&quot; beyond the requirements of WCAG 2. It is not required for conformance to WCAG. To learn about this document and other W3C work on accessibility for people with cognitive and learning disabilities, see: Cognitive Accessibility at W3C.</summary></entry><entry><title type="html">Updated Resource: Curricula on Web Accessibility</title><link href="https://www.w3.org/WAI/news/2021-03-30/curricula/" rel="alternate" type="text/html" title="Updated Resource: Curricula on Web Accessibility" /><published>2021-03-30T00:00:00+00:00</published><updated>2021-03-30T00:00:00+00:00</updated><id>https://www.w3.org/WAI/news/2021-03-30/curricula</id><content type="html" xml:base="https://www.w3.org/WAI/news/2021-03-30/curricula/">&lt;p&gt;New Developer Modules are now published in the &lt;a href=&quot;https://www.w3.org/WAI/curricula/&quot;&gt;Curricula on Web Accessibility&lt;/a&gt;. This curricula provides a framework for creating courses on digital accessibility, for including accessibility in other courses, and for reviewing existing and proposed courses. The March 2021 publication includes: updated guidance in the &lt;a href=&quot;https://www.w3.org/WAI/curricula/&quot;&gt;Curricula overview page&lt;/a&gt;, updated &lt;a href=&quot;https://www.w3.org/WAI/curricula/foundation-modules/&quot;&gt;Foundation Modules&lt;/a&gt;, and new &lt;a href=&quot;https://www.w3.org/WAI/curricula/developer-modules/&quot;&gt;Developer Modules&lt;/a&gt;. The new modules focus on accessible markup and coding techniques, primarily for teaching front-end developers. The next modules will cover designing and authoring accessible digital content.&lt;/p&gt;</content><author><name>W3C Web Accessibility Initiative (WAI)</name></author><summary type="html">New Developer Modules are now published in the Curricula on Web Accessibility. This curricula provides a framework for creating courses on digital accessibility, for including accessibility in other courses, and for reviewing existing and proposed courses. The March 2021 publication includes: updated guidance in the Curricula overview page, updated Foundation Modules, and new Developer Modules. The new modules focus on accessible markup and coding techniques, primarily for teaching front-end developers. The next modules will cover designing and authoring accessible digital content.</summary></entry><entry><title type="html">WCAG 2.1 in Polish: Authorized Translation Published</title><link href="https://www.w3.org/WAI/news/2021-03-11/wcag-21-in-polish/" rel="alternate" type="text/html" title="WCAG 2.1 in Polish: Authorized Translation Published" /><published>2021-03-11T00:00:00+00:00</published><updated>2021-03-11T00:00:00+00:00</updated><id>https://www.w3.org/WAI/news/2021-03-11/wcag-21-in-polish</id><content type="html" xml:base="https://www.w3.org/WAI/news/2021-03-11/wcag-21-in-polish/">&lt;p&gt;&lt;a href=&quot;https://www.w3.org/Translations/WCAG21-pl/&quot;&gt;Wytyczne dla dostępności treści internetowych (WCAG) 2.1&lt;/a&gt;, the Polish Authorized Translation of &lt;a href=&quot;http://www.w3.org/WAI/intro/wcag&quot;&gt;Web Content Accessibility Guidelines (WCAG) 2.1&lt;/a&gt;, is now available, following completion of the &lt;a href=&quot;http://www.w3.org/2005/02/TranslationPolicy&quot;&gt;W3C Authorized Translations process&lt;/a&gt;. Other translations of WAI resources are listed in &lt;a href=&quot;https://www.w3.org/WAI/translations/&quot;&gt;All WAI Translations&lt;/a&gt;. WAI encourages translations in all languages. If you might be interesting in translating resources, see &lt;a href=&quot;https://www.w3.org/WAI/about/translating/&quot;&gt;Translating WAI Resources&lt;/a&gt;.&lt;/p&gt;</content><author><name>W3C Web Accessibility Initiative (WAI)</name></author><summary type="html">Wytyczne dla dostępności treści internetowych (WCAG) 2.1, the Polish Authorized Translation of Web Content Accessibility Guidelines (WCAG) 2.1, is now available, following completion of the W3C Authorized Translations process. Other translations of WAI resources are listed in All WAI Translations. WAI encourages translations in all languages. If you might be interesting in translating resources, see Translating WAI Resources.</summary></entry><entry><title type="html">For Review: W3C Accessibility Guidelines (WCAG) 3.0 First Working Draft</title><link href="https://www.w3.org/WAI/news/2021-01-21/WCAG3/" rel="alternate" type="text/html" title="For Review: W3C Accessibility Guidelines (WCAG) 3.0 First Working Draft" /><published>2021-01-21T00:00:00+00:00</published><updated>2021-01-21T00:00:00+00:00</updated><id>https://www.w3.org/WAI/news/2021-01-21/WCAG3</id><content type="html" xml:base="https://www.w3.org/WAI/news/2021-01-21/WCAG3/">&lt;p&gt;&lt;a href=&quot;https://www.w3.org/TR/wcag-3.0/&quot;&gt;W3C Accessibility Guidelines (WCAG) 3.0 First Public Working Draft&lt;/a&gt; is published for review. W3C Accessibility Guidelines (WCAG) 3 has several differences from Web Content Accessibility Guidelines (WCAG) 2.&lt;/p&gt;

&lt;p&gt;We encourage you to &lt;strong&gt;start by reading the &lt;a href=&quot;https://www.w3.org/WAI/wcag3&quot;&gt;WCAG 3 Introduction&lt;/a&gt; first&lt;/strong&gt; to get important background on WCAG 3 development, review guidance, and timeline.&lt;/p&gt;

&lt;p&gt;WCAG 3 is intended to be easier to understand and more flexible than WCAG 2. The flexibility is to address different types of web content, apps, and tools — as well as organizations and people with disabilities. This WCAG 3 Draft proposes a different name, scope, structure, and draft conformance model.&lt;/p&gt;

&lt;p&gt;We are seeking input from evaluators, developers, designers, project managers, policy makers, people with disabilities, and others — particularly on the structure and the draft conformance model. Additional review guidance is in the blog post &lt;a href=&quot;https://www.w3.org/blog/2021/01/wcag-3-fpwd/&quot;&gt;WCAG 3 FPWD Published&lt;/a&gt;. Please submit comments &lt;strong&gt;by 26 February 2021&lt;/strong&gt;.&lt;/p&gt;</content><author><name>W3C Web Accessibility Initiative (WAI)</name></author><summary type="html">W3C Accessibility Guidelines (WCAG) 3.0 First Public Working Draft is published for review. W3C Accessibility Guidelines (WCAG) 3 has several differences from Web Content Accessibility Guidelines (WCAG) 2.</summary></entry><entry><title type="html">Invitation: WAI-Tools Final Meeting, Online 26 January 2021</title><link href="https://www.w3.org/WAI/news/2021-01-07/WAI-Tools-meeting/" rel="alternate" type="text/html" title="Invitation: WAI-Tools Final Meeting, Online 26 January 2021" /><published>2021-01-07T00:00:00+00:00</published><updated>2021-01-07T00:00:00+00:00</updated><id>https://www.w3.org/WAI/news/2021-01-07/WAI-Tools-meeting</id><content type="html" xml:base="https://www.w3.org/WAI/news/2021-01-07/WAI-Tools-meeting/">&lt;p&gt;You are invited to the &lt;a href=&quot;https://www.w3.org/WAI/about/projects/wai-tools/final-open-meeting/&quot;&gt;WAI-Tools Final Open Meeting, Online 26 January 2021&lt;/a&gt;. The meeting is intended for web accessibility practitioners, evaluation and quality assurance tool vendors, website owners, European monitoring bodies, researchers, and users interested in large-scale monitoring of web accessibility. Agenda, logistics, and registration information is in the &lt;a href=&quot;https://www.w3.org/WAI/about/projects/wai-tools/final-open-meeting/&quot;&gt;meeting page&lt;/a&gt;. This meeting is free, and registration is required.&lt;/p&gt;</content><author><name>W3C Web Accessibility Initiative (WAI)</name></author><summary type="html">You are invited to the WAI-Tools Final Open Meeting, Online 26 January 2021. The meeting is intended for web accessibility practitioners, evaluation and quality assurance tool vendors, website owners, European monitoring bodies, researchers, and users interested in large-scale monitoring of web accessibility. Agenda, logistics, and registration information is in the meeting page. This meeting is free, and registration is required.</summary></entry><entry><title type="html">For Review: XR Accessibility User Requirements (XAUR) Updated Draft</title><link href="https://www.w3.org/WAI/news/2020-09-16/XAUR/" rel="alternate" type="text/html" title="For Review: XR Accessibility User Requirements (XAUR) Updated Draft" /><published>2020-09-16T00:00:00+00:00</published><updated>2020-09-16T00:00:00+00:00</updated><id>https://www.w3.org/WAI/news/2020-09-16/XAUR</id><content type="html" xml:base="https://www.w3.org/WAI/news/2020-09-16/XAUR/">&lt;p&gt;An updated Working Draft of &lt;a href=&quot;https://www.w3.org/TR/xaur/&quot;&gt;XR Accessibility User Requirements (XAUR)&lt;/a&gt; is now available for review. XAUR describes the needs of people with disabilities in virtual or immersive environments (XR). It includes requirements for XR to be accessible. XAUR is for designers and developers who are involved in creating XR experiences. It is also useful for anyone who wants to better understand XR accessibility. We would particularly like input on any user needs or requirements that are missing from this draft. For more information, see the &lt;a href=&quot;https://lists.w3.org/Archives/Public/public-wai-announce/2020OctDec/0000.html&quot;&gt;XAUR review e-mail&lt;/a&gt;.&lt;/p&gt;</content><author><name>W3C Web Accessibility Initiative (WAI)</name></author><summary type="html">An updated Working Draft of XR Accessibility User Requirements (XAUR) is now available for review. XAUR describes the needs of people with disabilities in virtual or immersive environments (XR). It includes requirements for XR to be accessible. XAUR is for designers and developers who are involved in creating XR experiences. It is also useful for anyone who wants to better understand XR accessibility. We would particularly like input on any user needs or requirements that are missing from this draft. For more information, see the XAUR review e-mail.</summary></entry></feed>