forked from w3c/wai-planning-and-implementation
-
Notifications
You must be signed in to change notification settings - Fork 0
/
improving.html
199 lines (180 loc) · 15.9 KB
/
improving.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
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<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>Web Accessibility First Aid: Approaches for Interim Repairs</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="//www.w3.org/WAI/impl/../wai-main.css" rel="stylesheet" type="text/css" />
<link href="wai-style-changes.css" rel="stylesheet" type="text/css" />
<!--[if IE 7]><link rel="stylesheet" href="/WAI/ie-old.css" type="text/css" media="all" /><![endif]-->
</head>
<body class="draft">
<header>
<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>
</header>
<nav 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><a href="Overview">Planning & Managing</a></li>
<li id="current-node" class="current-nav"><span class="label"><span id="current-icon">»</span>Improving Existing Sites</span></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>
</nav>
<main id="main" role="main">
<div id="skipwrapper"><a id="skip">-</a></div>
<!-- Remove this when moving to live environment -->
<div class="status">
<p><strong>Status:</strong> This is an in-progress, unapproved draft.</p>
</div>
<h1>Web Accessibility First Aid: <br/>Approaches for Interim Repairs</h1>
<div id="contents">
<h2>Page contents</h2>
<ul>
<li><a href="#intro" class="no-display">Introduction</a></li>
<li><a href="#resources">Important Resources</a></li>
<li><a href="#understand">What is Accessibility?</a></li>
<li><a href="#explore">What are the Issues?</a></li>
<li><a href="#scope">What is your Scope?</a></li>
<li><a href="#target">What is your Target?</a></li>
<li><a href="#repair">What is your Strategy?</a></li>
<li><a href="#plan">Longer Term: Planning and Managing</a></li>
</ul>
</div>
<h2 id="intro" class="no-display">Introduction</h2>
<p>Do you need to urgently address web accessibility of an existing site, application or in an on-going development project? This page provides guidance and pointers to resources to help you address critical issues quickly. A more comprehensive guide to help you address accessibility more thoroughly throughout the design and development process is provided in <a href="https://www.w3.org/WAI/impl/Overview">Planning and Managing Web Accessibility</a>.</p>
<h2 id="resources">Important Resources</h2>
<p>The following resources may be helpful right away to the designers and developers in your team:</p>
<ul>
<li><a href="https://www.w3.org/WAI/gettingstarted/tips/">Tips for Getting Started</a> — Practical considerations with examples for designing, writing, and developing accessible web content.</li>
<li><a href="https://www.w3.org/WAI/tutorials/">Web Accessibility Tutorials</a> — Detailed information on specific topics with guidance on addressing accessibility requirements.</li>
<li><a href="https://www.w3.org/WAI/WCAG20/quickref/">How to Meet WCAG 2.0</a> — A customizable quick reference to Web Content Accessibility Guidelines (WCAG) 2.0.</li>
</ul>
<h2 id="understand">What is Accessibility?</h2>
<p>If you are new to accessibility, it is often helpful to first get a basic idea of the topic. Here are some quick introductions:</p>
<ul>
<li><a href="https://www.w3.org/standards/webdesign/accessibility">W3C - Accessibility</a> — Introduces essential concepts, rationale, and resources.</li>
<li><a href="https://www.w3.org/WAI/perspectives">Web Accessibility Perspectives</a> — Short non-technical videos that introduce accessibility features and their benefits for everyone.</li>
</ul>
<p>If there is a need, more in-depth introductions and background is provided in <a href="https://www.w3.org/WAI/intro/people-use-web/">How People with Disabilities Use the Web</a>. Specifically the <a href="https://www.w3.org/WAI/intro/people-use-web/principles">Accessibility Principles</a> section of the resource introduces the accessibility requirements and guidelines.</p>
<h2 id="explore">What are the Issues?</h2>
<p>If you already know the specific issues you need to address, you can skip this section. If you are starting to address accessibility without background, the following manual helps you get a rough idea of the current situation on your website:</p>
<ul>
<li><a href="https://www.w3.org/WAI/eval/preliminary.html">Easy Checks — A First Review of Web Accessibility</a> — Simple checks that can be carried out by anyone, regardless of technical skills and accessibility knowledge.</li>
</ul>
<p>Some web accessibility evaluation tools may help you further explore the accessibility on your website:</p>
<ul>
<li><a href="https://www.w3.org/WAI/ER/tools/">List of Web Accessibility Evaluation Tools</a> — Customizable list that allows you to search for different types of tools.</li>
</ul>
<p>Note: some web accessibility evaluation tools may be complex and confusing to use for people new to accessibility. They typically only check a subset of issues, and may be prone to misleading results.</p>
<p>To get a complete picture of the situation, a comprehensive evaluation may be needed. Such thorough evaluations require accessibility expertise. The following resources help you evaluate your website:</p>
<ul>
<li><a href="https://www.w3.org/WAI/eval/conformance.html">Website Accessibility Conformance Evaluation Methodology (WCAG-EM)</a> — Provides a structured approach to help evaluate websites for accessibility.</li>
<li><a href="https://www.w3.org/WAI/eval/report-tool/">WCAG-EM Report Tool</a> — Free online tool to help create evaluation reports following the WCAG-EM procedure.</li>
</ul>
<h2 id="scope">What is your Scope?</h2>
<p>You may not be able to address all the issues on every part of your website at once. To determine which parts you may need to improve right away, and which to address in later stages, consider the following:</p>
<ul>
<li><strong>Key tasks</strong>, such as registration, purchase, or checkout processes. Include all steps in each of these flows.</li>
<li><strong>Key content</strong>, such as frequently accessed content and content that is relevant to people with disabilities.</li>
<li><strong>Reported content</strong>, that has known barriers; for example, from user comments submitted through the website feedback form.</li>
<li><strong>In-development content</strong>, such as areas of the website that are currently being redesigned, to avoid the creation of new barriers.</li>
</ul>
<p>Within your scope of repair, consider prioritizing what you repair first by focusing on:</p>
<ul>
<li><strong>High-impact repairs</strong>
<ul>
<li>Appear on multiple web pages, such as navigation bars</li>
<li>Appear on frequently-used web pages, such as the home page</li>
<li>Are critical to complete processes, such as purchase forms</li>
<li>Web Content Accessibility Guidelines (WCAG) Level A issues</li>
</ul>
</li>
<li><strong>Low-effort repairs</strong>
<ul>
<li>Require less time, cost, or skills to repair</li>
<li>Requires less testing and validation</li>
</ul>
</li>
</ul>
<h2 id="target">What is your Target Level of Accessibility?</h2>
<p>The generally accepted target for accessibility is <a href="https://www.w3.org/WAI/intro/wcag">Web Content Accessibility Guidelines (WCAG) 2.0</a> Level AA. This may already be the standard specified in your organizational policy or it may be the legal requirement for your website.</p>
<p>You may need to define a phased approach with different dates for different levels. For example, meet particular WCAG 2.0 success criteria in the next release, and meet all Level A and Level AA success criteria in the following release.</p>
<p>Note that in some cases, some Level AAA success criteria may be fairly easy to meet. For example, refining appropriate link text (2.4.9, Level AA) and heading structure (2.4.10, Level AAA) may be easy to address together when revising content.</p>
<h2 id="repair">What is your Strategy?</h2>
<p>Consider the following tips to help you implement accessibility repairs:</p>
<ul>
<li><strong>Leverage the different skills in your team</strong> — While many tasks will be for developers, other roles have plenty to contribute. For example, designers can select better colors and content authors can improve the wording of links, headings, and text alternatives. The resource <a href="https://www.w3.org/WAI/eval/reviewteams.html">Using Combined Expertise to Evaluate Web Accessibility</a> may be helpful.</li>
<li><strong>Communicate requirements across your team</strong> — Ensure that everyone involved in repairs understands the basics of web accessibility and the specific requirements they need to address. Distribute the <a href="resources">Important Resources</a> to the relevant members of your team.</li>
<li><strong>Validate solutions as early as possible</strong> — Ensure that any solutions adequately address the issues raised to avoid implementing changes that do not work in practice. If at all possible, it is important to involve people with disabilities in such validation. The resources <a href="https://www.w3.org/WAI/users/involving">Involving Users in Web Projects for Better, Easier Accessibility</a> and <a href="https://www.w3.org/WAI/eval/users.html">Involving Users in Evaluating Web Accessibility</a> provide more background.</li>
<li><strong>Optimize your Tools</strong> — Explore and configure accessibility settings in the authoring tools you use to create web content, such as your content management system (CMS). The resources <a href="https://www.w3.org/WAI/eval/selectingtools">Selecting Web Accessibility Evaluation Tools</a> and <a href="https://www.w3.org/WAI/impl/software">Selecting and Using Authoring Tools for Web Accessibility</a> may be helpful.</li>
</ul>
<h2 id="plan">Longer Term: Planning and Managing</h2>
<p>Once you have addressed some of the most critical web accessibility issues on your website and begun to address the rest, it is essential you plan to integrate accessibility throughout the design and development process. The <a href="https://www.w3.org/WAI/impl/Overview">Planning and Managing Web Accessibility</a> guide can help you develop that plan.</p>
<aside class="side-box contribute" role="complementary">
<h2 class="heading">Help improve this page</h2>
<p>Please share your ideas, suggestions, or comments via email to the publicly-archived list <a href="mailto:wai-eo-editors@w3.org?subject=%5bImproving%20the%20Accessibility%20of%20Your%20Website%5d">wai-eo-editors@w3.org</a> or via GitHub.</p>
<div class="buttons">
<a class="btn" title="Publicly archived list" href="mailto:wai-eo-editors@w3.org?subject=%5bImproving%20the%20Accessibility%20of%20Your%20Website%5d">E-mail</a>
<a class="btn"
href="https://github.com/w3c/wai-planning-and-implementation/blob/gh-pages/improving.html">Fork & edit on GitHub</a>
<a class="btn" href="https://github.com/w3c/wai-planning-and-implementation/issues/new?title=[Improving%20the%20Accessibility%20of%20Your%20Website]&body=This%20is%20a%20comment%20related%20to%20the%20page%20[Improving%20the%20Accessibility%20of%20Your%20Website](//w3c.github.io/wai-planning-and-implementation/improving.html)">New GitHub Issue</a>
</div>
</aside>
</main>
<footer id="footer" role="contentinfo">
<div>
<h2>Document information</h2>
<p><strong>Status:</strong> <strong>Draft</strong> updated May 2016 (first published March 2006)<br>
Editors: <a href="/People/shadi/">Shadi Abou-Zahra</a>, <a href="/People/#kevin">Kevin White</a>, and <a href="/People/Shawn/">Shawn Lawton Henry</a>. Developed by the <a href="/WAI/EO/">Education and Outreach Working Group</a>. Previous contributors: Sharron Rush, Anna Belle Leiserson, and Judy Brewer. First developed with support from <a href="/WAI/TIES/" shape="rect"><acronym title="Web Accessibility Initiative: Training, Implementation, Education, Support">WAI-TIES</acronym> Project</a>, then updated with support of the <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> Project</a> and later the <a href="/WAI/DEV/" shape="rect"><acronym>WAI-DEV</acronym> Project</a>. This page was previously titled "Short Term Website Accessibility Improvements" and "Improving the Accessibility of Your Website".</p>
<div class="footer-nav">
<p>[<a href="/WAI/sitemap.html" shape="rect">WAI Site Map</a>] [<a href="WAI/sitehelp.html" shape="rect">Help with WAI Website</a>] [<a href="/WAI/search.php" shape="rect">Search</a>] [<a href="/WAI/contacts" shape="rect">Contacting WAI</a>]<br clear="none" />
<strong>Feedback welcome to <a href="mailto:wai-eo-editors@w3.org" shape="rect">wai-eo-editors@w3.org</a></strong> (a publicly archived list) or <a href="mailto:wai@w3.org" shape="rect">wai@w3.org</a> (a WAI staff-only list).</p>
</div>
<div class="copyright">
<p>Copyright © 2016 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>
</footer>
</body>
</html>