Web Accessibility First Aid:
Approaches for Interim Repairs

Key Resources for Designers and Developers

• Tips for Getting Started — Practical considerations with examples for designing, writing, and developing accessible web content.
• Tutorials — Detailed information on specific topics with guidance on addressing accessibility requirements.
• How to Meet WCAG (Quick Reference) — A customizable quick reference to Web Content Accessibility Guidelines (WCAG) 2.

What is Accessibility?

If you are new to accessibility, it is often helpful to first get a basic understanding of accessibility:

• Introduction to Web Accessibility — Introduces essential concepts, rationale, and resources.
• Web Accessibility Perspectives — Short non-technical videos that introduce accessibility features and their benefits for everyone.

More Background

When you need more in-depth background:

• How People with Disabilities Use the Web — Introduces experiences and terminology in accessibility and disability.
• Accessibility Principles — Introduces accessibility requirements defined by the W3C guidelines.

Identify the Issues

If you already know your accessibility issues, you can skip this section. If you need to identify potential issues, these resources can help:

• Easy Checks – A First Review of Web Accessibility — Simple checks that can be carried out by anyone, regardless of technical skills and accessibility knowledge.
• List of Web Accessibility Evaluation Tools — Customizable list that allows you to search for different types of tools.

Detailed Review

When you want to do a comprehensive evaluation:

• Website Accessibility Conformance Evaluation Methodology (WCAG-EM) — Provides a structured approach to help evaluate websites for accessibility.
• WCAG-EM Report Tool — Free online tool to help create evaluation reports following the WCAG-EM procedure.

Consider the Scope

You may not be able to address all the issues on every part of your website at once. To determine which parts you want to improve right away, and which to address in later stages, consider prioritizing:

• Key tasks, such as registration, search, submit, or checkout processes. Include all steps involved to complete each task.
• Key content, such as frequently accessed content and content that is relevant to people with disabilities.
• Reported content, that has known barriers; for example, from user comments submitted through the website feedback form.
• In-development content, such as areas of the website that are currently being redesigned, to avoid the creation of new barriers.

Within your scope of repair, consider prioritizing what you repair first by focusing on:

• High-impact repairs
  • Appear on multiple web pages, such as navigation bars
  • Appear on frequently-used web pages, such as the home page
  • Are critical to complete processes, such as purchase forms
  • Web Content Accessibility Guidelines (WCAG) Level A issues
• Low-effort repairs
  • Require less time, cost, or skills to repair
  • Requires less testing and validation

Set your Accessibility Target Level

The generally accepted target for accessibility is the latest version of Web Content Accessibility Guidelines (WCAG) Level AA. This may already be the standard specified in your organizational policy or it may be the legal requirement for your website.

You may need to define a phased approach with different dates for different levels. For example, meet particular WCAG success criteria in the next release, and meet all Level A and Level AA success criteria in the following release.

Note that in some cases, some Level AAA success criteria may be fairly easy to meet. For example, refining appropriate link text (2.4.4, Level A) and heading structure (2.4.10, Level AAA) may be easy to address together when revising content.

Tips for Efficient Repair

• Leverage the different skills in your team — 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 Using Combined Expertise to Evaluate Web Accessibility may be helpful.
• Communicate requirements across your team — Ensure that everyone involved in repairs understands the basics of web accessibility and the specific requirements they need to address. Distribute the Important Resources to the relevant members of your team.
• Validate solutions as early as possible — 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 about involving users in web projects and evaluating with users provide more background.
• Optimize your Tools — Explore and configure accessibility settings in the authoring tools you use to create web content, such as your content management system (CMS). The resources about selecting evaluation tools and selecting authoring tools may be helpful.

Longer Term: Planning and Managing

Once you have addressed some of the most critical web accessibility issues on your web project, it is essential you plan to integrate accessibility throughout future design and development processes. The Planning and Managing Web Accessibility guide can help you develop that plan.