• Skip to content
• | To change text size or colors

WAI: Strategies, guidelines, and resources to make the Web accessible to people with disabilities

Site Navigation

W3C Home

Web Accessibility Initiative (WAI) Home

1. Introducing Accessibility
   1. Introduction to Accessibility
   2. Essential Components
   3. How People with Disabilities Use the Web
   4. »Web Accessibility and Usability
   5. Web and Older Users
   6. Contact Inaccessible Websites
   7. Handouts
2. Guidelines & Techniques
3. Managing Accessibility
4. Evaluating Accessibility
5. WAI Groups
6. About WAI

This is an outdated draft and should not be referenced or quoted.
The latest version is at: www.w3.org/WAI/intro/usable

[Draft] Web Accessibility and Usability: Coordinating Guidelines, Research, and Practice

title ideas:

• Web Accessibility and Usability: Coordinating Guidelines, Research, and Practice
• Web Accessibility, Usability, and Digital Inclusion: Coordinating Guidelines, Research, and Practice
• Coordinating Web Accessibility and Usability Guidelines, Research, and Practice
• Coordinating Web Guidelines, Research, and Practice with Accessibility
• Coordinating Web Usability Guidelines, Research, and Practice with Accessibility
• old ones

See also: Accessibility - W3C

Introduction

There is significant overlap between usability and accessibility guidelines, and not a clear distinction between them. In most situations there is no need to differentiate between usability and accessibility, because their goals are complimentary. There are a few cases when the distinction is important, such as when looking at discrimination against people with disabilities and when defining specific accessibility standards.[1]

This document encourages increased communication and coordination between accessibility and usability research and practice in the design and development of standards, guidelines, websites, browsers, assistive technologies, and other web tools to make them accessible to people with disabilities, inclusive, and usable for everyone.

Understanding Accessibility

Accessibility is about ensuring an equivalent user experience for people with disabilities. For the Web, accessibility means that people with disabilities can perceive, understand, navigate, and interact with websites and tools, and that they can contribute equally without barriers.[2] Whereas usability is optional, accessibility is not an option — it is a human right, as recognized in the UN Convention on the Rights of Persons with Disabilities. It is also the policy of many governments and organizations around the world.} {@@another sentence idea: "While accessibility benefits everyone, for people with disabilities it is not an option. Accessibility is a human right ... "[3]

@@ really do need to focus on pwds - related to inclusive design and have benefits, but it is its own thing! to address discriminatory -- main motivation @@ Some accessibility requirements [@@]related to the needs to @@ primarily benefitare specific to[ug] people with disabilities. For example, they ensure that websites work well with assistive technologies such as screen readers that read aloud web pages, screen magnifiers that enlarge web pages,[<-what?->] and voice recognition software that is used to input text. Most of these requirements are technical and relate to the underlying code rather than to the visual appearance.

[Meeting accessibility requirements also] Most accessibility requirements [@@ requirements dont improve] improve usability for everyone, and especially benefit older users, people using different devices, people with low literacy or not fluent in the language, people with low bandwidth connections or using older technologies, and others. While these accessibility requirements are also general usability principles, they are included in accessibility standards because they can be significant barriers to people with disabilities. For example, a website that is developed so that it can be used without a mouse is good usability; and use without a mouse is an accessibility requirement because people with some physical and visual disabilities cannot use a mouse at all. Products designed to meet accessibility requirements are more usable for everyone.

Understanding Usability and User-Centered Design (UCD)

Usability is about designing products to be effective, efficient, and satisfying.[4] Usability is part of the human-computer interaction (HCI) research and design field (which is much broader than usability testing). A key aspect of usability is following a user-centered design (UCD) process to create positive user experiences.[5]

Note: Although "usability" is often considered an attribute for evaluation, in fact usability compasses a broad field of human-computer interaction research and design that is much larger than usability testing.

User-centered design (UCD) focuses on usability goals, user characteristics, environment, tasks, and workflow in designing a user interface to meet user requirements. For example, UCD considers users' hardware, software, computer experience, task knowledge, and other characteristics in designing a website, web application, browser, and other web tool. UCD is an iterative process with well-defined methods and techniques for analysis, design, and evaluation from the first stage of projects through implementation.[1]

Including Accessibility in Usability Research and Practice

Usability efforts often focus on primary user groups and common user characteristics; in the past, most have not included people with disabilities. However, including people with disabilities in usability research and practice has many benefits; for example: WAI encourages usability research and practice to fully incorporate people with disabilities. @@The many benefits include:

• Involving people with disabilities early in design processes broadens designers' perspectives and can lead to discovering new ways of thinking about making products that work better for more people in more situations.
• Involving participants with disabilities in evaluation can identify usability issues more easily because people with disabilities are often more sensitive to usability problems. For example, a large number of links poorly organized on a web page will be more of a problem for people with some types of cognitive, physical, or visual disabilities.
• Including accessibility guidelines along with usability guidelines helps improves usability for people with and without disabilities.

{Including accessibility guidelines along with usability guidelines helps improves product usability for people with disabilities, as well as people without disabilities.[@@ something stronger here?]}

[Including accessibility guidelines along with usability guidelines helps to improve product usability for everyone, including for people with disabilities.]

There @@ resources onlein

Usable Accessibility - Including Usability in Accessibility Research and Practice

Usable accessibility combines usability and accessibility to develop positive user experiences for people with disabilities. User-centered design processes (UCD) include both techniques for including users throughout design and evaluation, and use of guidelines to inform and evaluate designs. For example, UCD helps make informed decisions when designing accessibility features[@@ developing accessibility solutions][@@could move to next section]. Thus UCD methods are an effective way to improve accessibility in websites and web tools.[1]

Real People

The goal of web accessibility is to make the Web work well for people, specifically people with disabilities. While web accessibility standards are an effective tool to help meet that goal, however meeting standards itself is not the end goal. People with disabilities effectively interacting with and contributing to the Web is the end goal.

To make the Web work well for people with disabilities, designers and developers need to understand the basics of how people with disabilities use the Web. Following UCD to involve people with disabilities throughout design processes and involve users in web accessibility evaluation helps [subject] design solutions that are effective for users and for developers. (See also: How Involving Users Early Helps section.)

A first step in meeting the needs of real people using the Web is knowing what those needs are; for example by understanding the essential basics of how people with disabilities use the Web.

[Also involving people with disabilities throughout design processes and involving users in web accessibility evaluation helps understand real issues and solutions for people with disabilities.]

[Understanding those basics helps design web accessibility features and solutions that are most effective for users and for developers, and to avoid spending time and effort on less effective designs.]

Technical Standards

While including users with disabilities is key to making accessibility efforts more effective and more efficient, that alone cannot address all issues. Even large projects cannot cover the diversity of disabilities, adaptive strategies, and assistive technologies. That is the role of accessibility standards.[1]

The W3C Web Accessibility Initiative (WAI) develops a set of guidelines that are internationally recognized as the standard for web accessibility:

• Web Content Accessibility Guidelines (WCAG) addresses websites, including text, images, forms, and multimedia, as well as markup code, scripts, and applications.
• User Agent Accessibility Guidelines (UAAG) addresses web browsers and media players, and relates to assistive technologies.
• Authoring Tool Accessibility Guidelines (ATAG) addresses software or services that people use to produce web content, including code editors, content management systems, blogs, and other tools.

The WAI guidelines include considerations for people with auditory, cognitive, neurological, physical, speech, and visual disabilities, including people with age-related impairments.

The WAI guidelines are stable technical standards for meeting user requirements that apply broadly across technologies and situations. Along with the guidelines are techniques and other supporting resources that provide details on how to meet the guidelines (and thus the user requirements) in specific situations.

Working Together with Accessibility

Web universality, digital inclusion, design for all, universal usability, and other such efforts focus on making the Web and other technology available to and usable by all people whatever their abilities, age, economic situation, education, geographic location, language, etc. (Whereas accessibility focuses specifically on people with disabilities, including people with age-related impairments.) Often projects focus on one specific user group; for example, developing design guidelines to optimize websites for older users. Many of the requirements of different user groups overlap with the requirements of people with disabilities.

Coordinating related efforts with existing accessibility work supports international harmonization [and interoperability], [a universally inclusive Web for everyone], and can expand research and resources in both areas. However, when efforts are not coordinated, it leads to duplication of effort and confusing or even conflicting results. For example, an extensive literature review on web accessibility for older users showed that most research and development of web design recommendations for older users did not consider WAI guidelines at all, even though the WAI guidelines directly address the accessibility needs of older web users.

When developing web design guidelines and recommendations,[@@grammar] researchers, designers, and developers might identify different kinds of issues:

• Issues that affect people with disabilities disproportionately - These are considered accessibility barriers and need to be addressed by the WAI guidelines. For example, clear navigation mechanisms help everyone yet unclear navigation mechanisms can be particularly confusing for people with visual and cognitive disabilities. WAI welcomes comments on existing standards. New findings can be addressed through the techniques or other supporting documents, included in errata, and/or incorporated in future developments of standards.
• Particular combinations of issues that create accessibility barriers - For example, relying on needing to change settings that are difficult to find in common browsers, such as settings to change the colors for text size and color settings, is an obstacle for some users. In this case, the browser could be improved to help users customize the settings and the website could be improved to help educate users on how to customize their browsers. WAI welcomes the contribution of additional techniques, including techniques that help address accessibility issues in specific design situations.
• Issues that are not specifically related to people with disabilities - For example, lack of computer skills is a common issue for some older users, people with lower income, people in less developed areas, and others. Even though such issues are not considered accessibility barriers specifically for people with disabilities and thus are not directly covered addressed in accessibility guidelines, they may be related to accessibility issues that are covered. Therefore, design guidelines for such issues should build on existing accessibility guidelines, to take advantage of existing work and ensure harmonization.

Coordinating with WAI

W3C Web Accessibility Initiative (WAI) provides an international forum for collaboration between industry, disability organizations, accessibility researchers, government, and others interested in Web accessibility. WAI encourages those involved in usability, digital inclusion, and others to share perspectives and participate in WAI work. For example, to contribute to WCAG, see instructions for commenting on WCAG 2.0 documents and the form for submitting WCAG 2.0 techniques.

• The WAI Interest Group (IG) is open for anyone to read or share feedback, comments, research findings, and questions related to web accessibility.
• The e-mail address for all WAI staff is wai@w3.org.
• To contribute to WCAG, see instructions for commenting on WCAG 2.0 documents and the form for submitting WCAG 2.0 techniques.
• Participating in WAI describes opportunities ranging from volunteering to implement, promote, and review guidelines, to occasional participation in an interest group, to dedicated participation in a working group.

WAI looks forward to increased collaboration among usability, digital inclusion, and accessibility efforts research and practice.