CINXE.COM

<!DOCTYPE html> <html class="no-js" lang="en" dir="ltr" prefix="og: http://ogp.me/ns#"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <script> document.documentElement.className = document.documentElement.className.replace('no-js', 'has-js'); function downloadJSAtOnload() { var element = document.createElement("script"); element.src = "/WAI/assets/scripts/main.js?1732321439590790613"; document.body.appendChild(element); } window.addEventListener("load", downloadJSAtOnload, false); </script> <link rel="stylesheet" href="/WAI/assets/css/style.css?1732321439590790613"> <title> WCAG 3 Introduction | Web Accessibility Initiative (WAI) | W3C</title> <meta name="generator" content="Jekyll v4.3.3" /> <meta property="og:title" content="WCAG 3 Introduction" /> <meta name="author" content="W3C Web Accessibility Initiative (WAI)" /> <meta property="og:locale" content="en" /> <meta name="description" content="Introduces the W3C Accessibility Guidelines (WCAG) 3.0 Working Draft. WCAG documents explain how to make the web more accessible to people with disabilities." /> <meta property="og:description" content="Introduces the W3C Accessibility Guidelines (WCAG) 3.0 Working Draft. WCAG documents explain how to make the web more accessible to people with disabilities." /> <link rel="canonical" href="https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/" /> <meta property="og:url" content="https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/" /> <meta property="og:site_name" content="Web Accessibility Initiative (WAI)" /> <meta property="og:image" content="https://www.w3.org/WAI/content-images/wcag/wcag3_social.png" /> <meta property="og:type" content="website" /> <meta name="twitter:card" content="summary_large_image" /> <meta property="twitter:image" content="https://www.w3.org/WAI/content-images/wcag/wcag3_social.png" /> <meta property="twitter:title" content="WCAG 3 Introduction" /> <meta name="twitter:site" content="@w3c_wai" /> <meta name="twitter:creator" content="@W3C Web Accessibility Initiative (WAI)" /> <script type="application/ld+json"> {"@context":"https://schema.org","@type":"WebPage","author":{"@type":"Person","name":"W3C Web Accessibility Initiative (WAI)"},"description":"Introduces the W3C Accessibility Guidelines (WCAG) 3.0 Working Draft. WCAG documents explain how to make the web more accessible to people with disabilities.","headline":"WCAG 3 Introduction","image":"https://www.w3.org/WAI/content-images/wcag/wcag3_social.png","url":"https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/"}</script>  <link rel="alternate" type="application/rss+xml" href="/WAI/feed.xml"> </head> <body id="top" class="page-wcag-3-introduction "> <nav aria-label="Skip Link and Language Selector" id="controls" class="default-grid"> <ul> <li><a href="#main">Skip to Content</a></li> <li class="opt"> <a href="/WAI/meta/customize/">Change Text Size or Colors</a> </li> <li class="opt"> <a href="/WAI/translations/">All Translations <svg focusable="false" aria-hidden="true" class="icon-translations "><use xlink:href="/WAI/assets/images/icons.svg#icon-translations"></use></svg></a> </li> </ul></nav> <header id="site-header" class="default-grid with-gap"> <div class="logos"> <a lang="en" class="home w3c" href="https://www.w3.org/"> <svg role="img" aria-label="W3C" viewBox="0 0 68 34" xmlns="http://www.w3.org/2000/svg"><g><path d="m16.117 1.006 5.759 19.58 5.759-19.58h4.17 11.444v1.946l-5.879 10.128c2.065.663 3.627 1.868 4.686 3.615 1.059 1.748 1.589 3.799 1.589 6.155 0 2.914-.775 5.363-2.324 7.348s-3.555 2.978-6.017 2.978c-1.854 0-3.469-.589-4.845-1.767-1.377-1.178-2.396-2.773-3.058-4.786l3.256-1.35c.477 1.218 1.106 2.178 1.887 2.879.781.702 1.701 1.052 2.76 1.052 1.112 0 2.052-.622 2.82-1.866.768-1.245 1.152-2.74 1.152-4.489 0-1.933-.411-3.429-1.231-4.488-.954-1.244-2.45-1.867-4.489-1.867h-1.588v-1.906l5.56-9.612h-6.712l-.382.65-8.163 27.548h-.397l-5.958-19.937-5.957 19.937h-.397l-9.53-32.168h4.17l5.759 19.58 3.892-13.185-1.906-6.395z"/><path d="m64.92 1.006c-.819 0-1.554.295-2.111.861-.591.6-.92 1.376-.92 2.178s.313 1.545.887 2.128c.583.591 1.334.912 2.145.912.793 0 1.562-.321 2.161-.903.574-.557.887-1.3.887-2.136 0-.811-.321-1.57-.878-2.136-.584-.592-1.344-.904-2.171-.904zm2.643 3.065c0 .701-.271 1.351-.768 1.832-.524.507-1.174.777-1.892.777-.675 0-1.342-.278-1.84-.785s-.777-1.157-.777-1.849.287-1.368.802-1.891c.481-.49 1.131-.751 1.84-.751.726 0 1.376.271 1.883.785.49.489.752 1.147.752 1.882zm-2.559-1.807h-1.3v3.445h.65v-1.469h.642l.701 1.469h.726l-.769-1.57c.498-.102.785-.439.785-.929 0-.625-.472-.946-1.435-.946zm-.118.422c.608 0 .886.169.886.591 0 .405-.278.549-.87.549h-.549v-1.14z"/><path d="m59.807.825.676 4.107-2.391 4.575s-.918-1.941-2.443-3.015c-1.285-.905-2.122-1.102-3.431-.832-1.681.347-3.587 2.357-4.419 4.835-.995 2.965-1.005 4.4-1.04 5.718-.056 2.113.277 3.362.277 3.362s-1.452-2.686-1.438-6.62c.009-2.808.451-5.354 1.75-7.867 1.143-2.209 2.842-3.535 4.35-3.691 1.559-.161 2.791.59 3.743 1.403 1 .854 2.01 2.721 2.01 2.721z"/><path d="m60.102 24.063s-1.057 1.889-1.715 2.617c-.659.728-1.837 2.01-3.292 2.651s-2.218.762-3.656.624c-1.437-.138-2.772-.97-3.24-1.317s-1.664-1.369-2.34-2.322-1.733-2.859-1.733-2.859.589 1.91.958 2.721c.212.467.864 1.894 1.789 3.136.863 1.159 2.539 3.154 5.086 3.604 2.547.451 4.297-.693 4.73-.97s1.346-1.042 1.924-1.66c.603-.645 1.174-1.468 1.49-1.962.231-.36.607-1.092.607-1.092z"/></g></svg> </a> <a lang="en" class="home" href="/WAI/"> <span class="wai"><span class="wa">Web Accessibility</span> <span class="i"><span class="initieative">Initiative</span> <span>WAI</span></span></span> </a> <div class="claim"> <span>Strategies, standards, resources to make the Web accessible to people with disabilities</span> </div> <button class="button button-menu" aria-haspopup="true" aria-expanded="false" id="openmenu"><span><svg focusable="false" aria-hidden="true" class="icon-menu "><use xlink:href="/WAI/assets/images/icons.svg#icon-menu"></use></svg> Menu</span></button> </div> <div class="navigations"> <nav class="metanav" aria-label="Meta & Search" lang="en"> <ul> <li><a href="/WAI/about/participating/">Get Involved</a></li> <li><a href="/WAI/about/">About W3C WAI</a></li> <li> <form action="/WAI/search/" role="search"> <div> <label for="header-search"> <span class="visuallyhidden">Search:</span> <input id="header-search" type="search" name="q" placeholder="Search" aria-label="Search"> </label> <button class="button button-icon button-nobg button-noborder"><span><svg focusable="false" aria-label="Submit Search" class="icon-search "><use xlink:href="/WAI/assets/images/icons.svg#icon-search"></use></svg></span></button> </div> </form> </li> </ul> </nav> </div> </header><nav class="mainnav" aria-label="Main" lang="en"><ul><li><a lang="en" href="/WAI/fundamentals/"><span>Accessibility Fundamentals</span></a></li><li><a lang="en" href="/WAI/planning/"><span>Planning & Policies</span></a></li><li><a lang="en" href="/WAI/design-develop/"><span>Design & Develop</span></a></li><li><a lang="en" href="/WAI/test-evaluate/"><span>Test & Evaluate</span></a></li><li><a lang="en" href="/WAI/teach-advocate/"><span>Teach & Advocate</span></a></li><li><a lang="en" href="/WAI/standards-guidelines/"><span>Standards/<wbr>Guidelines</span></a></li></ul></nav><nav class="default-grid breadcrumb" aria-label="Breadcrumb" lang="en"> <ul style="align-self: center;"> <li><a href="/WAI/" lang="en">Home</a></li><li><a lang="en" href="/WAI/standards-guidelines/"><span>Standards/<wbr>Guidelines</span></a></li><li><a lang="en" href="/WAI/standards-guidelines/wcag/wcag3-intro/" aria-current="page"><span>WCAG 3 Draft</span></a></li></ul> </nav> <div class="default-grid with-gap leftcol"> <div class="sidenav"><nav class="sn-contents" aria-label="Secondary"> <ul class="sidenav--list"> <li> <a lang="en" href="/WAI/standards-guidelines/" class="page-link"><span>Standards/<wbr>Guidelines</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/wcag/" class="page-link"><span>Web Content – WCAG 2</span></a><ul><li> <a lang="en" href="https://www.w3.org/WAI/WCAG21/quickref/" class="page-link"><span>How to Meet WCAG 2 (Quick Reference)</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/wcag/glance/" class="page-link"><span>At a Glance</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/wcag/docs/" class="page-link"><span>The Documents</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/wcag/non-web-ict/" class="page-link"><span>Applying to Non-Web ICT</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/wcag/new-in-22/" class="page-link"><span>New in 2.2</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/wcag/new-in-21/" class="page-link"><span>New in 2.1</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/wcag/translations/" class="page-link"><span>Translations</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/wcag/commenting/" class="page-link"><span>Commenting</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/wcag/conformance-logos/" class="page-link"><span>Conformance Logos</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/wcag/faq/" class="page-link"><span>FAQ</span></a></li></ul></li><li> <a lang="en" href="/WAI/standards-guidelines/wcag/wcag3-intro/" aria-current="page" class="page-link"><span>WCAG 3 Draft</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/atag/" class="page-link"><span>Authoring Tool Accessibility Guidelines (ATAG) Overview</span></a><ul><li> <a lang="en" href="/WAI/standards-guidelines/atag/glance/" class="page-link"><span>At a Glance</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/atag/education/" class="page-link"><span>For LMS</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/atag/no-code/" class="page-link"><span>For No-Code Tools</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/atag/social-media/" class="page-link"><span>For Social Media Platforms</span></a></li></ul></li><li> <a lang="en" href="/WAI/standards-guidelines/uaag/" class="page-link"><span>User Agents – UAAG</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/aria/" class="page-link"><span>WAI-ARIA</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/evaluation/" class="page-link"><span>Evaluation – ACT & EARL</span></a><ul><li> <a lang="en" href="/WAI/standards-guidelines/act/" class="page-link"><span>Accessibility Conformance Testing – ACT</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/earl/" class="page-link"><span>Evaluation and Report Language – EARL</span></a></li></ul></li><li> <a lang="en" href="/WAI/adapt/" class="page-link"><span>WAI-Adapt</span></a></li><li> <a lang="en" href="/WAI/pronunciation/" class="page-link"><span>Pronunciation</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/harmonization/" class="page-link"><span>Standards Harmonization is Essential</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/w3c-process/" class="page-link"><span>W3C Process for Developing Standards</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/linking/" class="page-link"><span>Referencing and Linking to Standards</span></a></li><li> <a lang="en" href="/WAI/cognitive/" class="page-link"><span>Cognitive Accessibility at W3C</span></a></li><li> <a lang="en" href="/WAI/standards-guidelines/mobile/" class="page-link"><span>Mobile Accessibility at W3C</span></a></li></ul></nav> </div> <main id="main" lang="en"> <header> <h1> WCAG 3 Introduction </h1></header> <aside class="box box-full"><header class="box-h box-h-full"> <h2> Summary </h2></header><div class="box-i"> <p>Many aspects of W3C Accessibility Guidelines (WCAG) 3 are in an exploratory phase, and will change. We published an updated <a href="https://www.w3.org/TR/wcag-3.0/">WCAG 3 Working Draft</a> on 16 May 2024.</p> <p>WCAG 3 will have similar fundamental and specific accessibility requirements as WCAG 2. WCAG 3 will have a different structure, different conformance model, and broader scope.</p> <p>Please share this page as the starting point for official information about WCAG 3 now and in the future. short link: w3.org/WAI/wcag3</p> </div></aside> <nav class="box box-simple box-simple" aria-labelledby="tocheading" id="toc"> <header id="tocheading" class="box-h box-h-simple box-h-simple"> Page Contents</header> <div class="box-i"> <ul id="markdown-toc"> <li><a href="#status-exploratory-draft" id="markdown-toc-status-exploratory-draft">Status: Exploratory Draft</a> <ul> <li><a href="#for-your-review" id="markdown-toc-for-your-review">For your review</a></li> <li><a href="#status-of-sections" id="markdown-toc-status-of-sections">Status of Sections</a></li> </ul> </li> <li><a href="#wcag-3-draft-approach" id="markdown-toc-wcag-3-draft-approach">WCAG 3 Draft Approach</a> <ul> <li><a href="#compare" id="markdown-toc-compare">Some Similar, Some Different</a></li> <li><a href="#structure" id="markdown-toc-structure">Structure</a></li> <li><a href="#model" id="markdown-toc-model">Draft Conformance Model</a></li> </ul> </li> <li><a href="#development" id="markdown-toc-development">Development</a> <ul> <li><a href="#timeline" id="markdown-toc-timeline">Timeline</a></li> <li><a href="#wcag-3-name-formerly-silver-project" id="markdown-toc-wcag-3-name-formerly-silver-project">WCAG 3 Name (formerly “Silver” project)</a></li> <li><a href="#who-develops-wcag-3" id="markdown-toc-who-develops-wcag-3">Who Develops WCAG 3</a></li> </ul> </li> </ul> </div> </nav> <h2 class="no_toc" id="introduction">Introduction</h2> <p>WCAG 3 is currently an incomplete draft. WCAG 3 is intended to develop into a W3C Standard <strong>in a few years</strong>. The current standard, Web Content Accessibility Guidelines (WCAG 2), is introduced in the <a href="/WAI/standards-guidelines/wcag/">WCAG 2 Overview</a>.</p> <p>The WCAG 3 documents will explain how to make the web more accessible to people with disabilities. WCAG 3 applies to web content, apps, tools, publishing, and emerging technologies on the web.</p> <p>We will update this page regularly as work on the WCAG 3 Draft progresses.</p> <h2 id="status-exploratory-draft">Status: Exploratory Draft</h2> <p>The May 2024 <a href="https://www.w3.org/TR/wcag-3.0/">WCAG 3 Working Draft</a> includes <strong>potential</strong> 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.</p> <p>The purpose of this draft is to:</p> <ul> <li>better understand the scope of user needs and how they could be addressed in an accessibility standard,</li> <li>request assistance in identifying gaps, and</li> <li>request assistance locating and conducting research to validate or invalidate the drafted outcomes.</li> </ul> <p>Some of the outcomes are marked as needing research. We are particularly interested in assistance identifying or conducting research to support or refute them.</p> <h3 id="for-your-review">For your review</h3> <p>When reviewing this update, please focus on the Guidelines section. We did not make changes to conformance related sections.</p> <p>Please consider the following questions when reviewing the outcomes in this draft:</p> <ul> <li>What outcomes needed to make web content accessible are missing?</li> <li>What research supports or refutes these outcomes?</li> <li>Are any of these outcomes out of scope for accessibility standards? If so, please explain why.</li> </ul> <p>To provide input, please file GitHub issues at: <a href="https://github.com/w3c/wcag3/issues">https://github.com/w3c/wcag3/issues</a><br /> Or, if you are unable to use GitHub, send email to public-agwg-comments@w3.org</p> <p>Please create separate GitHub issues or email messages for each topic (rather than putting multiple topics in a single issue or email).</p> <h3 id="status-of-sections">Status of Sections</h3> <p>Each normative section has a status that indicates how far along in the development process this section is, how ready it is for experimental adoption, and what kind of feedback we are looking for.</p> <ul> <li><strong>Placeholder:</strong> This content is temporary. It shows the type of content or section to expect. Placeholder text will be replaced. It is hidden by default in the Editor’s draft. No feedback is needed on placeholder content.</li> <li><strong>Exploratory:</strong> The Working Group is exploring what direction to take with this section. This content is not refined; details and definitions may be missing. It is hidden by default in the Editor’s draft. We invite feedback on the proposed direction.</li> <li><strong>Developing:</strong> There is rough agreement on what is needed for this section, although not all high-level concerns have been settled. Details are included, yet they are not all agreed on. We invite general feedback on how understandable, usable, and reasonable the section is generally.</li> <li><strong>Refining:</strong> The Working Group has reach consensus on this section. It is ready for broad public review and experimental adoption. We seek feedback on feasibility and issues with implementations.</li> <li><strong>Mature:</strong> The Working Group thinks this content is ready for the final standard. Feedback should be focused on edge case scenarios the Working Group might not have anticipated.</li> </ul> <p><img src="/WAI/content-images/wcag/dialogs2.svg" alt="" style="float: right; margin-left: 2rem; width: 30%; max-width: 220px" /></p> <p><strong>There are substantial open issues that are still being discussed, particularly about testing and conformance.</strong></p>  <h2 id="wcag-3-draft-approach">WCAG 3 Draft Approach</h2> <p><img src="/WAI/content-images/wcag/brain-icon.svg" alt="" style="float: right; margin-left: 2rem; width: 30%; max-width: 220px" /></p> <h3 id="compare">Some Similar, Some Different</h3> <p><strong>Goals</strong> for WCAG 3 include:</p> <ul> <li>be easier to understand</li> <li>cover more user needs, including more needs of people with cognitive disabilities</li> <li>be flexible to address different types of web content, apps, tools, and organizations</li> </ul> <p>WCAG 3 is <strong>similar</strong> to previous versions in some ways. It has similar:</p> <ul> <li>goal of providing guidance on making web content and apps accessible to people with disabilities</li> <li>fundamental and specific accessibility requirements</li> </ul> <p>WCAG 3 is very <strong>different</strong> from previous versions in some ways. It has:</p> <ul> <li>different structure</li> <li>different conformance model</li> <li>broader scope, beyond just web content</li> </ul> <h3 id="structure">Structure</h3> <p>This WCAG 3 draft has:</p> <ul> <li><strong>Guidelines</strong> <ul> <li>Solutions to accessibility problems</li> <li>More <strong>granular</strong> than the guidelines in WCAG 2</li> <li>Each guideline has outcomes</li> </ul> </li> <li><strong>Outcomes</strong> <ul> <li>Verifiable statements</li> <li>Similar to <strong>success criteria</strong> in WCAG 2</li> <li>More granular and more focused on the desired results than the technical means for achieving them<br />(More <em>granular</em> means they are more specific, instead of broad. That generally makes them simpler. It also means there will be more of WCAG 3 outcomes than WCAG 2 success criteria.)</li> </ul> </li> <li><strong>Assertions</strong> <ul> <li>Formal claim of fact, attributed to a person or organization</li> <li>Assertions in WCAG 3 state that an organization has completed a procedure that can improve accessibility</li> <li>Example procedures include usability testing, assistive technology testing, and plain language reviews</li> <li>Assertions are used when the results of the same usability would be very different between testers</li> </ul> </li> </ul>  <p>WCAG 3 supporting material includes:</p> <ul> <li><strong>Methods</strong> <ul> <li>Technology-specific ways to achieve an outcome</li> <li>Tests for the outcome</li> <li>Similar to <strong>Techniques</strong> for WCAG 2</li> </ul> </li> <li><strong>How-To documents</strong> <ul> <li>Explain more about each guideline, such as how it addresses accessibility needs </li> <li>Information for designers, developers, people new to accessibility, and project planners</li> <li>Similar to the <strong>Understanding</strong> documents for WCAG 2</li> </ul> </li> <li><strong>Functional categories</strong> of <strong>functional needs</strong> <ul> <li>Categorized list of needs of people with disabilities</li> </ul> </li> </ul> <h3 id="model">Draft Conformance Model</h3> <p>The <em>conformance model</em> is the way to determine and communicate how well a website (or app, tool, etc.) meets WCAG. The conformance model in this draft of WCAG 3 will be very different from WCAG 2. It is intended to:</p> <ul> <li>be more flexible for organizations (that is, owners and developers of websites, apps, tools, etc.)</li> <li>encourage more accessible user experiences</li> </ul> <p>We are reworking the conformance model based on feedback and we encourage additional feedback as we iterate.</p> <h2 id="development">Development</h2> <h3 id="timeline">Timeline</h3> <p><img src="/WAI/content-images/wcag/calandara.svg" alt="" style="float: right; margin-left: 2rem; width: 20%; max-width: 111px" /></p> <p>The First Public Working Draft of WCAG 3.0 was published on 21 January 2021. The July 2023 draft has many changes that resulted from public feedback. We plan to publish updated drafts every 3-6 months.</p> <p><strong>WCAG 3 is not expected to be a completed W3C standard for a few more years.</strong></p> <p>The Working Group will focus on creating an initial set of guidelines and outcomes. Then will focus on refining the structure and conformance model. They will provide updated drafts for review throughout this process. Once the conformance approach is more stable, the Group will focus on refining the accessibility requirements (guidelines, outcomes, assertions, and support material). We will then provide material to help those wanting to transition to WCAG 3; for example, mapping between WCAG 2 and 3 requirements.</p> <p>WCAG 3 will not supersede WCAG 2, and WCAG 2 will not be deprecated, for at least several years after WCAG 3 is finalized.</p> <p>We will update this section with more specific timeline information as it is available.</p> <h3 id="wcag-3-name-formerly-silver-project">WCAG 3 Name (formerly “Silver” project)</h3> <p>The name of WCAG 3 is different from WCAG 2:</p> <ul> <li>WCAG <strong>3</strong> is W3C Accessibility Guidelines</li> <li>WCAG <strong>2</strong> is Web Content Accessibility Guidelines</li> </ul> <p>“W3C Accessibility Guidelines (WCAG) 3.0” was chosen:</p> <ul> <li>because of wide-spread familiarity with the “WCAG” acronym</li> <li>to encompass the broader scope beyond “content”</li> </ul> <h3 id="who-develops-wcag-3">Who Develops WCAG 3</h3> <p>The WCAG technical documents are developed by the Accessibility Guidelines Working Group (<a href="https://www.w3.org/WAI/GL/">AG WG</a>) (previously under the Silver Task Force) with the Silver Community Group. These Groups are part of the World Wide Web Consortium (<a href="https://www.w3.org">W3C</a>) Web Accessibility Initiative (<a href="https://www.w3.org/WAI/">WAI</a>). You can learn about the development process from <a href="/WAI/standards-guidelines/w3c-process/">How WAI Develops Accessibility Standards through the W3C Process: Milestones and Opportunities to Contribute</a>.</p> <p>We welcome your comments on WCAG 3 Working Drafts. The best way to provide feedback is by opening new <a href="https://github.com/w3c/wcag3/issues">GitHub issues</a>. Alternatively, e-mail public-agwg-comments@w3.org</p> <p>Opportunities for contributing more directly to WCAG and other WAI work are introduced in <a href="/WAI/about/participating/">Participating in WAI</a>.</p> <aside class="box box-icon box-space-above" id="helpimprove" aria-label="feedback"><header class="box-h box-h-icon box-h-space-above box-h-icon"> <svg focusable="false" aria-hidden="true" class="icon-comments "><use xlink:href="/WAI/assets/images/icons.svg#icon-comments"></use></svg> <h2> Help improve this page </h2></header><div class="box-i"><p>Please share your ideas, suggestions, or comments via e-mail to the publicly-archived list <a href="mailto:wai@w3.org?body=%5Binclude%20a%20relevant%20email%20Subject%5D%0A%0A%5Bput%20comment%20here...%5D%0A%0AI%20give%20permission%20to%20share%20this%20to%20a%20publicly-archived%20e-mail%20list.">wai@w3.org</a> or via GitHub.</p> <div class="button-group"> <a href="mailto:wai@w3.org?body=%5Binclude%20a%20relevant%20email%20Subject%5D%0A%0A%5Bput%20comment%20here...%5D%0A%0AI%20give%20permission%20to%20share%20this%20to%20a%20publicly-archived%20e-mail%20list." class="button"><span>E-mail</span></a><a href=" https://github.com/w3c/wai-website/edit/main/pages/standards-guidelines/wcag/wcag3-intro.md " class="button"><span>Fork & Edit on GitHub</span></a><a href="https://github.com/w3c/wai-website/issues/new?template=content-issue.yml&wai-resource-id=wai-wcag-intro&wai-url=https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/" class="button"><span>New GitHub Issue</span></a></div></div></aside> <a class="button button-backtotop" href="#top"><span><svg focusable="false" aria-hidden="true" class="icon-arrow-up "><use xlink:href="/WAI/assets/images/icons.svg#icon-arrow-up"></use></svg> Back to Top</span></a> </main> </div> <footer id="wai-site-footer" class="page-footer default-grid" aria-label="Page"> <div class="inner"><p><strong>Updated:</strong> 16 May 2024.</p><p><strong>Editor:</strong> <a href="https://www.w3.org/People/Shawn/">Shawn Lawton Henry</a>. Contributors: Rachael Bradley Montgomery, Jeanne Spellman, Kevin White.</p> <p>Developed with input from the Education and Outreach Working Group (<a href="https://www.w3.org/WAI/about/groups/eowg/">EOWG</a>), Accessibility Guidelines Working Group (<a href="https://www.w3.org/WAI/about/groups/agwg/">AG WG</a>), Silver Task Force, and Silver Community Group.</p> </div> </footer> <footer class="site-footer grid-4q" aria-label="Site"> <div class="q1-start q3-end about"> <div> <p><a class="largelink" href="https://www.w3.org/WAI/" lang="en" dir="auto" translate="no">W3C Web Accessibility Initiative (WAI)</a></p> <p>Strategies, standards, and supporting resources to make the Web accessible to people with disabilities.</p> </div> <div class="social" lang="en" dir="auto" translate="no"> <ul> <li><a href="https://w3c.social/@wai"><svg focusable="false" aria-hidden="true" class="icon-mastodon "><use xlink:href="/WAI/assets/images/icons.svg#icon-mastodon"></use></svg> Mastodon</a></li> <li><a href="https://www.linkedin.com/company/w3c-wai/"><svg focusable="false" aria-hidden="true" class="icon-linkedin "><use xlink:href="/WAI/assets/images/icons.svg#icon-linkedin"></use></svg> LinkedIn</a></li> <li><a href="https://www.w3.org/WAI/feed.xml"><svg focusable="false" aria-hidden="true" class="icon-rss "><use xlink:href="/WAI/assets/images/icons.svg#icon-rss"></use></svg> Feed</a></li> <li><a href="https://www.youtube.com/channel/UCU6ljj3m1fglIPjSjs2DpRA/playlists/"><svg focusable="false" aria-hidden="true" class="icon-youtube "><use xlink:href="/WAI/assets/images/icons.svg#icon-youtube"></use></svg> YouTube</a></li> <li><a href="https://www.w3.org/WAI/news/subscribe/" class="button">Get News in Email</a></li> </ul> </div> <div lang="en" dir="auto" translate="no"> <p>Copyright © 2024 World Wide Web Consortium (<a href="https://www.w3.org/">W3C</a><sup>®</sup>). See <a href="/WAI/about/using-wai-material/">Permission to Use WAI Material</a>.</p> </div> </div> <div lang="en" dir="auto" translate="no" class="q4-start q4-end"> <ul style="margin-bottom:0"> <li><a href="/WAI/about/contacting/">Contact WAI</a></li> <li><a href="/WAI/sitemap/">Site Map</a></li> <li><a href="/WAI/news/">News</a></li> <li><a href="/WAI/sitemap/#archive">Archive</a></li> <li><a href="/WAI/about/accessibility-statement/">Accessibility Statement</a></li> <li><a href="/WAI/translations/"> Translations</a></li> <li><a href="/WAI/roles/">Resources for Roles</a></li> </ul> </div> </footer> <script src="/WAI/assets/scripts/details4everybody.js?1732321439590790613"></script>  <script src="/WAI/assets/scripts/svg4everybody.js?1732321439590790613"></script> <script> svg4everybody(); </script><script> var translationStrings = {}; </script> </body> </html>