-
Notifications
You must be signed in to change notification settings - Fork 16
/
Copy pathOverview.html
557 lines (494 loc) · 37.1 KB
/
Overview.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
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="Keywords" content="Web Accessibility Initiative, web accessibility, WAI, W3C, World Wide Web, Web, WWW, Consortium, computer, access, accessibility, disability, disabilities, worldwide, international, W3, standard, technology, free, open source, software" />
<title>Strategic Planning for Web Accessibility</title>
<meta name="viewport" content="width=device-width">
<!-- When moving to the live environment any file or image links should have the following
removed from it:
http://www.w3.org/WAI/impl/
-->
<link href="http://www.w3.org/WAI/style/excol.css" rel="stylesheet" type="text/css" />
<!-- This should be used when the page goes live
<script type="text/javascript" src="//www.w3.org/WAI/scripts/excol/excol.js" xml:space="preserve"></script> -->
<!-- This should be removed with the page goes live -->
<script type="text/javascript" src="excol.js" xml:space="preserve"></script>
<link href="http://www.w3.org/WAI/impl/../wai-main.css" rel="stylesheet" type="text/css" />
<!--[if IE 7]><link rel="stylesheet" href="/WAI/ie-old.css" type="text/css" media="all" /><![endif]-->
<!-- Remove this when moving to the live environment -->
<style>
.draft.note {
background-color: #FFE6DA;
-webkit-border-radius: 3px;
-moz-border-radius: 3px;
border-radius: 3px;
margin: 1em;
padding: 5px 10px 8px;
}
.draft.note::before {
content: "Notes:";
font-weight: bold;
}
.draft.note p:first-child {
margin-top: 0;
}
.draft.note p:last-child {
margin-bottom: 0;
}
</style>
<!-- When moving to live environment this needs to move to wai-main.css -->
<style>
h1 {
margin-bottom: 1em;
}
/* ex-col jumping with hover/focus temp fix. Ideally this should be incorporated
into /WAI/style/excol.css to address this issue throughout the site */
.f_panelHead {
border-bottom: solid #fffaf5;
padding-left: 1.6em;
position: relative;
}
.f_panelHead.fs_hover, .f_panelHead.fs_focus {
border-bottom: solid #993300;
}
.f_panelHead.fs_selected {
border-bottom: solid #993300;
}
.f_expanderWrapper {
float: none;
position: absolute;
left: 0;
top: 0;
}
h1 .subtitle {
line-height: 2em;
}
/* It may be better not to add this to the core wai-main.css as it would make more
widespread changes to how to top links would look. */
p.totop a {
text-decoration: none;
}
p.totop a:hover, p.totop a:focus {
text-decoration: underline;
}
/* Again, it may be beneficial to move these classes into wai-main.css */
.eg {
color: #930;
font-size: 135%;
float:left;
padding-top: 0;
margin-top: 0;
margin-left: 10px;
}
.example-bar {
border-left: solid 2px #930;
margin-left: 55px;
padding: 0 15px;
}
.example-bar h4 {
margin: 0;
}
.example-bar ul {
/* This will need adjusted when moving to live */
list-style: disc outside url("http://www.w3.org/WAI/impl/../images/bullet-c60.gif");
padding-left: 1.3em;
margin-bottom: 0;
}
.key-actions {
list-style: none;
padding: 0px;
}
.key-actions li {
margin-left: 1.5em;
}
.key-actions li>span {
padding-left: 2em;
}
.key-actions li div p:first-child {
margin-top: 0.5em;
}
</style>
</head>
<body>
<div id="controls"><ul>
<li><a href="#skip"><img src="http://www.w3.org/WAI/impl/../../Icons/downinpage.png" alt="" /> Skip to Content</a></li>
<li> | <a href="/WAI/changedesign">Change text size or colors</a></li>
</ul></div>
<div id="masthead"><p id="logos"><a href="/" title="W3C Home"><img alt="W3C logo" src="http://www.w3.org/WAI/impl/../../Icons/w3c_home" /></a><a href="/WAI/" title="WAI Home"><img alt="Web Accessibility initiative" src="http://www.w3.org/WAI/impl/../../WAI/images/wai-temp" /></a></p></div>
<div id="tagline"><p>WAI: Strategies, guidelines, resources to make the Web accessible to people with disabilities</p></div>
<div id="nav">
<h2>Site Navigation</h2>
<p id="w3cnav"><a href="/">W3C Home</a></p>
<p id="subhomenav"><a href="/WAI/">Web Accessibility Initiative (WAI) Home</a></p>
<ol id="nav1" type="A">
<li><a href="../gettingstarted/Overview.html">Getting Started</a></li>
<li><a href="../users/Overview">Designing for Inclusion</a></li>
<li><a href="../guid-tech">Guidelines & Techniques</a></li>
<li class="current-nav "><a href="../managing">Planning & Implementing</a>
<ul>
<li class="nav-head">Policy Resources
<ol>
<li><a href="../Policy/harmon">Standards Harmonization</a></li>
<li><a href="../Policy/Overview">International Policies</a></li>
<li><a href="pol">Organizational Policies</a></li>
</ol>
</li>
<li class="current-nav nav-head">Managing Accessibility
<ol>
<li id="current-node" class="current-nav"><span class="label"><span id="current-icon">»</span>Strategic Planning</span></li>
<li><a href="improving">Improving Existing Sites</a></li>
<li><a href="../users/involving">Involving Users in Web Projects</a></li>
<li><a href="software">Selecting Authoring Tools</a></li>
</ol>
</li>
</ul>
</li>
<li><a href="../eval/Overview">Evaluating Accessibility</a></li>
<li><a href="../train">Presentations & Tutorials</a></li>
<li><a href="../about-links">Getting Involved with WAI</a></li>
</ol>
<div id="nav-static">
<div class="nav-discover">
<p><a href="/WAI/yourWAI"><strong><u>Discover new resources</u></strong> for people with disabilities, policy makers, managers, and you!</a></p>
</div>
<p class="translations"><a href="/WAI/wai-translations"><img src="http://www.w3.org/WAI/images/translations-med-1" alt="characters from different languages" /> Translations</a></p>
</div>
</div>
<div id="main">
<div id="skipwrapper"><a id="skip">-</a></div>
<!-- Remove this when moving to live environment -->
<p class="highlight-version"><strong>This is an internal Editor's Draft. The main page is at <a href="http://www.w3.org/WAI/impl/Overview.html">www.w3.org/WAI/impl/Overview.html</a><br>
Please send any suggestions, edits, or comments</strong> to the publicly-archived list: <a href="mailto:[email protected]">[email protected]</a>
</p>
<h1>Strategic Planning for Web Accessibility<br>
<span class="subtitle">Guidance for Developing a Plan for Your Organization or Project</span></h1>
<div id="contents">
<h2>Page Contents</h2>
<ul>
<li><a href="#goals">Determine Goal and Promote Awareness</a></li>
<li><a href="#resp">Establish Roles and Responsibilities</a></li>
<li><a href="#policy">Develop and Implement Organizational Policy</a></li>
<li><a href="#resource">Review Available Tools and Resources</a></li>
<li><a href="#train">Assess Skills and Deliver Training</a></li>
<li><a href="#project">Integrate into Project Life Cycle</a></li>
<li><a href="#share">Share Knowledge and Outcomes</a></li>
<li><a href="#monitor">Ensure Ongoing Monitoring and Maintenance</a></li>
</ul>
</div>
<div class="applicationNaviWrapper">
<div id="accordion" class="accordionWrapper">
<h2 id="intro" class="no-display">Introduction</h2>
<p>A successful plan for web accessibility addresses many areas of your organization and projects: training, quality assurance, recruiting, purchasing, marketing, content development, visual design, and more. As with other important aspects of website development, such as performance, accessibility is best approached as an integral and ongoing activity.</p>
<h3>What is this document for?</h3>
<p>This document provides IT managers, project managers, small business owners, accessibility consultants, and others with guidance on what to consider in developing an effective web accessibility plan for your specific organization or project. When you want more tactical guidance on fixing accessibility barriers in existing websites, see <a href="improving">Improving the Accessibility of Your Website</a>.</p>
<p>Note that additional content regarding each Key Action can be revealed using the button beside the action. You can expand all such content using the following buttons.</p>
<div class="f_controls_accordion f_fileToLoad_accordionControls"></div>
<p class="totop"><a href="#contents">back to page contents</a></p>
<h2 id="goal">Determine Your Goal and Gather Support</h2>
<p>Strategic planning, whether for a single project or broader organizational processes, benefits from broad backing and support. A clear and realistic accessibility goal is easy to communicate, aids in overall planning, and is recognizable when successfully achieved.</p>
<h3>Key actions</h3>
<ul class="key-actions">
<li><span class="f_panelHead">Identify and document the project accessibility goals.</span>
<div>
<p>Define project accessibility goals that are specific, measurable, achievable, realistic, and time-targeted. This helps to focus your team, clarifies what activities need to be planned, suggests how support can be best secured, and defines what deliverables are required. Goals may address the accessibility of a single website or online service, or may be more related to broader integration of accessibility into development processes and policies.</p>
</div>
</li>
<li><span class="f_panelHead">Explore your organization's current approach, understanding, and view of accessibility.</span>
<div>
<p>Use how your organization currently understands and views accessibility to help refine what goals can be realistically achieved. Review any existing policies or process, and explore the issue with key members of staff. As well as helping refine your goals, this should also highlight what activities might be beneficial in promoting those goals and gathering internal support.</p>
</div>
</li>
<li><span class="f_panelHead">Identify the key reasons for accessibility and, if needed, develop a business case.</span>
<div>
<p>Explore why accessibility has become important to help you prepare materials to persuade others and resolve resource prioritization clashes. Prepare a business case focused on key reasons to help in this process. Key reasons may also suggest additional necessary activities. For example, an executive directive to increase revenue by growing the website's reach to include people with disabilities, older people, and mobile web users will likely require more robust reporting of accessibility achievements and impact on revenue.</p>
</div>
</li>
<li><span class="f_panelHead">Promote awareness within your organization, and seek interested peers.</span>
<div>
<p>Persuade other project teams with a stake or role in your organization's online presence of the value of accessibility. Individuals in these teams may also be able to take on some accessibility responsibility or be helpful in adding additional influence for the project goals.</p>
</div>
</li>
<li><span class="f_panelHead">Secure commitment and backing, ideally from the executive and project management level.</span>
<div>
<p>Use your prepared business case to secure commitment to project goals, ideally by more senior management. This will simplify many issues down the line, especially when there are clashes in project or organizational priorities. Where you have limited influence within your organization, this backing will be invaluable.</p>
</div>
</li>
</ul>
<h3>Related resources</h3>
<ul>
<li><a href="/WAI/bcase/Overview">Developing a Web Accessibility Business Case</a> – Provides an outline of how incorporating accessibility can benefit your business or organization.</li>
</ul>
<p class="totop"><a href="#contents">back to page contents</a></p>
<h2 id="resp">Establish Roles and Responsibilities</h2>
<p>Identify and appoint individuals who are responsible for accessibility to ensure that any accessibility related issues are not neglected and that everyone on the team knows where to take accessibility questions.</p>
<p class="eg">e.g.</p>
<div class="example-bar">
<h3>Example responsibilities</h3>
<ul>
<li><b>Marketing</b> – Ensure good accessibility practices within the brand or design guidelines.</li>
<li><b>Quality assurance</b> – Test for and track accessibility issues within the code.</li>
<li><b>Development</b> – Maintain code libraries with accessible components.</li>
<li><b>Purchasing</b> – Ensure that organizational accessibility policy is incorporated within procurement processes.</li>
<li><b>Acceptance testing</b> – Ensure that any agency-delivered website or component meets your desired level of accessibility.</li>
<li><b>Recruitment</b> – Incorporate accessibility skills within recruitment profiles.</li>
</ul>
</div>
<h3>Key actions</h3>
<ul class="key-actions">
<li><span class="f_panelHead">Identify roles and assign responsibilities across different areas of the project.</span>
<div>
<p>For website development projects identify key project team members who will have responsibility for leading accessibility activities within their area and to function as primary contacts for accessibility questions. Ensure there is representation from across all project areas such as design, content creation, development, and quality assurance. In smaller teams it is likely that one individual will have primary responsibility for accessibility.</p>
</div>
</li>
<li><span class="f_panelHead">Assign responsibility to other organizational areas that impact on the provision of accessible websites.</span>
<div>
<p>For example, incorporating your accessibility policy into procurement processes reduces the risk that third-party supplied content or tools will introduce accessibility barriers. Consider other organizational areas such as information technology, human resources, marketing, organizational executive, and legal. Identify and appoint individuals to review policies and processes with accessibility in mind.</p>
</div>
</li>
<li><span class="f_panelHead">Communicate within the project and organization who the responsible parties are.</span>
<div>
<p>Communicate whom to take accessibility issues to and also highlight the ongoing commitment to accessibility. For wider organizational communication aim to inform key members of management and teams involved in website development activities.</p>
</div>
</li>
<li><span class="f_panelHead">Ensure any third-party providers are aware of your accessibility requirements and your expectations.</span>
<div>
<p>If you use an external company for the creation of part or all of your website then make them aware of your accessibility policy. Ultimately you, as the purchaser, still hold responsibility for website accessibility. Responsibility in this case means clear communication of what you expect in terms of accessibility and any additional accessibility acceptance testing.</p>
</div>
</li>
<li><span class="f_panelHead">Assign responsibility for each jurisdictional region your website spans.</span>
<div>
<p>Where your website is subject to many different legislations, consider appointing a responsible party for each region. Their role is to monitor legislative change relating to accessibility and ensure that organizational policies are reviewed and updated appropriately.</p>
</div>
</li>
</ul>
<h3>Related resources</h3>
<ul>
<li><a href="/community/wai-engage/wiki/Accessibility_Responsibility_Breakdown">Accessibility Responsibility Breakdown</a> – Explores <abbr title="Web Content Accessibility Guidelines">WCAG</abbr> 2.0 success criteria by project role.</li>
</ul>
<p class="totop"><a href="#contents">back to page contents</a></p>
<h2 id="policy">Develop and Implement Organizational Policy</h2>
<p>Establishing an organizational policy for web accessibility is a critical milestone in ensuring that web accessibility is understood as a strategic component of the organizational structure. Explicit policy statements document the commitment to accessibility and help to set expectations both internally and externally.</p>
<h3>Key actions</h3>
<ul class="key-actions">
<li><span class="f_panelHead">Identify any existing policies related to accessibility.</span>
<div>
<p>Review any existing policies and commitments relating to accessibility. They may provide a foundation for a more comprehensive policy. For example, there may be policies relating to work ethics, equal opportunities, diversity, and corporate social responsibility (CSR) that could be relevant. Reviewing existing policies will provide more insight on the organizational understanding and view of accessibility.</p>
</div>
</li>
<li><span class="f_panelHead">Establish a policy stating your organization's commitment to web accessibility.</span>
<div>
<p><a href="pol">Developing Organizational Policies on Web Accessibility</a> provides details on how to develop your organizational policy.</p>
</div>
</li>
<li><span class="f_panelHead">Communicate and promote the policy across relevant parts of the organization.</span>
<div>
<p>Acknowledge your intent by making internal and external audiences aware of your policy and commitments. Promote your policy internally to improve awareness for subsequent projects.</p>
</div>
</li>
<li><span class="f_panelHead">Review related policies and procedures to incorporate the accessibility policy throughout.</span>
<div>
<p>Most organizations have policies governing both broad aspects of doing business as well as specific areas such as procurement or marketing. An effective accessibility strategy will develop statements that can be integrated into policies already in place. For example, your procurement processes would outline how externally purchased websites or elements will meet your accessibility policy and what acceptance criteria are acceptable.</p>
</div>
</li>
<li><span class="f_panelHead">Announce your organizational commitments publicly for accountability.</span>
<div>
<p>Outline your organization's commitments in a public policy to help set expectations for your website visitors and reaffirm public accountability internally. This would be related to your organizational policy but in a format more suited to a non-technical, general audience.</p>
</div>
</li>
</ul>
<h3>Related resources</h3>
<ul>
<li><a href="pol">Developing Organizational Policies on Web Accessibility</a> – Describes considerations when making simple or comprehensive policies for organizations.</li>
</ul>
<p class="totop"><a href="#contents">back to page contents</a></p>
<h2 id="resource">Review Available Tools and Resources</h2>
<p>When planning a new website you will need to consider what standard organizational resources you are required to use and how accessible these are. Many organizations standardize IT operations using common development tools, design patterns, and code libraries. Review these resources and integrate accessibility improvements in order to efficiently achieve extensive change.</p>
<h3>Key actions</h3>
<ul class="key-actions">
<li><span class="f_panelHead">Identify web authoring tools and review how well they support your accessibility goals.</span>
<div>
<p>Review how well your authoring tools and processes support accessibility. As well as considering how the tools help create accessible content, review how they support content editors with disabilities. Content management systems (CMS) and templates have a fundamental impact on accessibility and are difficult to change later on. Also, consider other processes involved in the production of other online content for your website, for example, documents or video creation.</p>
</div>
</li>
<li><span class="f_panelHead">Review organizational design and development resources.</span>
<div>
<p>Assess any organizational resources such as design or branding guidelines, content guidelines, standard coding libraries, or guidelines for online services. Aim to ensure that they are supportive of the organizational accessibility goals. Ensuring shared resources such as these are accessible will have a significant impact on any subsequent online projects using them.</p>
</div>
</li>
<li><span class="f_panelHead">Research lessons learned from the development of other websites within the organization.</span>
<div>
<p>Identify and review any accessibility evaluations from similar previous projects. Aim to identify common good practices, and approaches that are known to cause problems. Seek out any accessibility resources used by previous project teams. For organizational change, evaluating existing websites will be an important early activity in understanding the extent of work required.</p>
</div>
</li>
<li><span class="f_panelHead">Identify external sources of accessible information and examples.</span>
<div>
<p>Consider what accessibility information and advisory resources are available external to your organization. Websites, forums, mailing lists, and books are invaluable in exploring accessibility in general and creating accessible solutions. Build a library of these resources for project team members, ideally allowing for their contributions.</p>
</div>
</li>
</ul>
<h3>Related resources</h3>
<ul>
<li><a href="/WAI/intro/atag.php">Authoring Tool Accessibility Guidelines (ATAG) Overview</a> – Guidelines on assessing and creating accessible website authoring tools.</li>
<li><a href="/WAI/eval/Overview">Accessibility Evaluation Resources</a> – Resources and guidelines on assessing and reviewing website accessibility.</li>
<li><a href="/WAI/tutorials/">Web accessibility tutorials</a> – Guidance on how to create websites that meet <abbr title="Web Content Accessibility Guidelines">WCAG</abbr>.</li>
<li><a href="/WAI/demos/bad/">Before and After Demonstration (BAD)</a> – Shows an inaccessible website and a retrofitted accessible version of the same website.</li>
</ul>
<p class="totop"><a href="#contents">back to page contents</a></p>
<h2 id="train">Assess Skills and Deliver Training</h2>
<p>The ability to create an accessible website is largely dependent on the skills and expertise of the team of designers, developers, and content creators. A frequent cause of accessibility barriers is simply the lack of awareness of the subject. Aim to develop more understanding of the need and value of accessibility, as well as improving the skills of key personnel.</p>
<p class="eg">
e.g.
</p>
<div class="example-bar">
<h4>Example training sessions</h4>
<ul>
<li><strong>Benefits of accessible websites</strong> for management.</li>
<li><strong>Introduction to accessibility</strong> for many departments, such as <abbr title="Human Resources">HR</abbr>.</li>
<li><strong>Visual design and accessibility</strong> for designers and marketing.</li>
<li><strong>Accessible web development</strong> for programmers and developers.</li>
<li><strong>Writing accessible content</strong> for non-technical content authors.</li>
</ul>
</div>
<h3>Key actions</h3>
<ul class="key-actions">
<li><span class="f_panelHead">Assess expertise and motivation of key project personnel.</span>
<div>
<p>Carry out an evaluation of technical, design, and content creation staff. Aim to identify what, if any, gaps in understanding and expertise exist. Also consider how motivated team members are to deliver accessible solutions. Use this information to create training solutions that respond to the needs of your team.</p>
</div>
</li>
<li><span class="f_panelHead">Budget and plan general awareness raising and targeted skills building training for team members.</span>
<div>
<p>All team members and, ideally, peer project managers will benefit from general accessibility awareness and understanding training. Depending on the size of your team you may conduct more involved training for all team members, or target specific key groups or individuals. For example, front-end developers receive training that differs from content creators. Consider on-going training at regular intervals to evolve the expertise and keep team knowledge up-to-date. Adopt developed training more broadly as part of your training offering.</p>
</div>
</li>
<li><span class="f_panelHead">Consider the potential need to recruit personnel with specific accessibility expertise.</span>
<div>
<p>Target recruitment for personnel with particular accessibility expertise. Use new experienced staff to boost the overall skills already within the team. They can help develop or deliver training sessions, or act as mentors to help build the skills of key team members.</p>
</div>
</li>
<li><span class="f_panelHead">Include accessibility requirements as standard criteria in the recruitment process.</span>
<div>
<p>As your organization develops, projects will benefit from accessibility recruitment requirements being incorporated into recruitment criteria. This helps build and maintain the overall skill level and capabilities across the organization.</p>
</div>
</li>
</ul>
<h3>Related resources</h3>
<ul>
<li><a href="/WAI/training/Overview">Developing Web Accessibility Presentations and Training</a> – Helps you develop presentations and training on web accessibility.</li>
<li><a href="/WAI/tutorials/">Web accessibility tutorials</a> – Guidance on how to create websites that meet <abbr title="Web Content Accessibility Guidelines">WCAG</abbr>.</li>
</ul>
<p class="totop"><a href="#contents">back to page contents</a></p>
<h2 id="project">Integrate into Project Life Cycle</h2>
<p>Regardless of your development methodology, integrate accessibility throughout the project from early planning to final deployment. This may by accomplished by comprehensive evaluations at key milestones, or more light-weight reviews following each sprint. Start early in the process to reduce the risk of being constrained by early design decisions that become expensive to change later in the project. Promote accessibility within the team as a positive challenge to encourage creative thinking of accessible solutions.</p>
<h3>Key actions</h3>
<ul class='key-actions'>
<li><span class="f_panelHead">Start early and factor for iterative checks.</span>
<div>
<p>Start early to increase the positive impact for target audiences, reduce costs, and increase adoption of accessible design and coding features.</p>
<p>Run iterative checks to allow teams to explore different solutions for complex issues. The process of exploring solutions will develop more understanding of accessibility issues. Iterative evaluation will also reveal some barriers that only become apparent when other barriers have been removed.</p>
</div>
</li>
<li><span class="f_panelHead">Evaluate all project design assets.</span>
<div>
<p>Review all design assets, including resources such as visual design and interaction concepts, wireframes, and prototypes. This will help identify barriers before significant coding work takes place. Consider reviewing resources such as personas, user stories, and storyboards. Incorporating the needs of users with disabilities into these assets can help designers and developers better understand how people will interact with your website.</p>
</div>
</li>
<li><span class="f_panelHead">Review accessibility solutions with key team members.</span>
<div>
<p>Have representatives from all relevant project teams review identified barriers. This helps create a shared understanding of solution constraints, such as organizational brand guidelines or authoring tool limitations. Where there are resource constraints, aim to prioritize the issues that have the greatest impact yet require fewer resources to address.</p>
</div>
</li>
<li><span class="f_panelHead">Evaluate throughout the project and ensure a comprehensive evaluation on completed website.</span>
<div>
<p>Plan evaluations for key milestones or sprints throughout the development process. Key pages or processes and stand alone components can be evaluated as they become available. Aim to ensure that what has been created meets the standards outlined in your organizational policy.</p>
<p>Include input from users with disabilities as part of your evaluations. Encourage team members to attend testing sessions as this provides considerable insight into barriers and helps team members identify with the problems caused.</p>
<p>Identified barriers should be reviewed by key team members to identify suitable solutions which should then be fed into the next development cycle.</p>
</div>
</li>
<li><span class="f_panelHead">Plan for a reasonable gap between completion and go-live to address any final barriers.</span>
<div>
<p>Running an accessibility evaluation in the last stages of a project will increase the risk that barriers will be found when there is no time or budget to address them. Starting early and integrating the evaluations will reduce this risk. Even with an iterative evaluation approach it could be that barriers are only found when the complete site is tested. Plan for some final time before go-live to reduce this risk.</p>
</div>
</li>
</ul>
<h3>Related resources</h3>
<ul>
<li><a href="/WAI/users/involving">Involving users with disabilities</a> – Provides guidance on including users with disabilities in accessibility evaluations.</li>
</ul>
<p class="totop"><a href="#contents">back to page contents</a></p>
<h2 id="share">Share Knowledge and Outcomes</h2>
<p>Sharing what is learned as part of a project is key to ongoing improvements in accessibility. Keeping executives, stakeholders, key departments, and the broader organization informed increases organizational awareness and also ensures that there is practical knowledge available for subsequent projects.</p>
<h3>Key actions</h3>
<ul class="key-actions">
<li><span class="f_panelHead">Report to stakeholders the project accessibility successes and difficulties.</span>
<div>
<p>Keep stakeholders and management aware of accessibility progress made. Consider what information is most relevant to their needs and how frequently it is required. For example, if they are concerned with legal compliance issues then it is important to report on how well websites conform with your organizational policy. If their primary concern is corporate social responsibility then they may be interested in PR activities, publicity, and impact on brand.</p>
</div>
</li>
<li><span class="f_panelHead">Report design and technical achievements and knowledge to other website teams.</span>
<div>
<p>Consider how successful approaches, techniques, and resources can be best communicated to other website teams. Sharing spreads best practice solutions and helps reduce the chance of the same problems occurring elsewhere. Use this as an opportunity to highlight the value of accessibility, with concrete examples, to help change attitudes towards accessibility. As knowledge of accessibility spreads through your organization, having a known platform for communicating this information can be invaluable as teams will come to see it as a go-to resource when developing websites.</p>
</div>
</li>
<li><span class="f_panelHead">Create internal publicity for new website accessibility.</span>
<div>
<p>Share website accessibility achievements as part of general organization wide website communications. Aim to build awareness and highlight the organization's positive approach and the benefits it brings.</p>
</div>
</li>
<li><span class="f_panelHead">Consider creating an organization wide accessibility monitoring and reporting framework.</span>
<div>
<p>Develop a standard reporting framework to help track and show accessibility improvements. When your organization has many websites, such a framework can be used to provide an overview of improvements and areas still in need of attention. For individual websites, having a standard reporting framework will help show progress.</p>
</div>
</li>
</ul>
<p class="totop"><a href="#contents">back to page contents</a></p>
<h2 id="monitor">Ensure Ongoing Monitoring and Maintenance</h2>
<p>Monitoring website accessibility is important to ensure that all the good work involved in creating the website is not undermined. For organizations with many websites and services an effective monitoring process is an important part of broader accessibility efforts.</p>
<h3>Key actions</h3>
<ul class='key-actions'>
<li><span class="f_panelHead">Create a plan for regular checks and audits.</span>
<div>
<p>Updates to content and website maintenance work may introduce accessibility barriers so it is important to plan for regular monitoring. Create a plan for regular reviews of random sample content from the website. Ensure that clear responsibility is assigned for the checks and there are clear escalation paths for identified issues.</p>
</div>
</li>
<li><span class="f_panelHead">Update publication process to include accessibility checks.</span>
<div>
<p>Aim to incorporate accessibility checks as part of your web content publishing workflow. This ensures that few errors are introduced and helps identify additional training needs.</p>
</div>
</li>
<li><span class="f_panelHead">Implement a public feedback process for accessibility issues.</span>
<div>
<p>Feedback from your website users can be an invaluable resource in improving website accessibility. Plan for a clear and simple way to allow users to raise accessibility issues. Ensure that the process includes a suitable mechanism to respond to feedback. Ensure there is adequate infrastructure to deal with any queries and escalate to responsible parties for immediate resolution or inclusion in the next maintenance release.</p>
</div>
</li>
<li><span class="f_panelHead">Schedule regular reviews and updates of policies and processes.</span>
<div>
<p>Following project completion conduct a review of organizational policies and procedures related to website development. Aim to update them based on how well they support the creation of accessible websites and in response to user feedback.</p>
<p>For example, your policy may say little regarding video transcripts and visitor feedback consistently highlights this as a problem. This could be addressed by improving your video creation guidelines and review process to include better instructions on transcripts.</p>
</div>
</li>
</ul>
<h3>Related resources</h3>
<ul>
<li><a href="/WAI/eval/considerations#ongoing">Evaluation Approaches for Specific Contexts</a> – Describes evaluation during ongoing monitoring.</li>
</ul>
<p class="totop"><a href="#contents">back to page contents</a></p>
</div>
</div>
</div>
<div id="footer">
<h2>Document Information</h2>
<p><strong>Status:</strong> <strong>Draft</strong> approved by <a href="/WAI/EO/">EOWG</a> updated October 2014 (first published: October 2002)<br>
Editors: <a href="/People/#kevin">Kevin White</a> and <a href="/People/shadi/">Shadi Abou-Zahra</a>. Previous Editors: <a href="/People/Brewer/">Judy Brewer</a> and Sarah Horton. Contributors: Sharron Rush, Anna Belle Leiserson, and <a href="/WAI/EO/EOWG-members.html">participants</a> of the <a href="/WAI/EO/">Education and Outreach Working Group</a>. Updated with support from <a href="/WAI/ACT/" shape="rect"><acronym title="Web Accessibility Initiative - Cooperation Framework for Guidance on Advanced Technologies, Evaluation Methodologies, and Research Agenda Setting to Support eAccessibility">WAI-ACT</acronym></a>, a project of the European Commission <acronym title="Information Society Technologies">IST</acronym> Programme.</p>
<div class="footer-nav">
<p>[<a href="/WAI/sitemap.html">WAI Site Map</a>] [<a href="/WAI/sitehelp.html">Help with WAI Website</a>] [<a href="/WAI/search.php">Search</a>] [<a href="/WAI/contacts">Contacting WAI</a>]<br clear="none" />
<strong>Feedback welcome to <a href="mailto:[email protected]">[email protected]</a></strong> (a publicly archived list) or <a href="mailto:[email protected]">[email protected]</a> (a WAI staff-only list).</p>
</div>
<div class="copyright">
<p>Copyright © 2014 W3C <sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>) <a href="/Consortium/Legal/ipr-notice">Usage policies apply</a>.</p>
</div>
</div>
</body>
</html>