-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathag-charter.html
451 lines (406 loc) · 30.7 KB
/
ag-charter.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
<!DOCTYPE html>
<html lang="en-US" xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta charset="utf-8" />
<title>Accessibility Guidelines 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/Guide/pubrules-style.css" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css" />
<style type="text/css">
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;
}
.delete
{
text-decoration:line-through;
}
.delete:before
{
content:"[del]";
}
.delete:after
{
content:"[/del]";
}
.change
{
background-color: orange;
}
.change:before
{
content:"[add]";
}
.change:after
{
content:"[/add]";
}
.todo
{
color:red;
}
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="#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="http://www.w3.org/Icons/w3c_home" width="72" />
</a>
<a class="domainlogo" title="domain:wai" href="http://w3.org/WAI/">
<img src="http://www.w3.org/Icons/wai" alt="WAI Domain" />
</a>
</p>
</header>
<main>
<h1 id="title">[DRAFT] Accessibility Guidelines Working Group Charter</h1>
<p class="todo">This is a draft charter for the Accessibility Guidelines Working Group. It incorporates changes made in response to the <a href="https://www.w3.org/2002/09/wbs/33280/accessibility-guidelines-2016/">Advisory Committee review</a>, but has not yet been approved. A draft <a href="AG_DOC">Disposition of Comments</a> is available.</p>
<p class="mission">The <strong>mission</strong> of the <a href="http://www.w3.org/WAI/GL/">Accessibility Guidelines Working Group</a> (AG WG) is to develop specifications to make content on the Web accessible for people with disabilities and to participate in the development and maintainance of implementation support materials for the Web Content Accessibility Guidelines.</p>
<div class="noprint">
<p class="join">
<a href="https://www.w3.org/2004/01/pp-impl/35422/join">Join the Accessibility Guidelines Working Group.</a>
</p>
</div>
<section id="details">
<table class="summary-table">
<tr id="date_start">
<th> Start date </th>
<td></td>
</tr>
<tr id="date_end">
<th> End date </th>
<td> 31 October 2019</td>
</tr>
<tr>
<th> Chairs</th>
<td> Andrew Kirkpatrick, Joshue O Connor </td>
</tr>
<tr>
<th>Team Contacts</th>
<td>
<a href="mailto:[email protected]">Michael Cooper</a> (0.45 <abbr title="Full-Time Equivalent">FTE</abbr>)<br />
<a href="mailto:[email protected]">Shadi Abou-Zahra</a> (0.3 <abbr title="Full-Time Equivalent">FTE</abbr>) <br />TBD (.35 FTE)</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, no more than 3 per year. </td>
</tr>
</table>
</section>
<section id="background">
<h2>Background</h2>
<p>The Accessibility Guidelines Working Group is being chartered as an early update to the existing <a href="http://www.w3.org/2015/09/wcag-charter">Web Content Accessibility Guidelines Working Group charter</a>. As indicated in the current charter, the Working Group has been developing <span class="change">extensions to address gaps in WCAG 2.0</span><span class="delete">new work in the areas of mobile accessibility, low vision accessibility, and cognitive accessibility</span>. While it has proved useful to be developing proposals for new criteria in focused task forces, following additional discussion in the WCAG WG and W3C member company and public feedback, we believe that it will be more beneficial to develop these as a combined <span class="change">recommendation</span><span class="delete">normative guidance</span> in Web Content Accessibility Guidelines 2.1 <span class="change">rather than as separate extensions</span>. Specifically, the group has received feedback that the existence of multiple separate <span class="change">recommendations</span><span class="delete">normative specifications</span> (as extensions) risks deharmonization of global accessibility guideline use and increases the likelihood of conflicts <span class="change"> between specifications due to the recommendations not being developed together</span><span class="delete">between these separate documents</span>. As a result, the Working Group is now seeking to recharter in order to produce a WCAG 2.1 Recommendation.</p>
<p>The <span class="change">WCAG 2.1 recommendation will address gaps in WCAG 2.0 related to content and</span><span class="delete">Web Content Accessibility Guidelines 2.1 document</span> will incorporate updated <span class="change">Success Criteria to address content viewed on small display sizes and used with touch and stylus-based input modalities - features particularly common for mobile devices. WCAG 2.1 will also incorporate updated Success Criteria related to content and digital publications accessed by people with low-vision and with cognitive disabilities.</span><span class="delete">guidance to better address topics including low-vision and cognitive disabilities and to incorporate guidance to support mobile use cases and touch interfaces.</span> The Working Group has conducted research and initial development for these topics in task forces and expects to reach FPWD in February 2017.</p>
<p>The WCAG 2.1 update will be an incremental update to WCAG 2.0 rather than a major revision. WCAG 2.1 is designed to build on the WCAG 2.0 recommendation to ensure testability and technology independence, and will also ensure backward compatibility with WCAG 2.0. As with WCAG 2.0 in the past, the Working Group will periodically conduct reviews and provide feedback on WCAG 2.1 support materials created by other groups to help ensure that resources reflect the intent of the <span class="change">recommendation</span><span class="delete">specification</span>.</p>
<p>The Working Group intends to produce updated guidance for accessibility on a regular interval, starting with WCAG 2.1. Depending on the outcome of the requirements development for the next major update to WCAG, it may be necessary to pursue further dot-releases of WCAG until a major release is ready to be completed in time for a scheduled release date.</p>
<p>Improving support for testing WCAG is an important priority for the Working Group. The AG WG has an Accessibility Conformance Testing (ACT) Task Force which is developing a framework and repository of test rules to promote a unified interpretation of WCAG among different web accessibility test tools. The proposed recommendation-track framework will be generic enough to meet the needs of WCAG 2.0 but not exclude other standards, including WCAG 2.1. The framework will also allow the development of custom test rules to meet company requirements and best practices. This includes test rules for fully automated and semi-automated conformance testing in different web technologies, such as HTML, CSS, and WAI-ARIA. While this framework will add a layer of implemention for tool developers, it provides more consistency and comparability of the resulting test rules.</p>
<p>In addition to WCAG 2.1, and as a result of the research conducted in the various task forces and the experiences working with WCAG 2.0 for several years, a substantial evolution of WCAG is also needed to <span class="change">account for the complex interdependencies of content and user agent capabilities and to improve the usability of the specification.</span><span style="text-decoration:line-through">integrate guidance for content and user agents, and to address authoring tool requirements as an essential part of the process for delivering accessible information.With the closure of the User Agent and Authoring Tools Working Groups in the past year, many participants of these groups have joined the current WCAG Working Group in order to participate in the various task forces and have made the need for a major update clear.</span><span class="change">This incubation work is lower priority than the primary deliverable (WCAG 2.1).</span> The requirements for the next major version will be defined in parallel with (and are substantially informed by) the development of WCAG 2.1.</p>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>The group will:</p>
<ul>
<li><span class="change">Develop WCAG 2.1 to address gaps in WCAG 2.0 related to content and incorporate updated Success Criteria to address content viewed on small display sizes and used with touch and stylus-based input modalities - features particularly common for mobile devices. WCAG 2.1 will also incorporate updated Success Criteria related to content and digital publications accessed by people with low-vision and with cognitive disabilities.</span><span class="delete">Support the application of the Web Content Accessibility Guidelines to mobile and touch devices through the development of Normative updates to WCAG 2.0, as well as adding improvements to better support users with low vision and cognitive, language, and learning impairments.</span></li>
<li>Develop a framework and repository of test rules, to promote a unified interpretation of WCAG 2.0 and WCAG 2.1 among different web accessibility test tools</li>
<li><span class="change">Incubate</span> requirements for a major update to WCAG <span class="change">to address usability and conformance challenges.</span> <span class="delete">which may include the incorporation of user agent and authoring tool requirements.</span></li>
<li>Continue development of non-normative documents to support implementation of accessibility guidelines.</li>
</ul>
<div 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 required to be the central repository for accessibility support data.</li>
<li>The AG WG does not perform conformance evaluations and reviews.</li>
</ul>
</div>
<div>
<h3>Success Criteria</h3>
<p>The group will be considered successful if it produces stable versions of specifications addressing the work items listed in the <a href="#milestones">Milestones</a> section, with normative conformance requirements for implementation.</p>
</div>
</section>
<section id="deliverables">
<h2> Deliverables </h2>
<p>A detailed plan to achieve these milestones along with updates to the timeline is documented in the <a href="/WAI/GL/project">AG WG Project Management Plan</a>.</p>
<div id="normative">
<h3> Normative Specifications </h3>
<p> The Working Group will deliver the following W3C normative specifications: </p>
<dl>
<dt class="spec new">
<a href="#">Web Content Accessibility Guidelines 2.1</a>
</dt>
<dd>
<p>This specification defines updated guidelines to make web content accessible to people with disabilities, updating WCAG 2.0 with additional guidance to better address needs for users with low vision and cognitive disabilities, and users of touch and mobile interfaces.</p>
</dd>
<dt class="spec new">
<a href="https://www.w3.org/WAI/GL/task-forces/conformance-testing/work-statement">Accessibility Conformance Testing Framework <span class="change">(ACTF)</span> 1.0</a>
</dt>
<dd>
<p>This specification defines the format, logic, and implementation of accessibility test rules.</p>
</dd>
<dt class="spec new" style="text-decoration:line-through">
<a href="#">Accessibility Guidelines 3.0 (FPWD)</a>
</dt>
<dd style="text-decoration:line-through">
<p>First Public Working Draft of a major version update of guidance for accessibility. This version is expected to include substantial changes, including the incorporation of guidance for user agents and authoring tools.</p>
</dd>
</dl>
</div>
<div id="ig-other-deliverables">
<h3> Other Deliverables </h3>
<p> Other non-normative documents may be created such as: </p>
<ul>
<li>Working Group Notes to support understanding and interpretation of other deliverables as the need arises (Note)</li>
<li>Semi-annual updates of Understanding WCAG 2.0, to be published as a W3C Working Group Note or as a curated resource of the Working Group (Note)</li>
<li>Semi-annual updates of Understanding WCAG 2.1, to be published as a W3C Working Group Note or as a curated resource of the Working Group (Note)</li>
<li>Semi-annual updates of Techniques for WCAG 2, to be published as a W3C Working Group Note or as a curated resource of the Working Group (Note). The Techniques note will be a resource that covers WCAG 2.0 and 2.1 together, unlike the Understanding notes, which are separate documents for WCAG 2.0 and 2.1.</li>
<li>Requirements for Accessibility Guidelines 3.0 (Note).</li>
<li>Working Group Notes supporting the Accessibility Conformance Testing Framework 1.0, such as the Benchmarking Method (Note)</li>
<li>Errata for WCAG 2.1.</li>
</ul>
</div>
<div id="milestones">
<h3>Milestones</h3>
<ul>
<li>February 2017: FPWD for WCAG 2.1</li>
<li>January 2018: CR for WCAG 2.1</li>
<li>January 2018: FPWD for ACTF 1.0</li>
<li>June 2018: WCAG 2.1 Recommendation</li>
<li>August 2018: Requirements for Accessibility Guidelines 3.0 (Note)</li>
<li>October 2018: CR for ACTF 1.0</li>
<li style="text-decoration:line-through">October 2019: FPWD for Accessibility Guidelines 3.0</li>
<li>October 2019: ACTF 1.0 Recommendation</li>
</ul>
</div>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/Charter.html#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 recommendation-track document transition, including <a href="https://www.w3.org/2015/Process-20150901/#RecsWD" title="First Public Working Draft">FPWD</a> and <a href="https://www.w3.org/2015/Process-20150901/#RecsCR" title="Candidate Recommendation">CR</a>, and should be issued when major changes occur in a specification.</p>
<p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/2015/Process-20150901/#WGCharter">W3C Process Document</a>:</p>
<div>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="/WAI/APA/">Accessible Platform Architectures Working Group</a></dt>
<dd>Provide input into other W3C groups on accessibility requirements.</dd>
<dt><a href="/WAI/ARIA/">ARIA Working Group</a></dt>
<dd>Review and help develop WCAG 2.0 Techniques for WAI-ARIA.</dd>
<dt><a href="http://www.w3.org/Style/CSS/">Cascading Style Sheets Working Group</a></dt>
<dd>Advise on WCAG conformance interpretations of CSS features.</dd>
<dt class="change"><a href="http://www.w3.org/dpub/IG/">Digital Publishing Interest Group</a></dt>
<dd>Coordinate on accessibility guidelines that impact digital publishing.</dd>
<dt><a href="http://www.w3.org/WAI/EO/">Education and Outreach Working Group</a></dt>
<dd>Coordinate on making WCAG 2.0 usable by a wider audience, on developing or reviewing strategies and materials to increase awareness and to educate Web community about WCAG 2.0, ensure WCAG 2.0 uses terms from WAI Glossary properly.</dd>
<dt><a href="/International/">Internationalization Activity</a></dt>
<dd>Ensure that references to internationalization techniques are correct, and to ensure that language can be translated successfully.</dd>
<dt><a href="/Mobile/">Mobile Web Initiative</a></dt>
<dd>Explore relationship between <a href="http://www.w3.org/TR/mobile-bp/ ">Mobile Web best practices</a> and WCAG 2.0, and applicability of WCAG 2.0 to content displayed on mobile devices.</dd>
<dt><a href="http://www.w3.org/WAI/IG/">WAI Interest Group</a></dt>
<dd class="change">Provide input on group deliverables and explore ideas for consideration and further development.</dd>
<dt><a href="http://www.w3.org/WAI/??/">Web Platform Working Group</a></dt>
<dd>Send deliverables for review.</dd>
</dl>
<h3 id="external-coordination">External Organizations</h3>
<p class="change">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="http://www.etsi.org">European Telecommunications Standards Institute (ETSI)</a></dt>
<dd class="change">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 class="change"><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>
</div>
</section>
<section class="participation">
<h2 id="participation"> 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 <span class="change">implementers</span> of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute <span class="change">four hours</span> per week towards the Working Group. There is no minimum requirement for other Participants. </p>
<p class="change">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>
</section>
<section id="communication">
<h2> Communication </h2>
<p id="public"> Technical discussions for this Working Group are <a href="https://www.w3.org/2015/Process-20150901/#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 on a public repository, 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="">Accessibility Guidelines Working Group home page.</a>
</p>
<p> Most Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis. </p>
<p> This group primarily conducts its technical work on the public mailing list <a id="public-name" href="mailto:[email protected]">[email protected]</a> (<a href="http://lists.w3.org/Archives/Public/public-wai-gl/">archive</a>) or on <a id="public-github" href="https://github.com/w3c/wcag21">GitHub issues</a>. 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> At charter time, the decision policy is under review within the group in order to develop a decision process that supports greater asynchronous participation and minimizes dependence on weekly teleconferences. Until completed, the Working Group decision policy is as explained in Process Document <a href="/Consortium/Process/policies#Consensus">section 3.3 of the W3C Process Document</a>.</p>
<p>The <span class="change">Working</span> Group maintains specific procedures to establish and measure consensus and address objections in the <a href="/WAI/GL/decision-policy">AG Working Group Decision Policy</a>.</p>
<!-- <p>
This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/2015/Process-20150901/policies#Consensus"> W3C Process Document (section 3.3</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, but 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>
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional.
A call for consensus (CfC) will be issued for all resolutions (for example, via email and/or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue.
If no objections are raised on the mailing list by the end of the response period, the resolution will be considered to have consensus as a resolution of the (Working|Interest) Group.
</p>
<p>
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/policies#Votes">W3C Process Document (Section 3.4, 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="http://w3.org/Consortium/Patent-Policy-20040205/">W3C Patent Policy</a> (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations 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/2004/01/pp-impl/">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-documents">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/groups#GAGeneral">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/2015/Process-20150901/#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="http://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="">Rechartered 2017</a>
</th>
<td>3 January 2017</td>
<td>31 October 2019 </td>
<td>
<p>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.</p>
</td>
</tr>
</tbody>
</table>
</section>
</section>
</main>
<hr />
<footer>
<address>
<a href="mailto:[email protected]">Andrew Kirkpatrick</a>
</address>
<address>
<a href="mailto:[email protected]">Joshue O Connor</a>
</address>
<address>
<a href="mailto:[email protected]">Michael Cooper</a>
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2016 <a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> ( <a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://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>
<p>
<!-- $Date: 2016/11/17 18:06:27 $ -->
</p>
</footer>
</body>
</html>