W3C logoWeb Accessibility Initiative (WAI) logo

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

Editors Draft: $Date: 2010/11/05 17:33:57 $ [changelog]
Status: This document is an in-progress draft and should not be referenced or quoted under any circumstances. Please send comments to wai-eo-editors@w3.org (a publicly archived list).

[Draft] Web Accessibility and Usability

See also: Accessibility - W3C

Page Contents

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.

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, it means that people with disabilities can perceive, understand, navigate, and interact with websites and tools, and that they can contribute equally without barriers. Accessibility is not an option, it is a human right, as recognized in the UN Convention on the Rights of Persons with Disabilities (CRPD). [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 ... "]

Some accessibility requirements 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.

Most accessibility requirements 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. Thus products designed to meet accessibility requirements are more usable for everyone.

{Much of the focus on accessibility the last ten years has been on meeting standards; however, standards are not the end goal, they are a tool to help ensure accessibility. The goal of web accessibility is to make websites, browsers, and other web tools work well for people with disabilities.}

Understanding Usability and User-Centered Design (UCD)

Usability is about designing products to be effective, efficient, and satisfying. Usability is an aspect of human-computer interaction (HCI) research and design {(it is much broader than usability testing)}. The practice of usability is largely about following a user-centered design (UCD) process to create positive user experiences.

[Note: Although "usability" is often considered an attribute for evaluation, usability compasses a broad field of human-computer interaction research and design that is much broader 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. {[ref]}

{Usability efforts often focus on primary user groups and common user characteristics; in the past, most have not included people with disabilities.}

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:]

{Including people with disabilities in usability research and practice has many benefits; for example:}

{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.]

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. Thus UCD methods are an effective way to improve accessibility in websites and web tools.

Real People

[The goal of web accessibility is to make websites, browsers, and other web tools work well for people with disabilities. Web accessibility standards are an effective tool to help meet that goal, however, meeting these standards alone is not the end goal.]

[A first step in meeting the needs of real people using the Web is knowing what those needs are; for example by understanding 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.]

{Usable web accessibility means meeting the needs of real people using the Web. A first step is knowing what those needs are by understanding essential basics of how people with disabilities use the Web.

Involving Users in Web Projects for Better, Easier Accessibility introduces:

[@@ maybe more here ]}

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:

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.

{A Solid Framework for Flexibility and Adaptability}

[@ main points: explain that WCAG 2.0 is stable, and provides for adaptability. optimizations to meet the need of specific audiences are part of accessibility & WCAG; still, need to ensure accessibility for all by meeting WCAG. not about one size fits all, technical requirements give you options to make choices.]

WCAG 2.0 provides a solid framework that allows for flexibility in how websites meet users' needs. The supporting documents include detailed sufficient and advisory techniques for meeting user requirements and for optimizing accessibility for people with disabilities.

WCAG 2.0 guidelines, success criteria, and techniques are provided in the How to Meet WCAG 2.0 customizable quick reference.

Often user interfaces are optimized for specific users. An advantage of the Web is that it is highly adaptable and allows the same content to be presented to users in different ways according to their needs and preferences. Websites can even provide different content that serves the same purpose; for example, different versions of a course to help students with different learning styles to complete the same curriculum. Websites that are optimized for particular users also need to meet web accessibility standards and be usable by a wider audience.

[@@ transition here would be nice]

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 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], researchers and [developers] might identify different kinds of issues:

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 to anyone wanting to discuss or share comments and feedback, research findings, and questions related to web accessibility. Contacting WAI via the e-mail address wai@w3.org and WAI staff directly is also welcome.] [@@ maybe add: "However, please note that WAI does not have staff resources for developer support questions and similar queries"]

{You can share comments, research findings, and questions to WAI via the e-mail address wai@w3.org. (If you don't get a reply, it might have gotten caught in spam filters; try contacting one of the WAI staff directly.)}

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

{Resources and References}

[@@ This document briefly addresses a few points of a very complex topic...]

[@@ key resources and references for text in doc - ISO maybe, other WAI docs, other chunks]