/
eowg-2020.html
380 lines (377 loc) · 33 KB
/
eowg-2020.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
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8">
<title>Accessibility Education and Outreach Working Group (EOWG) 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>
ul.listspaced li {
margin-bottom: 0.5em;
}
ul#navbar {
font-size: small;
}
dl.spaced {
padding-top: 0;
margin-top: 1em;
}
dt.spec {
font-weight: bold;
margin-bottom: 0;
padding-bottom: 0;
}
dt.spec new {
background: yellow;
}
.spaced dd {
padding-bottom: 1.5em;
}
dd ul li {
margin-top: 0;
padding-top: 0;
}
dd p {
margin-bottom: 0;
padding-bottom: 0.25em;
margin-top: 0;
padding-top: 0.5em;
}
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="#intro">Introduction</a></li>
<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 Disclosures</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 Education and Outreach Working Group (EOWG) Charter</h1>
<p class="mission">The <strong>mission</strong> of the <a href="http://www.w3.org/WAI/EO">Accessibility Education and Outreach Working Group</a> is to develop strategies and resources to promote awareness, understanding, implementation, and conformance testing for W3C accessibility standards; and to support the accessibility work of other W3C Groups.</p>
<div class="noprint">
<p class="join"><a href="http://www.w3.org/2004/01/pp-impl/35532/join">Join the Accessibility Education and Outreach Working Group (EOWG).</a></p>
</div>
<section id="details">
<table class="summary-table">
<tr id="Duration">
<th> Start Date </th>
<td><i class="todo">[30 June 2020]<!--(@@date of the "Call for Participation", when the charter is approved)--></i></td>
</tr>
<tr id="CharterEnd">
<th> End Date </th>
<td>30 June 2023</td>
</tr>
<!-- <tr class="todo">
<th>Charter extension</th>
<td>See <a href="#history">Change History</a>. </td>
</tr>
-->
<tr>
<th> Initial Chairs </th>
<td> Brent Bakken (Pearson), Sharron Rush (Knowbility)</td>
</tr>
<tr>
<th> Team Contacts </th>
<td><a href="mailto:shawn@w3.org">Shawn Lawton Henry</a> (0.35<!-- @@ Judy confirm --> <abbr title="full-time equivalent">FTE</abbr> [external funds])<br><a href="https://www.w3.org/WAI/EO/wiki/EOWG_Charter_2020_Additional_Information#Staff_Support_and_External_Funding">More information on staff support and external funds</a></td>
</tr>
<tr>
<th> Meeting Schedule </th>
<td><strong>Teleconferences:</strong> Weekly. Additional teleconferences on specific topics, including Task Force topics, may also be held.<br>
<strong>Face-to-face:</strong> EOWG usually meets during the W3C Technical Plenary week. Additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 2 per year.<br>
<strong>Asynchronous:</strong> EOWG uses GitHub and surveys to support asynchronous contributions.</td>
</tr>
</table>
</section>
<section id="intro">
<h2>Introduction</h2>
<p>Accessibility is a key aspect of W3C's commitment to a Web for All. W3C standards include accessibility guidelines and technical specifications. However, accessibility is not as widely known and understood as many areas of W3C work. Understanding and implementing W3C's accessibility standards is quite complex. The Accessibility Education and Outreach Working Group addresses these challenges and <span class="listintro">supports W3C's mission by</span>: </p>
<ul class="listafterp listspaced">
<li><strong>Promoting W3C standards and resources for accessibility</strong>: Maintaining and extending the broad recognition of W3C standards and resources for accessibility, to further strengthen the credibility, authority, and trust in W3C as the leading technical body for web accessibility. </li>
<li><strong>Supporting uniform uptake of W3C standards for accessibility</strong>: Contributing to harmonized adoption of W3C standards in national and international standardization efforts (e.g. US Section 508, European EN 301 549, etc.), to enable organizations to use W3C standards and supporting educational, technical, and evaluation resources across multiple international markets.</li>
<li><strong>Supporting implementation of W3C standards for accessibility</strong>: Assisting a broad audience (developers, designers, project managers, etc.), including W3C membership, in understanding and implementing W3C standards.</li>
<li><strong>Engaging the community around W3C standards and resources</strong>: Engaging a wide multi-stakeholder community (industry, experts, researchers, users, etc.), throughout the development of W3C standards and resources, to improve the quality, consensus, and acceptance. </li>
<li><strong>Demonstrating W3C leadership in building a better web</strong>: Reinforcing the leadership of W3C as the go-to standardization body for web standards, to support the mission of leading the web to its full potential and to promote the universality of the web.</li>
</ul>
<p class="listintro">EOWG resources have proven valuable to promoting understanding, implementing, and testing conformance to W3C accessibility standards. The community relies on authoritative support from EOWG resources, for example:</p>
<ul class="listafterp">
<li><a href="https://www.w3.org/WAI/tutorials/">Web Accessibility Tutorials</a></li>
<li><a href="https://www.w3.org/WAI/eval/preliminary">Easy Checks - A First Review of Web Accessibility</a></li>
<li><a href="https://www.w3.org/WAI/WCAG20/quickref/">How to Meet WCAG: A customizable quick reference</a></li>
<li><a href="http://www.w3.org/WAI/eval/report-tool/">WCAG-EM Report Tool: Web Accessibility Evaluation Report Generator</a></li>
<li><a href="https://www.w3.org/WAI/perspectives/">Web Accessibility Perspectives – Videos that Explore the Impact and Benefits for Everyone</a></li>
</ul>
<p> This charter proposes continuing the Accessibility Education and Outreach Working Group to maintain continuity of established W3C Member engagement in successfully developing deliverables consistent with <a href="https://www.w3.org/2019/Process-20190301/#GAGeneral">W3C Process definition of a Working Group</a>.</p>
<p>For additional information, including analysis of group options, list of external funds, and answers to questions that come up during charter review, see <a href="https://www.w3.org/WAI/EO/wiki/EOWG_Charter_2020_Additional_Information">EOWG Charter 2020 Additional Information</a>.</p>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<!-- this charter has that in the introduction --
<p><i class="todo">Brief background of landscape, technology, and relationship to the Web, users, developers, implementers, and industry.</i></p>
-->
<p>Activities within the scope of this Accessibility Education and Outreach Working Group charter include:<br>
</p>
<ol>
<li>Develop resources that support understanding, implementing, and testing conformance to W3C accessibility standards.</li>
<li>Update, revise, and redesign existing EOWG resources to better meet users' needs in the current environment.</li>
<li>Conduct direct outreach activities to promote W3C accessibility standards and resources. Encourage and support other's outreach activities.</li>
<li>Support accessibility education and outreach throughout W3C, including in Accessibility Guidelines Working Group, Accessible Rich Internet Applications (ARIA) Working Group, Publishing@W3C activities, and other groups.</li>
</ol>
<section id="section-out-of-scope">
<h3 id="out-of-scope">Out of Scope</h3>
<p>EOWG will not develop W3C Recommendations.</p>
</section>
<section id="success-criteria">
<h3>Success Criteria</h3>
<ul>
<li>Updating and developing resources supporting EOWG's mission, defined in the Deliverables section below.</li>
<li>Greater use of WAI resources among W3C Members and the broader community, as indicated by tracking data and anecdotal references to WAI materials.</li>
</ul>
</section>
</section>
<section id="deliverables">
<h2> Deliverables </h2>
<p>EOWG primarily develops "WAI Resources" that are stable, vetted pages on the WAI website. EOWG may publish W3C Working Group Notes during this charter period. The Working Group will contribute to and deliver the following resources: </p>
<dl class="spaced">
<dt class="spec">Curricula on Web Accessibility</dt>
<dd>
<p>The <strong><a href="https://www.w3.org/WAI/curricula/">curricula</a></strong> provide a framework for building courses, as well as comparing and procuring courses. They provide learning outcomes, teaching ideas, ideas to assess knowledge, and teaching resources. Background is in the <a href="https://www.w3.org/WAI/EO/wiki/WAI_Curricula">Curricula Project Page</a>. The first curriculum, <a href="https://www.w3.org/WAI/curricula/introduction-to-web-accessibility/">Introduction to Web Accessibility</a>, was used as the basis for a <a href="https://www.w3.org/blog/2019/12/free-online-course-introduction-to-web-accessibility/">free online course</a>. </p>
<ul>
<li>Add supporting information to the overview page <a href="https://www.w3.org/WAI/curricula/">Curricula on Web Accessibility</a> (as started in <a href="https://www.w3.org/WAI/EO/wiki/WAI_Curricula/Supporting_Materials/">Supporting Materials Requirement Analysis</a>)</li>
<li>Update <a href="https://www.w3.org/WAI/curricula/introduction-to-web-accessibility/">Introduction to Web Accessibility</a> based on further input</li>
<li>Completed curriculum for developers – <a href="https://wai-curricula.netlify.com/curricula/developing-accessible-content/">in-progress draft Curriculum: Developing Accessible Content</a></li>
<li>Develop curriculum for designers, content authors, managers, and tester, as listed in the <a href="https://www.w3.org/WAI/curricula/#future-outline">Future Outline section</a>.</li>
</ul>
</dd>
<dt class="spec">Accessibility Roles and Responsibilities Mapping (ARRM)</dt>
<dd>
<p>ARRM guides project managers and others to know which roles (e.g., front-end developer, visual designer, content author) are responsible for which aspects of accessibility. (It is a much more robust and vetted version of this <a href="https://www.w3.org/community/wai-engage/wiki/Accessibility_Responsibility_Breakdown#Web_accessibility_by_roles">Accessibility Responsibility Breakdown</a>.) Background is in the <a href="https://www.w3.org/WAI/EO/wiki/ARRM_Project_-_Accessibility_Roles_and_Responsibilities_Mapping">ARRM Project page</a>. The following are links are to in-progress drafts. </p>
<ul>
<li>Refine, review, and publish <a href="https://www.w3.org/WAI/EO/wiki/Role_definition_document">Role definitions</a></li>
<li>Refine, review, and publish <a href="https://www.w3.org/WAI/EO/wiki/Role-Based_Decision_Tree">Role-Based Decision Tree</a></li>
<li>Develop, refine, review, and publish mappings for <a href="https://www.w3.org/WAI/EO/wiki/UX_Designer_Responsibilities_Mapping">UX Designer Responsibilities</a>, <a href="https://www.w3.org/WAI/EO/wiki/Visual_Designer_Responsibilities_Mapping">Visual Designer Responsibilities</a>, <a href="https://www.w3.org/WAI/EO/wiki/Content_Author_Responsibilities_Mapping">Content Author Responsibilities</a>, and <a href="https://www.w3.org/WAI/EO/wiki/Front-End_Developer_Responsibilities_Mapping">Front-End Developer Responsibilities</a></li>
</ul>
</dd>
<dt class="spec">Easy Checks - A First Review of Web Accessibility</dt>
<dd>
<p><strong><a href="https://www.w3.org/WAI/eval/preliminary">Easy Checks</a></strong> provides simple steps to help assess if a web page addresses accessibility. Information on the next iteration is in the <a href="https://www.w3.org/WAI/EO/wiki/Easy_Checks_Next_Gen">Easy Checks Next Generation definition/requirements</a>. It includes: </p>
<ul>
<li>Update existing content</li>
<li>Add new checks for WCAG 2.1 and 2.2 success criteria</li>
<li>Redesign the resource with simple checks on first page(s) and harder checks on other page(s)</li>
<li>Provide filtering functionality to improve usefulness and usability, and make the resource shorter for most users</li>
</ul>
</dd>
<dt class="spec">Web Accessibility Laws and Policies Database</dt>
<dd>
<p><strong><a href="https://www.w3.org/WAI/policies/">Web Accessibility Laws and Policies</a></strong> lists governmental policies related to web accessibility. </p>
<ul>
<li>Update existing listings after vetting</li>
<li>Actively research additional listings</li>
</ul>
</dd>
<dt class="spec">Before and After Demonstration (BAD)</dt>
<dd>
<p><strong><a href="https://www.w3.org/WAI/demos/bad/">Before and After Demonstration (BAD)</a></strong> is a multi-page resource that shows an inaccessible website and a retrofitted version of this same website. Each web page includes annotations and has an example evaluation report. </p>
<ul>
<li>Update BAD to address WCAG 2.1 success criteria, and WCAG 2.2 success criteria if resources are available</li>
<li>Update BAD to be more modern design and coding</li>
</ul>
</dd>
<dt class="spec">WCAG Support Materials</dt>
<dd>
<p>WCAG supporting technical materials include <a href="https://www.w3.org/WAI/WCAG21/Techniques/">Techniques for WCAG 2.1</a>, <a href="https://www.w3.org/WAI/WCAG21/Understanding/">Understanding WCAG 2.1</a>, and <a href="https://www.w3.org/WAI/WCAG21/quickref/">How to Meet WCAG: A customizable quick reference...</a>. Work on these may also include supplemental guidance that goes beyond WCAG requirements. Background: [https://github.com/w3c/wai-wcag-supporting-documents-redesign/wiki/Requirements-Analysis Requirements Analysis: WCAG Support Materials Redesign]. </p>
<ul>
<li>Update the user interface and visual design of WCAG support materials, in coordination with the Accessibility Guidelines Working Group (<a href="https://www.w3.org/WAI/GL/">AG WG</a>)</li>
</ul>
</dd>
<dt class="spec">Authoring Tool Accessibility Support Resources</dt>
<dd>
<p>Authoring tools are software and services that “authors” (web developers, designers, writers, etc.) use to produce web content (static web pages, dynamic web applications, etc.) Some background for the work listed below is in: <a href="https://github.com/w3c/wai-atag-report-tool/wiki/Requirements-analysis">Requirements Analysis for ATAG Report Tool</a>) and (<a href="https://github.com/w3c/wai-authoring-tools/wiki/Requirements-Analysis:-Authoring-Tools-List">Requirements Analysis for Authoring Tools List</a>). The following are links are to in-progress drafts. </p>
<ul>
<li>Complete <a href="https://github.com/w3c/wai-atag-report-tool">ATAG Report Tool (ART)</a></li>
<li>Complete <a href="https://wai-authoring-tools.netlify.com/authoring-tools/">Authoring Tools Accessibility Functionality List</a> and encourage submissions</li>
<li>Develop material to help project teams select authoring tools to support accessibility, and to encourage authoring tool vendors to meet Authoring Tool Accessibility Guidelines (<a href="https://www.w3.org/WAI/standards-guidelines/atag/">ATAG</a>)</li>
</ul>
</dd>
<dt class="spec">Accessibility Evaluation Support Resources</dt>
<dd>
<p>WAI has several <a href="https://www.w3.org/WAI/test-evaluate/">resources to help evaluate web accessibility</a>. Accessibility evaluation is also called “assessment”, “audit”, and “testing”. </p>
<ul>
<li>Develop next iteration of the <a href="https://www.w3.org/WAI/eval/report-tool/#!/">WCAG-EM Report Tool - Website Accessibility Evaluation Report Generator</a> (<a href="https://github.com/w3c/wcag-em-report-tool/issues">issues in GitHub</a>)</li>
<li>Update (or retire) evaluation resources such as <a href="https://www.w3.org/WAI/test-evaluate/combined-expertise/">Using Combined Expertise to Evaluate Web Accessibility</a></li>
</ul>
</dd>
<dt class="spec">Video Resources</dt>
<dd>
<p>WAI video resources currently include the <a href="https://www.w3.org/WAI/videos/standards-and-benefits/">Video Introduction to Web Accessibility and W3C Standards</a>, <a href="https://www.w3.org/WAI/test-evaluate/">Evaluating Web Accessibility Overview videos <i>(coming soon)</i></a>, and 10 <a href="https://www.w3.org/WAI/perspective-videos/">Web Accessibility Perspectives videos</a> that illustrate that accessibility is essential for some and useful for all (<a href="http://media.w3.org/wai/perspective-videos/compilation.mp4">complication of Perspectives Videos</a>). The following additional video series are introduced in the <a href="https://www.w3.org/WAI/EO/wiki/Video-Based_Resources">Video-Based Resources Project Page</a>: </p>
<ul>
<li>Develop a series of videos that illustrate the intent of each WCAG guideline and success criteria</li>
<li>Develop a series of videos that show people with disabilities using different assistive technologies and adaptive strategies, to supplement <a href="https://www.w3.org/WAI/people-use-web/">How People with Disabilities Use the Web</a></li>
<li>Develop videos on using <a href="https://www.w3.org/WAI/demos/bad/">Before and After Demonstration (BAD)</a> (after it is updated) for teaching and learning</li>
</ul>
</dd>
<dt class="spec">Other</dt>
<dd>
<p>EOWG will update other EOWG resources to address the current state of the art and make improvements for usability and consistency; for example, improve the translate-ability of the <a href="https://www.w3.org/WAI/planning/statements/">Accessibility Statement Generator Tool</a>. </p>
<p>EOWG will contribute to accessibility education and outreach related efforts throughout W3C, such as:</p>
<ul>
<li>Targeted messaging to different audiences</li>
<li>What's New in WCAG 2.2 resource</li>
<li>Material explaining the next generation of accessibility guidelines (code named “Silver”)</li>
<li>Editing and publishing some of the videos from the <a href="https://www.edx.org/course/web-accessibility-introduction">Introduction to Web Accessibility course</a></li>
<li>Accessibility issues and solutions with high-focus technologies (such as real-time communication (RTC)) and emerging technologies</li>
</ul>
<p>If projects are defined and editor resources are available, EOWG may also develop:</p>
<ul>
<li>Additional training material</li>
<li>Updates to the <a href="https://www.w3.org/WAI/people-use-web/">How People with Disabilities Use the Web</a> multi-page resource</li>
<li><a href="https://github.com/w3c/wai-eo-online-learning/wiki/Requirements-Analysis">Accessible Online Learning additions to EOWG Resources</a></li>
<li>List of training courses based on the <a href="https://www.w3.org/WAI/curricula/">WAI Curricula on Web Accessibility</a></li>
<li>Publishing-related information in coordination with <a href="https://www.w3.org/publishing/">Publishing@W3C</a> — This will most likely be adding information to existing EOWG Resources — for example, adding publishing examples to the sub-pages of <a href="https://www.w3.org/WAI/intro/people-use-web/">How People with Disabilities Use the Web</a>, although it could be new resources</li>
</ul>
</dd>
</dl>
<section id="timeline">
<h3>Timeline</h3>
<p>EOWG work priorities are evaluated regularly by EOWG and WAI staff. Work priorities are periodically revised based on current education and outreach needs, and the progress of deliverables in other WAI Working Groups with which EOWG has dependencies. Therefore, the priority of deliverables listed above are subject to change based on changed circumstances, and timelines below may be adjusted. Updated deliverable schedule and work status will be available on the <a href="@@">EOWG Current Projects</a> page.</p>
<p>Timeline of some major deliverables — with the latest expected date (most deliverables will likely be completed earlier):</p>
<ul>
<li>September 2020: WCAG Support Materials redesign - complete requirements analysis</li>
<li>December 2020: Curriculum - publish curriculum supporting materials and Developing Accessible Content Curricula</li>
<li>March 2021: ARRM - publish public review drafts of first set of materials</li>
<li>December 2021: Curriculum - publish Designing Accessible Content Curricula, Authoring Accessible Content Curricula, and Testing Content for Accessibility Curricula</li>
<li>September 2021: WCAG Support Materials redesign - publish redesign</li>
<li>March 2022: ARRM - publish public review drafts of second set of materials</li>
<li>August 2022: Before and After Demonstration (BAD) - publish update</li>
<li>October 2023: Web Accessibility Laws and Policies Database - publish updates</li>
<li>March 2023: ARRM - publish final versions of all materials</li>
<li>June 2023: Publish updated EOWG resources to address current issues</li>
</ul>
</section>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all relevant resources, this Working Group will seek <a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">horizontal review</a> for accessibility, internationalization, performance, privacy, and security with the relevant Working Groups, Interest Groups, and <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>, as appropriate. The Working Group will engage collaboratively with the horizontal review groups throughout development of each relevant resource.</p>
<p>Coordination with the following Groups will be made, per the <a href="https://www.w3.org/Consortium/Process/#WGCharter">W3C Process Document</a>: </p>
<div>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/WAI/GL/">Accessibility Guidelines Working Group</a></dt>
<dd>Coordinate on education and outreach on WCAG 2.2 and on future accessibility guidelines. Coordinate on improving the usability of WCAG support material.</dd>
<dt><a href="https://www.w3.org/publishing/">Publishing@W3C Groups</a></dt>
<dd>Coordinate on adding coverage of publishing issues in EOWG Resources, and on education and outreach around W3C Publishing work.</dd>
<dt><a href="https://www.w3.org/WAI/IG/">WAI Interest Group</a></dt>
<dd>Coordinate on reviewing EOWG Resources, and on gathering input for additional education and outreach support material.</dd>
<dt><a href="https://www.w3.org/WAI/ARIA/">Accessible Rich Internet Applications (ARIA) Working Group</a></dt>
<dd>Coordinate on understandability, approachability, and ease-of-use of ARIA support resources.</dd>
<dt><a href="https://www.w3.org/WAI/APA/">Accessible Platform Architectures (APA) Working Group</a></dt>
<dd>Coordinate on understandability, approachability, and ease-of-use of Working Group Notes.</dd>
<dt><a href="https://www.w3.org/International/">Internationalization Groups</a></dt>
<dd>Coordinate on internationalization issues in EOWG Resources, and on user interface for translations of EOWG Resources.</dd>
</dl>
<!--
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a href=""><i class="todo">[other name]</i> Working Group</a></dt>
<dd><i class="todo">[specific nature of liaison]</i></dd>
</dl>
-->
</div>
</section>
<section class="participation">
<h2 id="participation"> Participation </h2>
<p> To be successful, this Working Group is expected to have 10 or more active participants for its duration. Chairs and resource Editors are expected to contribute at least 6 hours per week towards the Working Group. Active participants are expected to contribute about 4 hours per week.</p>
<p> The group encourages W3C Member and public questions, comments, and issues on its document repositories and public mailing lists, as described in <a href='#communication'>Communication</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"> Content 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 Editors' Drafts will be developed in a public repository and will permit direct public contribution requests.
The teleconferences are not open to public participation.</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/EO">Accessibility Education and Outreach Working Group home page</a>.</p>
<p> This group primarily conducts its work through teleconferences, <a id="public-github" href="https://github.com/orgs/w3c/teams/wai-eo/repositories">GitHub</a>, and <a href="https://www.w3.org/2002/09/wbs/35532/all">surveys</a>; and occasionally uses <a href="https://www.w3.org/WAI/EO/wiki/EOWG_Meetings">wiki</a> and the e-mail list w3c-wai-eo@w3.org (<a href="http://lists.w3.org/Archives/Public/w3c-wai-eo/">archive</a>) for communication. 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 3.3</a>). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with the group participants 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. 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).
If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group. 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 3.4, Votes)</a> and includes no voting procedures beyond what the Process Document requires. </p>
</section>
<section id="patentpolicy">
<h2>Patent Disclosures </h2>
<p>The Working Group provides an opportunity to
share perspectives on the topic addressed by this charter. W3C reminds
Working Group participants of their obligation to comply with patent
disclosure obligations as set out in <a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Disclosure">Section
6</a> of the W3C Patent Policy. While the Working Group does not
produce Recommendation-track documents, when Working Group
participants review Recommendation-track specifications from other Working
Groups, the patent disclosure obligations do apply. 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<i> </i><a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a> for some of its deliverables, and for deliverables that are intended to be modified, it will use a more clearly permissive Creative Commons license (<a href="https://creativecommons.org/licenses/by/4.0/">CC-BY</a>) or the <a href="https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document">W3C Software and Document License</a>.</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 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 Changes </h3>
<p>This section lists important changes in this charter; the rationale for the changes is in the Introduction, per the <a href="https://www.w3.org/Consortium/Process/#CharterReview">W3C Process Document (section 5.2.3)</a>.</p>
<p>EOWG's previous charters: <a href="https://www.w3.org/WAI/EO/charter.htm">1998</a>, <a href="https://www.w3.org/WAI/EO/charter2.html">2000</a>, <a href="https://www.w3.org/WAI/EO/charter3.html">2002</a>, <a href="https://www.w3.org/WAI/EO/charter4.html">2005</a>, <a href="https://www.w3.org/WAI/EO/charter5.html">2010</a>, <a href="https://www.w3.org/WAI/EO/2015/charter6-2015-09">2015</a>, <a href="https://www.w3.org/WAI/EO/charter2017">2017</a>. The EOWG is renewing its charter in order to continue developing education and outreach resources supporting web accessibility.</p><p>The main additions from the previous charter are:</p>
<ul>
<li>WCAG Support Materials</li>
<li>Curricula on Web Accessibility</li>
<li>Before and After Demonstration (BAD)</li>
<li>Authoring Tool Accessibility Support Resources</li>
<li>Accessibility Roles and Responsibilities Mapping (ARRM)</li>
<li>Video Resources </li>
</ul>
</section>
</section>
</main>
<hr>
<footer>
<address>
<a href="mailto:shawn@w3.org">Shawn Lawton Henry</a>
</address>
<p class="copyright"> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2020 <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>