CINXE.COM

<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="utf-8"/> <title>Accessible Rich Internet Applications Working Group 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="#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">Accessible Rich Internet Applications Working Group Charter</h1> <p>The <strong>mission</strong> of the <a href="https://www.w3.org/WAI/ARIA/">Accessible Rich Internet Applications Working Group</a> is to enhance the accessibility of web content through the development of supplemental attributes, including roles, states, and other properties, that can be applied to native host language elements and exposed via platform accessibility APIs.</p> <div class="noprint"> <p class="join"><a href="https://www.w3.org/groups/wg/aria/join">Join the Accessible Rich Internet Applications Working Group.</a></p> </div> <table class="summary-table" id="details"> <tr id="Duration"> <th> Start date </th> <td>9 February 2022</td> </tr> <tr id="CharterEnd"> <th> End date </th> <td>31 December 2024</td> </tr> <tr> <th>Charter extension</th> <td>See <a href="#history">Change History</a>. </td> </tr> <tr> <th> Chairs </th> <td>James Nurthen (Adobe), Valerie Young (Igalia)</td> </tr> <tr> <th> Team Contacts </th> <td> <a href="mailto:cooper@w3.org">Michael Cooper</a> (0.30 <abbr title="Full-Time Equivalent">FTE</abbr> Primary <abbr title="Team Contact">TC</abbr>), <a href="mailto:ran@w3.org">Ruoxi Ran</a> (0.1 <abbr title="Full-Time Equivalent">FTE</abbr>, Publication support, ARIA integration)</td> </tr> <tr> <th> Meeting Schedule </th> <td> <strong>Teleconferences:</strong> The Working Group and its Task Forces generally each hold weekly teleconferences, but this may vary over time according to agenda and preferences.<br /> <strong>Face-to-face:</strong> The Working Group generally meets 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 2 per year. </td> </tr> </table> <section id="scope" class="scope"> <h2>Scope</h2> <ul> <li>Continue development of existing ARIA specifications to address needs reported by authors of accessible content and to achieve parity with native host languages (markup languages such as HTML or SVG that can use ARIA attributes to provide additional accessibility information), creating new ARIA specifications where necessary;</li> <li>For each ARIA specification developed by this Working Group, create a corresponding Accessibility API Mappings specification defining the correct exposure for each platform;</li> <li>For all attributes defined by this Working Group, document best practices for authors;</li> <li>Collaborate with other groups to create mapping specifications for native host language semantics, generally but not always to be published by the ARIA WG;</li> <li>Work with developers of testing tools that can be used to verify accessibility implementations by examining the mappings exposed via platform accessibility APIs;</li> <li>Collaborate with other groups involved in defining ARIA techniques and implementing ARIA support.</li> </ul> <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> <li>Technologies for which corresponding Accessibility API Mappings do not need to be defined.</li> </ul> </section> </section> <section id="deliverables"> <h2> Deliverables </h2> <p>In order to maximize the likelihood of achieving the success criteria described below, the ARIA Working Group will follow a <a href="https://www.w3.org/WAI/ARIA/workflow">work flow</a> designed to see each feature from its <a href="https://www.w3.org/WAI/ARIA/roadmap">road map</a> through to completion, with ARIA feature development, platform accessibility API mapping, implementation, <a href="https://github.com/w3c/testing-how-to/#test-as-you-commit-pointer-event-whatwg-webperf">testing</a>, and authoring guidance taking place at the same time.</p> <p>More detailed milestones and updated publication schedules are available on the <a href="https://www.w3.org/WAI/ARIA/project">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. For deliverables marked as “living standard”, the Working Group intends to publish the latest state of their work as Candidate Recommendation (with Snapshots). The Working Group will publish Recommendations approximately every two years for specifications that define technology features. The Working Group will not publish Recommendation versions of Accessibility API Mappings because they define mappings to accessibility APIs, which may be updated independent of the ARIA technology.</p> <section id="normative"> <h3> Normative Specifications </h3> <p> The Working Group will deliver the following W3C normative specifications: </p> <dl> <dt class="spec" id="7556"><a href="https://www.w3.org/TR/html-aam-1.0/">HTML Accessibility API Mappings</a> (living standard) </dt> <dd>Latest publication: <a href="https://www.w3.org/TR/2020/WD-html-aam-1.0-20200817/">17-Aug-2020</a><br />Exclusion Draft: <a href="https://www.w3.org/TR/2015/WD-html-aam-1.0-20150407/">https://www.w3.org/TR/2015/WD-html-aam-1.0-20150407/</a><br /> associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2015Apr/0000.html"> Call for Exclusion</a> on 09-Apr-2015 ended on 06-Sep-2015 <br />Produced under Working Group Charter: </dd> <dt class="spec" id="8499"><a href="https://www.w3.org/TR/dpub-aria-1.1/">Digital Publishing WAI-ARIA Module 1.1</a></dt> <dd> Latest publication: <a href="https://www.w3.org/TR/2021/WD-dpub-aria-1.1-20210826/">2021-08-26</a><br /> Exclusion Draft: <a href="https://www.w3.org/TR/2021/WD-dpub-aria-1.1-20210826/">https://www.w3.org/TR/2021/WD-dpub-aria-1.1-20210826/</a><br /> associated <a href="https://www.w3.org/mid/cfe-8499-d1d8a827c081051ecdad6330af49a057da4989ac@w3.org"> Call for Exclusion</a> on 2021-08-26 <br /> <i>Exclusion opportunity will end on 2022-01-23</i><br /> Produced under Working Group Charter: <a href="https://www.w3.org/2018/11/aria-charter.html">https://www.w3.org/2018/11/aria-charter.html</a> </dd> <dt><a href="https://www.w3.org/TR/svg-aam-1.0/">SVG Accessibility API Mappings 1.0</a></dt> <dd> Latest publication: <a href="https://www.w3.org/TR/2018/WD-svg-aam-1.0-20180510/">2018-05-10</a><br /> Exclusion Draft: <a href="https://www.w3.org/TR/2015/WD-svg-aam-1.0-20150226/">https://www.w3.org/TR/2015/WD-svg-aam-1.0-20150226/</a><br /> associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2015Feb/0011.html"> Call for Exclusion</a> on 2015-02-26 ended on 2015-07-26<br /> Produced under Working Group Charter: <a href="https://www.w3.org/WAI/PF/charter201006">http://www.w3.org/WAI/PF/charter201006</a> </dd> <dt class="spec"><a href="https://www.w3.org/TR/dpub-aam-1.1/">Digital Publishing Accessibility API Mappings 1.1</a> (living standard)</dt> <dd> Latest publication: <a href="https://www.w3.org/TR/2021/WD-dpub-aria-1.1-20210826/">2021-08-26</a><br /> Exclusion Draft: <a href="https://www.w3.org/TR/2021/WD-dpub-aria-1.1-20210826/">https://www.w3.org/TR/2021/WD-dpub-aria-1.1-20210826/</a><br /> associated <a href="https://www.w3.org/mid/cfe-8499-d1d8a827c081051ecdad6330af49a057da4989ac@w3.org"> Call for Exclusion</a> on 2021-08-26 <br /> <i>Exclusion opportunity will end on 2022-01-23</i> Produced under Working Group Charter: <a href="https://www.w3.org/2018/11/aria-charter.html">https://www.w3.org/2018/11/aria-charter.html</a> </dd> <dt class="spec" id="7887"><a href="https://www.w3.org/TR/wai-aria-1.2/">Accessible Rich Internet Applications (WAI-ARIA) 1.2</a></dt> <dd>Latest publication: <a href="https://www.w3.org/TR/2021/CR-wai-aria-1.2-20210302/">02-Mar-2021</a><br />Exclusion Draft: <a href="https://www.w3.org/TR/2021/CR-wai-aria-1.2-20210302/">https://www.w3.org/TR/2021/CR-wai-aria-1.2-20210302/</a><br /> associated <a href="https://www.w3.org/mid/cfe-7887-475965d0b8ef1edf941c209104ccf1395cb08bc0@w3.org"> Call for Exclusion</a> on 02-Mar-2021 <i>Exclusion opportunity will end on 01-May-2021</i><br />Produced under Working Group Charter: <a href="https://www.w3.org/2018/11/aria-charter.html">https://www.w3.org/2018/11/aria-charter.html</a></dd> <dt class="spec" id="7298"><a href="https://www.w3.org/TR/core-aam-1.2/">Core Accessibility API Mappings</a> (living standard)</dt> <dd>Latest publication: <a href="https://www.w3.org/TR/2019/WD-core-aam-1.2-20191218/">18-Dec-2019</a><br />Exclusion Draft: <a href="https://www.w3.org/TR/2018/WD-core-aam-1.2-20180719/">https://www.w3.org/TR/2018/WD-core-aam-1.2-20180719/</a><br /> associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2018Jul/0006.html"> Call for Exclusion</a> on 19-Jul-2018 ended on 16-Dec-2018 <br />Produced under Working Group Charter: <a href="https://www.w3.org/2015/10/aria-charter">http://www.w3.org/2015/10/aria-charter</a></dd> <dt class="spec" id="7075"><a href="https://www.w3.org/TR/accname-1.2/">Accessible Name and Description Computation 1.2</a> (living standard)</dt> <dd>Latest publication: <a href="https://www.w3.org/TR/2019/WD-accname-1.2-20190711/">11-Jul-2019</a><br />Exclusion Draft: <a href="https://www.w3.org/TR/2019/WD-accname-1.2-20190711/">https://www.w3.org/TR/2019/WD-accname-1.2-20190711/</a><br /> associated <a href="https://www.w3.org/mid/cfe-7075-953b9ac673e809ed18f1ea48f73864f8dcf276d4@w3.org"> Call for Exclusion</a> on 11-Jul-2019 ended on 08-Dec-2019 <br />Produced under Working Group Charter: <a href="https://www.w3.org/2018/11/aria-charter.html">https://www.w3.org/2018/11/aria-charter.html</a></dd> </dl> </section> <section id="ig-other-deliverables"> <h3> Other Deliverables </h3> <p>As described above and in the <a href="https://www.w3.org/WAI/ARIA/workflow">work flow</a>, the Working Group will create a test suite and implementation report for the specification. In addition, other non-normative documents may be created such as use case and requirement documents.</p> <p>The Working Group also expects to collaborate with other groups which produce ARIA and/or Accessibility API Mappings specifications to ensure that all ARIA modules and Accessibility API Mappings specifications are consistent with one another regardless of the producer.</p> <p> The Working Group will also produce WAI-ARIA Authoring Practices, a comprehensive support resource for the WAI-ARIA suite but not published as a Technical Report itself. In further support of that guidance, the Working Group will work with developers of the <a href="https://aria-at.w3.org/">ARIA-AT application</a> to help achieve consistent implementation of the guidance across tools.</p> <p>Other non-normative documents may be created such as: </p> <ul> <li>Use case and requirement documents;</li> <li>Test suite and implementation report for the specification;</li> <li>Primer or Best Practice documents to support web developers when designing applications.</li> </ul> </section> <section id="timeline"> <h3>Timeline</h3> <p>The Working Group maintains a <a href="https://www.w3.org/WAI/ARIA/project">detailed project plan</a> that provides target dates, updated as needed.</p> </section> </section> <section id="success-criteria"> <h2>Success Criteria</h2> <p>The normative documents produced by this Working Group fall into two categories: ARIA specifications and Accessibility API Mapping specifications.</p> <ul> <li>For the ARIA specifications, implementability and interoperability of every feature will be demonstrated by having at least two independent browser implementations of that feature. In addition, for the Accessibility API Mapping specification(s), each ARIA feature will be shown to have at least one implementation in each of: ATK/AT-SPI2, MSAA+IAccessible2, AXAPI, and UIAutomation.</li> <li>Every effort will be made to take member organizations' schedules into account and to ensure all platforms are included. If needed, an Accessibility API Mapping specification will be split into platform-specific specifications, e.g. one for ATK/AT-SPI2, one for MSAA+IAccessible2, one for AXAPI, and one for UIAutomation. This will allow each platform's specification to progress along the Rec track at the timeline that best suits them. For specifications which are not split apart in this fashion, no platform will be dropped out of the specification without prior consultation with that platform's owners.</li> </ul> <p> Modules that reach <a href="https://www.w3.org/2020/Process-20200915/#rec-publication">W3C Recommendation</a> are considered successful when all of the following are present:</p> <ul> <li>Production of stable documents addressing the work items listed in the Deliverables section.</li> <li>Test suites for each module with conformance criteria.</li> <li>Availability of multiple, independent, interoperable implementations of each feature with conformance criteria in each deliverable; as demonstrated by an implementation report (summarizing implementation status against the relevant test suite) for each testable class of product, including user agents.</li> <li>Deployment on multiple platforms.</li> <li>User community and industry adoption of the group deliverables.</li> </ul> <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 separate 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> 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> <h3 id="w3c-coordination">W3C Groups</h3> <dl> <dt><a href="https://www.w3.org/WAI/GL/">Accessibility Guidelines (WCAG) Working Group</a></dt> <dd>Work on HTML 5 and ARIA <a href="https://www.w3.org/WAI/WCAG22/Techniques/">Techniques for WCAG 2.2</a>.</dd> <dt><a href="https://www.w3.org/WAI/APA/">Accessible Platform Architectures Working Group</a></dt> <dd>Collaborate on joint deliverables.</dd> <dt><a href="https://www.w3.org/Style/CSS">CSS Working Group</a></dt> <dd>Coordinate media queries support for context awareness. Provide requirements for future WAI-ARIA support. Coordinate on general CSS accessibility topics.</dd> <dt><a href="https://www.w3.org/publishing/groups/epub-wg/">EPUB 3 Working Group</a></dt> <dd>Coordinate development of digital publishing roles and EPUB Accessibility 1.1.</dd> <dt><a href="https://www.w3.org/International/">Internationalization Working Group</a></dt> <dd>Coordinate how to address accessibility and internationalization in W3C specs.</dd> <dt><a href="https://tag.w3.org/">Technical Architecture Group</a></dt> <dd>Confirm the ARIA relationship to various host languages is interoperable and forwards-compatible.</dd> <dt><a href="https://www.w3.org/Privacy/">Privacy Interest Group</a></dt> <dd>Identify and resolve privacy implications of features of the technology that capture user environment information, particularly specific assistive technology being used, in order to customize the user experience.</dd> <dt><a href="https://www.w3.org/Graphics/SVG/">SVG Working Group</a></dt> <dd>Coordinate on graphics role module and SVG Accessibility API Mappings.</dd> <dt><a href="https://www.w3.org/WebPlatform/WG/">Web Platform Working Group</a></dt> <dd>Implementation of ARIA and HTML Accessibility API Mappings, coordinate development of APIs that address accessibility use cases, and work on other joint deliverables including <a href="https://www.w3.org/TR/2dcontext2/">Canvas 2D Context</a>.</dd> </dl> </section> <section> <h3 id="external-coordination">External Organizations</h3> <dl> <dt><a href="http://www.daisy.org/">DAISY Consortium</a></dt> <dd>Coordinate on publishing and math accessibility API mappings.</dd> <dt><a href="http://www.imsglobal.org/">IMS Global Learning Consortium</a></dt> <dd>Coordinate on features that impact e-learning and testing.</dd> <dt><a href="https://whatwg.org/">WHATWG</a></dt> <dd>Coordination on integration of ARIA in HTML and Web Components.</dd> </dl> </section> </section> <section class="participation"> <h2 id="participation"> Participation </h2> <p> To be successful, this Working Group is expected to have 6 or more active participants for its duration, including representatives from the key implementers 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|Interest) Group. There is no minimum requirement for other Participants. </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, except by explicit one-time invitation from the chair(s). </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/ARIA/">Accessible Rich Internet Applications Working Group</a> </p> <p>This group uses the public mailing list <a href="mailto:public-aria@w3.org" id="public-name">public-aria@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-aria/">archive</a>) and <a href="https://www.w3.org/WAI/ARIA/contribute#github" id="public-github">several GitHub repositories</a>. <a href="https://www.w3.org/WAI/ARIA/communication">Additional communication channels</a> are also used. 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</a>). The Working Group maintains specific procedures to establish and measure consensus and address objections in the <a href="https://www.w3.org/WAI/ARIA/decision-policy">Accessible Rich Internet Applications Working Group Decision Policy</a>. All decisions made by the group should be considered resolved unless and until new information becomes available, or unless reopened at the discretion of the Chairs or the Director. </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, Votes)</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/aria/ipr">W3C Patent Policy Implementation</a>. </p> </section> <section id="licensing"> <h2>Licensing</h2> <p>This Working Group will use the <a href="https://www.w3.org/Consortium/Legal/copyright-software">W3C Software and 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/#WG-and-IG">section 5.2</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 5.2.3)</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/2015/10/aria-charter">Initial Charter</a></th> <td> 22 October 2015 </td> <td> 31 July 2018 </td> <td> none </td> </tr> <tr> <th><a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2018JulSep/0038.html">Charter Extension</a></th> <td>6 September 2018</td> <td>31 October 2018</td> <td>none</td> </tr> <tr> <th><a href="https://www.w3.org/2018/11/aria-charter">Rechartered</a></th> <td> 8 November 2018 </td> <td>31 October 2021</td> <td> <ul> <li>Clarified mission to focus exclusively on WAI-ARIA and Accessibility API Mappings (AAMs);</li> <li>Clarified dependency on other groups for several ARIA modules;</li> <li>Updated Success Criteria to describe successful testing procedure for ARIA and AAMs;</li> <li>Removed User Context as a deliverable; the evolution of it, Pesonalization Semantics; is being transferred to the <a href="https://www.w3.org/WAI/APA/">APA Working Group</a>;</li> <li>Produced annual dot-release publications of ARIA and supporting specifications beginning Q4 2019, with features prioritized according to the <a href="https://www.w3.org/WAI/ARIA/roadmap">roadmap</a>;</li> <li>Adopted a concrete <a href="https://www.w3.org/WAI/ARIA/workflow">workflow</a> for feature acceptance to add predictability to timelines;</li> <li>Clarified participation and communication procedures;</li> <li>Added licensing section to specify the W3C Document license for Recommendation-track deliverables and the W3C Software and Document license for others; </li> <li>Staff effort increased from .25 FTE to .4 FTE to provide additional support for project management, inter-group coordination on related ARIA specifications, and publication.</li> </ul> </td> </tr> <tr> <th><a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2021OctDec/0034.html">Charter Extension</a></th> <td>19 November 2021</td> <td>31 January 2022</td> <td>none</td> </tr> <tr> <th><a href="https://www.w3.org/2022/02/aria-charter">Rechartered</a></th> <td>7 February 2022</td> <td>31 January 2024</td> <td>Changes from the <a href="https://www.w3.org/2018/08/apa-charter">previous charter</a> (<a href="https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2F2018%2F11%2Faria-charter.html&doc2=https%3A%2F%2Fwww.w3.org%2F2022%2F02%2Faria-charter.html">diff from previous charter</a>):<ul> <li>Switch to Evergreen for certain specs.</li> </ul></td> </tr> <tr> <th>New co-chair</th> <td>13 April 2022</td> <td></td> <td><a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2022AprJun/0008.html">Valerie Young appointed as co-chair</a>, replacing <a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2021JulSep/0045.html">Joanmarie Diggs who stepped down</a> in September 2021.</td> </tr> <tr> <th><a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2023OctDec/0060.html">Charter Extension</a></th> <td>18 December 2023</td> <td>31 July 2024</td> <td>none</td> </tr> <tr> <th><a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2024AprJun/0049.html">Charter Extension</a></th> <td>25 June 2024</td> <td>31 December 2024</td> <td>The group is developing a new charter (see <a href="https://w3c.github.io/charter-drafts/2024/aria-charter.html">draft charter</a>) and comments can be raised on <a href="https://github.com/w3c/charter-drafts/issues">GitHub</a>.</td> </tr> </tbody> </table> </section> </section> </main> <hr /> <footer> <address> <a href="mailto:cooper@w3.org">Michael Cooper</a></address> <p class="copyright"> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2021 <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> <hr /> </footer> </body> </html>