• 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

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

[Editors' Draft] Web Accessibility and Usability Working Together

Introduction

[Web accessibility and usability are closely related; their goals, approaches, and guidelines overlap significantly. It is most effective to address them together in many situations, such as when developing websites. There are a few cases when it's important to distinguish between accessibility and usability, such as when looking at discrimination against people with disabilities and when defining specific accessibility standards.]

{Web accessibility and usability are closely related and there are benefits to combining them in research and practice. In most situations there is no need to differentiate between usability and accessibility; there are only few cases when the distinction is important, such as when looking at discrimination against people with disabilities and when defining specific accessibility standards.}

The purpose of this document is to encourage increased communication and coordination between accessibility and usability research and practice in the design and development of guidelines, websites, browsers, assistive technologies, and other web tools to make them accessible, inclusive, and usable for everyone.

Understanding Accessibility

Accessibility is about ensuring an equivalent user experience for people with disabilities, including people with age-related impairments. 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. Access to information and communications technologies is a basic human right as recognized in the UN Convention on the Rights of Persons with Disabilities (CRPD) . See Accessibility - W3C for an introduction to web accessibility.

Most accessibility guidelines also improve usability for everyone, and especially benefit older users, people using different devices, and others such as people with low literacy or not fluent in the language, and people with low bandwidth connections or using older technologies. Thus accessibility includes both:

• Requirements that are more specific to 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, 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.
• Requirements that are also general usability principles, which are included in accessibility requirements 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.

Websites, web tools, and other products that meet accessibility goals are more usable for everyone.

Understanding Usability and User-Centered Design (UCD)

Usability is about designing products to be effective, efficient, and satisfying. Usability is part of the human-computer interaction (HCI) research and design field (which is much broader than usability testing). [For web developers,] a key aspect of usability is following a user-centered design (UCD) process to create positive user experiences. {Usability and human-centred design for interactive systems are covered in ISO 9241 Ergonomics of Human System Interaction, which is increasingly bringing usability and accessibility together.}

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.

Including Accessibility in Usability Research and Practice

Usability efforts often focus on primary user groups and common user characteristics; in the past, many have not included people with disabilities. [More and more usability specialists are recognizing the benefits of including people with disabilities in usability research and practice, including:]

• Involving people with disabilities early in design processes broadens designers' perspectives and can lead to making products 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 throughout the design process helps improves usability for people with and without disabilities.

Involving Users in Web Projects for Better, Easier Accessibility introduces some basics. Just Ask: Integrating Accessibility Throughout Design provides detailed guidance on incorporating accessibility in user-centered design.

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 using guidelines for design and evaluation. UCD helps make informed decisions about accessible design. Thus UCD is necessary to improve accessibility in websites and web tools.

Real People

The goal of web accessibility is to make the Web work well for people, specifically people with disabilities. [While technical standards are an essential tool for meeting that goal, marking off a checklist is not the end goal.]{While technical standards are an effective tool to help meet that goal, 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 [@@ need subject here] design solutions that are effective for users and for developers. (See also: How Involving Users Early Helps section.)

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.

The W3C Web Accessibility Initiative (WAI) develops a set of guidelines that are internationally recognized as the standard for web accessibility. These 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

[There are efforts to make the Web and other technology available to and usable by all people whatever their abilities, age, economic situation, education, geographic location, language, etc. Digital inclusion, design for all, universal usability, and similar efforts address the broad range of issues; whereas accessibility focuses specifically on people with disabilities, including people with age-related impairments. Often projects address one user group or issue; for example, developing design guidelines to optimize websites for older users, or developing standards for mobile devices. Many of the requirements of different user groups overlap with the requirements of people with disabilities.]

[another version: Making the Web and other technology available to and usable by all people whatever their abilities, age, economic situation, education, geographic location, language, etc. is the goal of "digital inclusion", "design for all", "universal usability", and similar efforts (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, for people using mobile devices, etc. 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, 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 researchers, designers, and developers, and others are developing web design guidelines, they 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 independent design issues that create accessibility barriers - For example, needing to change settings that are difficult to find in common browsers, such as text size and color settings, is an obstacle for many users, including people with disabilities. 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 and tools.
• 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 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.

• 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 research and practice.

Status: DRAFT Updated $Date: 2015/07/15 07:44:10 $ [Analysis and changelog]
Editors: Shawn Lawton Henry and Shadi Abou-Zahra. Contributors: [@@usability & other folks@@] participants of the WAI-AGE Task Force and the Education and Outreach Working Group (EOWG). Developed as part of the WAI-AGE Project (IST 035015) funded by the European Commission under the 6th Framework.

[Contacting WAI] Feedback welcome to wai-eo-editors@w3.org (a publicly archived list).