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

Page Contents

Introduction
Understanding Accessibility
Understanding Usability and UCD
Usable Accessibility
Working Together with Accessibility

Introduction

[@ main points: state that there times when differentiation is not necessary and times when it is. introduce main pooint of document (encouraging coordination).]

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 and inclusive for everyone.

Understanding Accessibility

[@ main points: introduce the scope of accessibility. explain that it has aspects specific to people with disabilities (that are usually technical), and aspects that overlap with usability.]

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) [@@and many governments and organizations].

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 desveloped 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 UCD

[@ main points: introduce the scope of usability, specifically differentiating from accessibility, e.g., whereas accessibility has technical focus, usability practice is largely about process.]

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.

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

[@ main points: explain the benefit of involving people with disabilities throughout design processes & including accessibility guidelines]

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

Involving people with disabilities early in design processes broadens your perspective in ways that can lead you to discover new ways of thinking about your product that will make it 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 product usability for people with disabilities, as well as people without disabilities.[@@ something stronger here?]

Usable Accessibility - Including Usability in Accessibility Research and Practice

[@ main points: address issues with "technical accessibility" versus usability - do UCD, including real people AND accessibility standards.]

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

[@ main points: emphasize the human factor of accessibility and that it is about real people (as opposed to ticking-off checkboxes); and that developers need to learn the basics first in order to manage accessibility effectively.]

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:

The benefits of involving users
How to involve users throughout your project
Getting a range of users
Working with users

[@@ maybe more here ]

Technical Standards

[@ main points: explain the role of technical standards for developing accessible products. explain the role of techniques to provide practical guidance for specific situations.]

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:

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.

WCAG 2.0 Framework for Flexibility and Adaptability

[@ main points: explain that WCAG 2.0 provides a solid framework along with flexibility, and for adaptability. optimizations to meet the need of specific audiences, including adaptability approaches, are part of accessibility; still, need to ensure accessibility for all. 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. WCAG support 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 should also meet web accessibility standards and be usable by a wider audience.

[@@ transition needed?]

Working Together with Accessibility

[@ main points: promote coordination of related work with existing accessibility work, in particular by inviting contribution to WAI work by researchers. mention negatives of not building on existing work. differentiate broad issues of "inclusion", from accessibility for specifically people with disabilities.]

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, [@@ another good thing], 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 @@], researchers[ and @@] 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 settings that are difficult to find in common browsers, such as settings to change the colors for text, 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 addressed in accessibility guidelines, they may be related to accessibility issues. 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.

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

[@@ note only touches on complex issue...]

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

Site Navigation