Accessibility Guidelines Working Group (AG WG) Charter

<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="utf-8" /> <title>Accessibility Guidelines Working Group (AG WG) Charter</title> <link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen" /> <link rel="stylesheet" type="text/css" href="https://www.w3.org/OldGuide/pubrules-style.css" /> <link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css" /> <style> main { max-width: 60em; margin: 0 auto; } ul#navbar { font-size: small; } dt.spec { font-weight: bold; } dt.spec new { background: yellow; } ul.out-of-scope > li { font-weight: bold; } ul.out-of-scope > li > ul > li { font-weight: normal; } .issue { background: cornsilk; font-style: italic; } .todo { color: #900; } footer { font-size: small; }</style> </head> <body> <header id="header"> <aside> <ul id="navbar"> <li> <a href="#background">Background</a> </li> <li> <a href="#scope">Scope</a> </li> <li> <a href="#deliverables">Deliverables</a> </li> <li> <a href="#success-criteria">Success Criteria</a> </li> <li> <a href="#coordination">Coordination</a> </li> <li> <a href="#participation">Participation</a> </li> <li> <a href="#communication">Communication</a> </li> <li> <a href="#decisions">Decision Policy</a> </li> <li> <a href="#patentpolicy">Patent Policy</a> </li> <li> <a href="#licensing">Licensing</a> </li> <li> <a href="#about">About this Charter</a> </li> </ul> </aside> <p> <a href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72" /> </a> </p> </header> <main> <h1 id="title">Accessibility Guidelines Working Group Charter</h1> <p class="mission">The <strong>mission</strong> of the <a href="https://www.w3.org/groups/wg/ag/">Accessibility Guidelines Working Group</a> is to develop specifications to support making implementations of web technologies accessible for people with disabilities, and to develop and maintain implementation support materials.</p> <div class="noprint"> <p class="join"> <a href="https://www.w3.org/groups/wg/ag/join">Join the Accessibility Guidelines Working Group.</a> </p> </div> <p> This charter is available on <a href="https://github.com/w3c/wcag/blob/charter-2022/charter.html">GitHub</a>. Feel free to raise <a href="https://github.com/w3c/wcag/issues">issues</a>. </p> <section id="details"> <table class="summary-table"> <tr id="Status"> <th> Charter Status </th> <td>In <a href="https://www.w3.org/groups/wg/ag/charters">group status page</a> and <a href="https://www.w3.org/2023/11/ag-charter#history">detailed change history</a>.</td> </tr> <tr id="Duration"> <th> Start date </th> <td>3 November 2023</td> </tr> <tr id="CharterEnd"> <th> End date </th> <td> 31st October 2025 </td> </tr> <tr> <th> Chairs </th> <td> <ul> <li>Chuck Adams (Oracle)</li> <li>Alastair Campbell (Nomensa)</li> <li>Rachael Montgomery (Library of Congress)</li> </ul> </td> </tr> <tr> <th> Team Contacts </th> <td> <ul> <li>Kevin White (0.5 FTE <b>primary AG WG team contact</b> [Member funds])</li> <li>Shawn Lawton Henry (0.05 FTE for <a href="https://www.w3.org/WAI/GL/low-vision-a11y-tf/">Low Vision TF</a> [external funds])</li> <li>Roy Ran (0.05 FTE for <a href="https://www.w3.org/WAI/GL/task-forces/coga/">COGA TF</a> and 0.05 FTE for <a href="https://www.w3.org/WAI/GL/mobile-a11y-tf/">Mobile TF</a> [<b>Member funds</b>])</li> </ul> </td> </tr> <tr> <th>Additional Team Support</th> <td> <ul> <li>Roy Ran (0.05 FTE for standards harmonization [<b>Member funds</b>])</li> <li>Daniel Montalvo (0.2 FTE for <a href="https://www.w3.org/WAI/GL/task-forces/conformance-testing/">ACT TF</a> resource development [external funds])</li> </ul> </td> </tr> <tr> <th> Meeting Schedule </th> <td> <strong>Teleconferences:</strong> weekly<br /> <strong>Face-to-face:</strong> we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year. </td> </tr> </table> </section> <section id="background" class="background"> <h2>Background</h2> <section id="background-ag"> <h3>Motivation for Accessibility Guidelines Working Group (AG WG)</h3> <p>Web accessibility means that websites, tools, and technologies are designed and developed so that people with disabilities can use them. Web accessibility encompasses all disabilities that affect access to the Web, and also benefits older users and people without disabilities. Accessible design improves overall user experience and satisfaction, especially in a variety of situations, and across different devices. It is essential that several different components of web development and interaction work together in order for the web to be accessible to people with disabilities. These components include content technologies, web content, web browsers and media players, assistive technology, users, developers, authoring tools, and evaluation tools. Groups in the Web Accessibility Initiative work together to address accessibility for all the components.</p> <p>The Accessibility Guidelines Working Group describes the characteristics of accessible web content, in the form of guidance to content developers. It also describes support from other components needed for its advice to work, such as technologies, user agents, and authoring tools. Guidelines from this Working Group are widely used by developers and implementers, referenced in industry policy, and benefit all web users.</p> </section> <section id="background-focus"> <h3>Focus for the 2023 - 2025 Charter</h3> <p>The goal of this 2023 - 2025 AG WG charter will be to put into wide (public) review one or more draft documents that demonstrate all major components of <a href="https://www.w3.org/TR/wcag-3.0/">W3C Accessibility Guidelines (WCAG) 3</a> and how they fit together. During this charter period, the WG will propose an approach for public review that addresses each of the <a href="https://www.w3.org/TR/wcag-3.0-requirements/#requirements">WCAG 3 requirements</a> and known challenges. Examples of known challenges include:</p> <ul> <li>Rewriting existing guidelines,</li> <li>Adding guidance to address known gaps in WCAG 2,</li> <li>Creating new guidelines for emerging technologies, and</li> <li>Complex conformance questions, such as third-party content, scoring, accessibility statements, etc.</li> </ul> <p>Requirements or challenges will need a demonstrated solution that has AG WG consensus by the end of this charter or will be excluded from WCAG 3. Solutions will not all be complete at the end of this charter period, but they will be sufficiently mature so that reviewers can understand the intended scope of WCAG 3 as a whole, and will have enough depth to understand how conformance evaluations for WCAG 3 will work.</p> <p>By the end of the 2022 - 2024 charter AG WG will: </p><ul> <li>Know what will and will not be part of WCAG 3,</li> <li>have a timeline for delivering WCAG 3, and </li> <li>have decided how WCAG 3 will be delivered (all at once, in phases, or as modules.) </li> </ul> In the case of phases or modules, AG WG will have the scope and requirements of those phases or modules defined for the next charter period. </section> </section> <section id="scope" class="scope"> <h2>Scope</h2> <section id="scope-wcag3"> <h3>WCAG 3 </h3> <p>The primary objective of the AG WG during this charter period is to publish one or more <a href="https://www.w3.org/2021/Process-20211102/#wide-review">wide review draft(s)</a> of WCAG 3. The goal is to get broad support for the scope and direction of WCAG 3 and work out how the <a href="https://www.w3.org/TR/wcag-3.0-requirements/">requirements for WCAG 3</a> can be met, including better coverage across disabilities, and be easier to maintain, so that the new framework will be more durable as technologies evolve. These wide review(s) of WCAG 3 will include the following:</p> <ul> <li>A preliminary set of guidelines (not including outcomes or methods),</li> <li>A representative set of outcomes worked out in detail, along with all methods and documentation necessary to understand and test those outcomes,</li> <li>At least one example of each type/category of testing or evaluation approach, </li> <li>A candidate conformance model, and</li> <li>An approach on testing emerging technologies (if included).</li> </ul> <p>WCAG 3 will not be brought to Recommendation during this charter period. Results of the wide review(s) will determine scope and timeline for further work in the following charter period. Deliverables and timelines for WCAG 3 are further described in the <a href="https://github.com/w3c/wcag3/wiki#WCAG3_Project_Plan">WCAG 3 project plan</a>.</p> <section id="scope-wcag3-additional"> <h4>Additional WCAG 3 Publications</h4> <p>AG WG will explore options for publishing WCAG 3 in stages or as modules. If any part of the initial WCAG 3 will be published as a stand-alone resource, a draft will be made available within this charter period. If a transitional document between WCAG 2.2 and WCAG 3 is to be created (such as a WCAG 2.3 or WCAG 2.9), a first draft of it will be published by the end of the charter.</p> </section> </section> <section id="scope-wcag3-conformance"> <h4>WCAG 3 Conformance Model</h4> <p>In this charter period, AG WG will define a working conformance model for WCAG 3. If any part of the initial WCAG 3 recommendation will be published as a stand-alone resource, a draft will be made available within this charter period.</p> <p>WCAG 3 will not include normative guidelines for stand-alone user agents or authoring tools. WCAG 3 may, however, include guidance for user agents and authoring tools.</p> </section> <section id="scope-other"> <h3>Non WCAG 3 Scope</h3> <p>In addition to WCAG 3, the group continues existing work and materials support commitments:</p> <ul> <li>updates <a href="https://www.w3.org/TR/wcag2ict/"><u>WCAG2ICT</u></a> with non-normative guidance on applying WCAG 2.1 and WCAG 2.2 to non-web technology,</li> <li>continues addressing <a href="https://github.com/w3c/wcag/issues"><u>open WCAG 2 issues</u></a> and public feedback and maintains interpretive support materials for its normative guidance (<a href="https://www.w3.org/WAI/WCAG22/Understanding/"><u>Understanding WCAG 2</u></a>, <a href="https://www.w3.org/WAI/WCAG22/Techniques/"><u>WCAG 2 Techniques</u></a>),</li> <li>performs secondary research, and engages with primary researchers, to understand better the needs of specific user groups (such as <a href="https://www.w3.org/TR/low-vision-needs/">Accessibility Requirements for People with Low Vision</a>, <a href="https://www.w3.org/TR/coga-user-research/">Cognitive Accessibility User Research</a>),</li> <li>conducts gap analyses against deployed features to identify accessibility guidance needs (such as <a href="https://www.w3.org/TR/coga-gap-analysis/">Cognitive Accessibility Roadmap and Gap Analysis</a>, <a href="https://www.w3.org/TR/mobile-accessibility-mapping/">Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile</a>),</li> <li>develops Accessibility Conformance Testing (ACT) Rules Format 1.1, to keep ACT rules compatible with WCAG 3, and enable writing rules that have proven difficult to write under version 1.0,</li> <li>provides evaluation guidance and test materials to support verification of conformance to normative guidance (such as <a href="https://www.w3.org/TR/act-rules-format-1.0/">Accessibility Conformance Testing (ACT) Rules Format 1.0</a>),</li> <li>develops supplemental guidance, beyond that in the normative guidance, that describes enhanced accessibility for certain scenarios (such as <a href="https://www.w3.org/TR/coga-usable/">Making Content Usable for People with Cognitive and Learning Disabilities</a>), and</li> <li>maintains errata for content developed by predecessor groups (such as <a href="https://www.w3.org/TR/ATAG20/">Authoring Tool Accessibility Guidelines 2.0</a>).</li> </ul> </section> <section id="section-out-of-scope"> <h3 id="out-of-scope">Out of Scope</h3> <p>The following features are out of scope, and will not be addressed by this Working group.</p> <ul class="out-of-scope"> <li>The AG WG is not, and does not aspire to be, the central repository for accessibility support data.</li> <li>The AG WG does not perform conformance evaluations and reviews.</li> <li>The AG WG does not provide normative guidance on non-web technologies; however, informational guidance may include examples outside the scope of the web.</li> <li>The AG WG is not currently working on the <a href="https://www.w3.org/TR/ATAG20/">Authoring Tool Accessibility Guidelines</a> or the <a href="https://www.w3.org/TR/UAAG20/">User Agent Accessibility Guidelines</a> specifications, except to maintain errata, though some content may be relevant to and included in WCAG 3.</li> </ul> <ul class="out-of-scope"> </ul> </section> </section> <section id="deliverables"> <h2> Deliverables </h2> <p>Updated document status is available on the <a href="https://www.w3.org/groups/wg/ag/publications">group publication status page</a>.</p> <p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval. <i>Expected completion</i> indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.</p> <section id="normative"> <h3> Normative Specifications </h3> <p> The Working Group will deliver the following W3C normative specifications: </p> <dl> <dt id="web-foo" class="spec"> <a href="https://www.w3.org/TR/wcag-3.0/">W3C Accessibility Guidelines (WCAG) 3.0</a> </dt> <dd> <p>This specification presents a new model and guidelines to make web content and applications accessible to people with disabilities. It supports a wide set of user needs, uses new approaches to testing, and allow frequent maintenance of guidelines and related content to keep pace with accelerating technology change. WCAG 3.0 supports this evolution by focusing on users’ functional needs. Following these guidelines will make content more accessible to people with a wide range of <a href="https://w3c.github.io/fast/#functional-needs">functional needs</a>.</p> <p class="draft-status"><b>Draft state:</b> Working Draft</p> <p class="milestone"><b>Expected completion:</b> Q2 2026</p> <p> <b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2021/WD-wcag-3.0-20210121/">W3C Accessibility Guidelines (WCAG) 3.0 W3C Working Draft 07 December 2021</a> </p> <p> <b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2021/WD-wcag-3.0-20210121/">W3C Accessibility Guidelines (WCAG) 3.0 W3C First Public Working Draft 21 January 2021 </a> </p> <p> <b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2019/12/ag-charter">https://www.w3.org/2019/12/ag-charter</a> </p> </dd> <dt>ACT Rules Format 1.1</dt> <dd> <p>This specification defines the format, logic, and implementation of accessibility test rules.</p> <p class="draft-status"> <b>Draft state:</b> <a href="https://w3c.github.io/wcag-act/act-rules-format.html">Editor's Draft</a> </p> <p class="milestone"><b>Expected completion:</b> Q3 2024</p> </dd> </dl> </section> </section> <section> <h3>Non-Normative Technical Reports</h3> <p>The Working Group publishes formal non-normative guidance such as:</p> <ul> <li>Updates to <a href="https://www.w3.org/TR/wcag2ict/">Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies</a> (WCAG2ICT).</li> <li>Working Group Notes supporting the <a href="https://www.w3.org/TR/act-rules-format-1.0/">Accessibility Conformance Rules Format 1.0</a>.</li> <li>Working Group Notes to support understanding and interpretation of other deliverables as the need arises.</li> </ul> <section id="ig-other-deliverables"> <h3> Other Deliverables </h3> <p> Other non-normative documents may be created such as: </p> <ul> <li>Ongoing updates of non-normative resources to understand and implement guidance, including the current <a href="https://www.w3.org/WAI/WCAG21/Understanding/">Understanding WCAG 2.x</a> and <a href="https://www.w3.org/WAI/WCAG21/Techniques/">Techniques for WCAG 2.x</a> as well as new resources to support implementation of WCAG 3.</li> <li><a href="https://www.w3.org/TR/wcag-3.0-requirements/">Requirements for WCAG 3.0</a>, noting that it is a living document and this charter defines the scope of the group’s work.</li> <li>Mapping guidance and / or other materials to support transition between WCAG 2.x and WCAG 3.</li> <li>Publications supporting the <a href="https://www.w3.org/TR/act-rules-format-1.0/">Accessibility Conformance Rules Format 1.0</a>, such as instances of ACT Rules.</li> <li>Errata for WCAG 2.0, 2.1, and 2.2.</li> <li>Errata for ATAG 2.0.</li> </ul> </section> <section id="timeline"> <h3>Timeline</h3> <p>The Working Group maintains <a href="https://www.w3.org/WAI/GL/wiki/Timelines">currrent timeline estimates</a> in its wiki.</p> <ul> <li>Q1 2023: FPWD for ACT Rules Format 1.1</li> <li>Q3 2024: Wide review draft of W3C Accessibility Guidelines (WCAG) 3.0.</li> <li>Q3 2024: Recommendation of ACT Rules Format 1.1.</li> </ul> </section> </section> <section id="success-criteria"> <h2>Success Criteria</h2> <p> In order to advance to <a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each normative specification is expected to have <a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent implementations</a> of every feature defined in the specification.</p> <p>Each specification should contain sections detailing all known security and privacy implications for implementers, Web authors, and end users.</p> <p>There should be testing plans for each specification, starting from the earliest drafts.</p> <p>There should be sufficient techniques and tests for each specification, starting from the earliest drafts. To promote interoperability, all changes made to specifications should have <a href="https://www.w3.org/2019/02/testing-policy.html">tests</a>.</p> </section> <section id="coordination"> <h2>Coordination</h2> <p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">horizontal review</a> for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>. Invitation for review must be issued during each major standards-track document transition, including <a href="https://www.w3.org/Consortium/Process/#RecsWD" title="First Public Working Draft">FPWD</a>. The Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of each specification. The Working Group is advised to seek a review at least 3 months before first entering <a href="https://www.w3.org/Consortium/Process/#RecsCR" title="Candidate Recommendation" >CR</a> and is encouraged to proactively notify the horizontal review groups when major changes occur in a specification following a review.</p> <p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/Consortium/Process/#WGCharter">W3C Process Document</a>:</p> <section id="w3c-coordination"> <h3>W3C Groups</h3> <dl> <dt> <a href="https://www.w3.org/WAI/EO/">Accessibility Education and Outreach Working Group</a> </dt> <dd>Coordinate on making WCAG 2.x and WCAG 3.0 usable by a wider audience, on developing or reviewing strategies and materials to increase awareness and to educate Web community about WCAG 2.x and 3.0.</dd> <dt> <a href="https://www.w3.org/WAI/APA/">Accessible Platform Architectures Working Group</a> </dt> <dd>Provide input into other W3C groups on accessibility requirements, and coordinate on development and adoption of functional needs and maturity model.</dd> <dt> <a href="https://www.w3.org/WAI/ARIA/">ARIA Working Group</a> </dt> <dd>Review and help develop WCAG 2.x Techniques for WAI-ARIA.</dd> <dt> <a href="https://www.w3.org/Style/CSS/">Cascading Style Sheets Working Group</a> </dt> <dd>Advise on WCAG conformance interpretations of CSS features.</dd> <dt> <a href="https://www.w3.org/publishing/groups/epub-wg/">EPub 3 Working Group</a> </dt> <dd>Coordinate on accessibility guidelines that impact digital publishing.</dd> <dt> <a href="https://www.w3.org/International/core/Overview">Internationalization Working Group</a> </dt> <dd>Ensure that references to internationalization techniques are correct, and to ensure that language can be translated successfully.</dd> <dt> <a href="https://www.w3.org/WAI/IG/">WAI Interest Group</a> </dt> <dd>Provide input on group deliverables and explore ideas for consideration and further development.</dd> </dl> </section> <section id="external-coordination"> <h3>External Organizations</h3> <p>This section is a non-exclusive list of organizations that may take up WAI guidelines into policies. The Working Group seeks to develop standards that can be incorporated into policies globally and expects to accomplish this through broad review and involvement. AG WG will liaise with these organizations at key stages but recommends direct participation in the Working Group where possible.</p> <dl> <dt> <a href="https://www.access-board.gov">U.S. Access Board</a> </dt> <dd>Review of specification</dd> <dt> <a href="https://www.parl.ca/DocumentViewer/en/42-1/bill/C-81/third-reading">Canadian Accessibility Standards Development Organization which may administer C-81 the Accessible Canada Act</a> </dt> <dd>Review of specification</dd> <dt> <a href="http://www.etsi.org">European Telecommunications Standards Institute (ETSI)</a> </dt> <dd>Establish liaison with the ETSI Human Factors Technical Committee for collaboration and specification review.</dd> <dt> <a href="http://www.cen.eu">European Committee for Standardization (CEN)</a> </dt> <dd>Review of specification</dd> <dt> <a href="http://ec.europa.eu">European Commission</a> </dt> <dd>Review of specification</dd> <dt> <a href="http://eng.nia.or.kr/">National Information Society Agency (NIA)</a> </dt> <dd>Review of specification</dd> <dt> <a href="http://www.ucdenver.edu/academics/colleges/Engineering/research/AssistiveTechnologyPartners/research/RERC/Projects/Pages/Projects.aspx"><abbr title="Rehabilitation Engineering Research Center">RERC</abbr> for the Advancement of Cognitive Technologies</a> </dt> <dd>Review of specification</dd> <dt> <a href="http://trace.umd.edu/itrerc"><abbr title="Rehabilitation Engineering Research Center">RERC</abbr> on Universal Interface and Information Technology Access</a> </dt> <dd>Review of specification</dd> <dt> <a href="http://www.cdpf.org.cn/"> Chinese Disabled People's Federation (CDPF)</a> </dt> <dd>Review of specification</dd> <dt> <a href="https://www.jisc.go.jp/"> Japanese Industry Standards Organization (JIS)</a> </dt> <dd>Review of specification</dd> </dl> </section> </section> <section id="participation" class="participation"> <h2> Participation </h2> <p> To be successful, this Working Group is expected to have 15 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a working day per week towards the Working Group. There is no minimum requirement for other Participants. </p> <p>Key implementers of WCAG (desktop and non-desktop environments) include Web content developers (page authors, site designers, etc.), Web authoring tool developers, Web accessibility evaluation tool developers, user agent tool developers, and people with disabilities.</p> <p> The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href="#communication">Communication</a>. </p> <p> The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a>. </p> <p>Participants in the group are required (by the <a href="https://www.w3.org/Consortium/Process/#ParticipationCriteria">W3C Process</a>) to follow the W3C <a href="https://www.w3.org/Consortium/cepc/">Code of Ethics and Professional Conduct</a>.</p> </section> <section id="communication"> <h2> Communication </h2> <p id="public">Technical discussions for this Working Group are conducted in <a href="https://www.w3.org/Consortium/Process/#confidentiality-levels">public</a>: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests. The meetings themselves are not open to public participation, however. </p> <p>Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="https://www.w3.org/WAI/GL/">Accessibility Guidelines Working Group home page</a>. </p> <p>This group conducts email discussion on the public mailing list <a href="mailto:w3c-wai-gl@w3.org" id="public-name">w3c-wai-gl@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/w3c-wai-gl/">archive</a>). <a href="https://www.w3.org/WAI/GL/task-forces/">Task forces</a> and sub-groups may use additional lists or other communication mechanisms documented on their home pages. Discussion of issues for specific deliverables generally takes place in the GitHub repository identified for the deliverable. The public is invited to review, discuss and contribute to this work. </p> <p>The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion. </p> </section> <section id="decisions"> <h2> Decision Policy </h2> <p>This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/Consortium/Process/#Consensus"> W3C Process Document (Section 5.2.1, Consensus</a>). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.</p> <p>However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections. </p> <p>The Working Group maintains specific procedures to establish and measure consensus and address objections in the <a href="https://www.w3.org/WAI/GL/decision-policy">AG Working Group Decision Policy</a>.</p> <p>Note: The AG WG has maintained a supplemental decision policy to support the review needed for decisions that can impact regulatory content. A recent update preserves this for stable content while reducing procedural requirements for content that is still under development. The scope of this charter combines <em>maintenance of the mature WCAG 2.x</em> with <em>innovation of WCAG 3</em>. Because of this complex scope, the WG chairs view the decision policy changes as essential to WG success. The updated decision policy should be reviewed together with this draft charter.</p> <p>This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/#Votes">W3C Process Document (Section 5.2.3, Deciding by Vote)</a> and includes no voting procedures beyond what the Process Document requires. </p> </section> <section id="patentpolicy"> <h2>Patent Policy</h2> <p>This Working Group operates under the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a> (Version of 15 September 2020). To promote the widest adoption of Web standards, W3C seeks to issue Web specifications that can be implemented, according to this policy, on a Royalty-Free basis. For more information about disclosure obligations for this group, please see the <a href="https://www.w3.org/groups/wg/ag/ipr">licensing information</a>. </p> </section> <section id="licensing"> <h2>Licensing</h2> <p>This Working Group will use the <a href="https://www.w3.org/Consortium/Legal/2015/doc-license">W3C Document license</a> for all its deliverables.</p> </section> <section id="about"> <h2> About this Charter </h2> <p> This charter has been created according to <a href="https://www.w3.org/Consortium/Process/#GAGeneral">section 3.4</a> of the <a href="https://www.w3.org/Consortium/Process/">Process Document</a>. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence. </p> <section id="history"> <h3> Charter History </h3> <p>The following table lists details of all changes from the initial charter, per the <a href="https://www.w3.org/Consortium/Process/#CharterReview">W3C Process Document (Section 4.3, Advisory Committee Review of a Charter)</a>:</p> <table class="history"> <tbody> <tr> <th>Charter Period </th> <th> Start Date </th> <th> End Date </th> <th> Changes </th> </tr> <tr> <th> <a href="https://www.w3.org/WAI/GL/initial-charter">Initial Charter</a> </th> <td>6 October 1997</td> <td><not set></td> <td> Develop Understanding Web Access Issues, later named Web Content Accessibility Guidelines 1.0; document supporting quicklists.</td> </tr> <tr> <th> <a href="https://www.w3.org/WAI/GL/new-charter-2000.html">Rechartered 2001</a> </th> <td>18 June 2001</td> <td>May 2002, extended to June 2004</td> <td>Add WCAG 2.0 and supporting techniques to its deliverables.</td> </tr> <tr> <th> <a href="https://www.w3.org/2004/04/wcag-charter.html">Rechartered 2005</a> </th> <td>1 January 2005</td> <td>31 December 2006; extended to 30 April 2007, 31 December 2007, 30 June 2008, 31 December 2008, 30 June 2009, 9 August 2009</td> <td>Incorporation of Quality Assurance (QA) Framework into its mission; updated descriptions of supporting deliverables for WCAG 2.0, especially including test suites and implementation reports; updated dependency statements; updated language where necessary to align with June 2003 W3C Process Document.</td> </tr> <tr> <th> <a href="https://www.w3.org/WAI/GL/2010/06/charter">Rechartered 2010</a> </th> <td>14 September 2010</td> <td>30 June 2013; extended to 30 September 2013, 18 May 2015, 15 July 2015, and 24 September 2015</td> <td>Transitioned to maintain support resources for WCAG 2.0.</td> </tr> <tr> <th> <a href="https://www.w3.org/2015/09/wcag-charter">Rechartered 2015</a> </th> <td>24 September 2015 </td> <td>31 July 2018</td> <td>Added recommendation-track work in the form of extensions to WCAG 2.0; increased focus on work to address needs related to mobile devices, cognitive impairments and learning disabilities, digital learning materials, and low vision; more work on accessibility support documentation and testing.</td> </tr> <tr> <th> <a href="https://www.w3.org/2017/01/ag-charter">Rechartered 2017</a> </th> <td>27 January 2017</td> <td>31 October 2019, extended to 31 December 2019</td> <td>Changing from publishing normative extensions for multiple topics to a consolidated WCAG 2.1 and adding new publication for Accessibility Conformance Testing Framework 1.0.</td> </tr> <tr> <th> <a href="https://lists.w3.org/Archives/Member/chairs/2018JanMar/0079.html">New Co-Chair</a> </th> <td>27 February 2018</td> <td></td> <td>Alastair Campbell joins Andrew Kirkpatrick as co-chair; Joshue O Connor steps down as co-chair.</td> </tr> <tr> <th> <a href="https://www.w3.org/2019/12/ag-charter">Rechartered 2019</a> </th> <td>19 December 2019</td> <td>31 October 2022</td> <td>Added WCAG 2.2 and moved previously incubated Silver to Recommendation Track.</td> </tr> <tr> <th> <a>New Co-Chairs</a> </th> <td>4 March 2020</td> <td></td> <td>Chuck Adams and Rachael Montgomery join Alastair Campbell as co-chairs; Andrew Kirkpatrick steps down as co-chair.</td> </tr> <tr> <th>Chair Affiliation</th> <td>24 September 2021</td> <td></td> <td>Rachael Montgomery re-appointed as group chair after affiliation changed.</td> </tr> <tr> <th> Charter Extension </th> <td>28 October 2022</td> <td>31 October 2023</td> <td>Charter extended until <a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2022OctDec/0012.html">30 April 2023</a>.<br> Charter extended until <a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2023AprJun/0018.html">31st October 2023</a>.</td> </tr> <tr> <th colspan="1"><a href="https://www.w3.org/2023/11/ag-charter.html">Rechartered 2023</a></th> <td colspan="1">3 November 2023</td> <td colspan="1">31 October 2025</td> <td colspan="1">Shift in focus to WCAG 3 and ongoing updates of non-normative resources for WCAG 2.x</td> </tr> </tbody> </table> </section> <section id="changelog"> <h3>Change log</h3>  <p>Changes to this document are documented in this section.</p>  </section> </section> </main> <hr /> <footer> <p class="copyright"> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2022 <a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> ( <a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="https://www.keio.ac.jp/">Keio</a>, <a href="https://ev.buaa.edu.cn/">Beihang</a> ), All Rights Reserved. <abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply. </p> </footer> </body> </html>

CINXE.COM

Accessibility Guidelines Working Group (AG WG) Charter