The Role Attribute defined in this specification allows the author to annotate markup languages with machine-extractable semantic information about the purpose of an element.

Guidelines for making Web content more accessible to people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these.

This document provides guidelines for designing user agents that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). User agents include HTML browsers and other types of software that retrieve and render Web content. A user agent that conforms to these guidelines will promote accessibility through its own user interface and through other internal facilities, including its ability to communicate with other technologies (especially assistive technologies). Furthermore, all users, not just users with disabilities, should find conforming user agents to be more usable.

In addition to helping developers of HTML browsers and media players, this document will also benefit developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a conforming user agent. Technologies not addressed directly by this document (e.g., technologies for braille rendering) will be essential to ensuring Web access for some users with disabilities.

This specification provides guidelines for Web authoring tool developers. Its purpose is two-fold: to assist developers in designing authoring tools that produce accessible Web content and to assist developers in creating an accessible authoring interface.

Authoring tools can enable, encourage, and assist users ("authors") in the creation of accessible Web content through prompts, alerts, checking and repair functions, help files and automated tools. It is just as important that all people be able to author content as it is for all people to have access to it. The tools used to create this information must therefore be accessible themselves. Adoption of these guidelines will contribute to the proliferation of Web content that can be read by a broader range of readers and authoring tools that can be used by a broader range of authors.

This document is part of a series of accessibility documents published by the W3C Web Accessibility Initiative (WAI).

Specific authoring practices that may be used in support of WCAG 2.0. Includes general techniques, techniques for HTML, CSS, etc., and common failures.

Guide to understanding and implementing WCAG 2.0.

The XHTML Access module defines an element that, when used in conjunction with other XHTML modules in XHTML Family Markup Languages, enables a more robust accessibility model than is presently possible.

This technical report describes the similarities and differences between the Web Content Accessibility Guidelines (WCAG) and the Mobile Web Best Practices 1.0.

Requirements used for development of WCAG 2.0.

A common method of limiting access to services made available over the Web is visual verification of a bitmapped image. This presents a major problem to users who are blind, have low vision, or have a learning disability such as dyslexia. This document examines a number of potential solutions that allow systems to test for human users while preserving access by users with disabilities.

This document provides techniques for satisfying the checkpoints defined in "User Agent Accessibility Guidelines 1.0" [UAAG10]. These techniques address key aspects of the accessibility of user interfaces, content rendering, application programming interfaces (APIs), and languages such as the Hypertext Markup Language (HTML), Cascading Style Sheets (CSS) and the Synchronized Multimedia Integration Language (SMIL).

The techniques listed in this document are not required for conformance to the Guidelines. These techniques are not necessarily the only way of satisfying the checkpoint, nor are they a definitive set of requirements for satisfying a checkpoint.

This document provides information to authoring tool developers who wish to satisfy the checkpoints of "Authoring Tool Accessibility Guidelines 1.0" [ATAG10]. It includes suggested techniques, sample strategies in deployed tools, and references to other accessibility resources (such as platform-specific software accessibility guidelines) that provide additional information on how a tool may satisfy each checkpoint.

This document is part of a series of accessibility documents published by the W3C Web Accessibility Initiative (WAI).

This document describes techniques for authoring accessible Cascading Style Sheets (CSS). Cascading Style Sheets are defined by the W3C Recommendations "CSS Level 1" [CSS1] and "CSS Level 2" [CSS2]. This document is intended to help authors of Web content who wish to claim conformance to "Web Content Accessibility Guidelines 1.0" ([WCAG10]). While the techniques in this document should help people author CSS that conforms to "Web Content Accessibility Guidelines 1.0", these techniques are neither guarantees of conformance nor the only way an author might produce conforming content.

This document is part of a series of documents about techniques for authoring accessible Web content. For information about the other documents in the series, please refer to "Techniques for Web Content Accessibility Guidelines 1.0" [WCAG10-TECHS].

Note: This document contains a number of examples that illustrate accessible solutions in CSS but also deprecated examples that illustrate what content developers should not do. The deprecated examples are highlighted and readers should approach them with caution -- they are meant for illustrative purposes only.

Techniques that apply across technologies for authors of Web content who wish to claim conformance to WCAG 1.0

This document describes techniques for authoring accessible Hypertext Markup Language (HTML) content (refer to HTML 4.01 [HTML4]). This document is intended to help authors of Web content who wish to claim conformance to "Web Content Accessibility Guidelines 1.0" ([WCAG10]). While the techniques in this document should help people author HTML that conforms to "Web Content Accessibility Guidelines 1.0", these techniques are neither guarantees of conformance nor the only way an author might produce conforming content.

This document is part of a series of documents about techniques for authoring accessible Web content. For information about the other documents in the series, please refer to "Techniques for Web Content Accessibility Guidelines 1.0" [WCAG10-TECHS].

Note: This document contains a number of examples that illustrate accessible solutions in CSS but also deprecated examples that illustrate what content developers should not do. The deprecated examples are highlighted and readers should approach them with caution -- they are meant for illustrative purposes only.

The "Authoring Tool Accessibility Guidelines 2.0" (ATAG 2.0) is part of a series of accessibility guidelines published by the W3C Web Accessibility Initiative (WAI).

This document provides explanation of the intent of UAAG 2.0 success criteria, examples of implementation of the UAAG 2.0 guidelines, best practice recommendations and additional resources for the guidelines.

This document provides guidelines for designing user agents that lower barriers to Web accessibility for people with disabilities. User agents include browsers and other types of software that retrieve and render Web content. A user agent that conforms to these guidelines will promote accessibility through its own user interface and through other internal facilities, including its ability to communicate with other technologies (especially assistive technologies). Furthermore, all users, not just users with disabilities, should find conforming user agents to be more usable.

In addition to helping developers of browsers and media players, this document will also benefit developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a conforming user agent. Technologies not addressed directly by this document (e.g., technologies for braille rendering) will be essential to ensuring Web access for some users with disabilities.

The "User Agent Accessibility Guidelines 2.0" (UAAG 2.0) is part of a series of accessibility guidelines published by the W3C Web Accessibility Initiative (WAI).

This document specifies Best Practices for delivering accessible rich internet applications using WAI-ARIA [ARIA]. The principle objective is to produce a usable, accessible experience over the Web. It provides recommended approaches to create accessible Web content using WAI-ARIA roles, states, and properties to make widgets, navigation, and behaviors accessible. The document also describes considerations that might not be evident to most implementers from the WAI-ARIA specification alone. This document is directed primarily to Web application developers, but the guidance is also useful to user agent and assistive technology developers. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

This document is a practical guide for developers on how to add accessibility information to HTML elements using ARIA, a markup mechanism for making Web content and Web applications more accessible to people with disabilities.

An abstraction between device-specific user interaction events and inferred user intent such as scroll, activate, etc. This provides an intermediate layer between device- and modality-specific user interaction events, and the basic user interface functionality used by Web applications.

Describes how the Web Content Accessibility Guidelines (WCAG) 2.0 and its principles, guidelines, success criteria and conformance model can be applied to non-Web Information and Communications Technologies (ICT), including non-web documents and software.

Implementing ATAG 2.0 is an essential guide to understanding and using "Authoring Tool Accessibility Guidelines 2.0" [ATAG20]. Although the normative definitions and requirements for ATAG 2.0 can all be found in the ATAG 2.0 document itself, the concepts and provisions may be new to some people. Implementing ATAG 2.0 provides a non-normative extended commentary on each guideline and each success criterion to help readers better understand the intent and how the guidelines and success criteria work together. It also provides examples that the Working Group has identified for each success criterion.

Accessibility metrics can extend the existing WCAG 2.0 conformance model to provide scores for the accessibility level of websites in more depth and detail. This Report provides considerations for validity, reliability, sensitivity, adequacy, and complexity as the main qualities of measuring web accessibility. The Report is a consolidated view of the outcomes of the Website Accessibility Metrics Online Symposium.

Describes how user agents should support keyboard navigation, respond to roles, states, and properties provided in Web content via WAI-ARIA, and expose this to accessibility APIs.

Aggregates requirements of a user with disabilities with respect to audio and video on the Web, providing background on user needs, alternative content technologies, and their application on the Web.

The identification of resources on the Web by URI alone may not be sufficient, as other factors such as HTTP content negotiation might come into play. This issue is particularly significant for quality assurance testing, conformance claims, and reporting languages like the W3C Evaluation And Report Language (EARL). This document provides a representation of the HTTP vocabulary in RDF, to allow quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. The RDF terms defined by this document represent the core HTTP specification defined by RFC 2616, as well as additional HTTP headers registered by IANA. These terms can also be used to record HTTPS exchanges.

This document is a specification for a vocabulary to represent Content in RDF. This vocabulary is intended to provide a flexible framework within different usage scenarios to semantically represent any type of content, be it on the Web or in local storage media. For example, it can be used by Web accessibility evaluation tools to record a representation of the assessed Web content in an Evaluation And Report Language (EARL) 1.0 Schema evaluation report. The document contains introductory information on its usage and some examples.

Add content here.

This document is an introductory guide to the Evaluation and Report Language (EARL) 1.0. EARL is a vocabulary, the terms of which are defined across a set of specifications and technical notes, that is used to describe test results. The primary motivation for developing this vocabulary is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor-neutral and platform-independent format.

The WAI-ARIA Primer introduces developers to the use of WAI-ARIA [ARIA] for addressing the accessibility of dynamic Web content for people with disabilities. This primer explains the accessibility problems posed by hybrid technologies such as DHTML and Ajax. It introduces the technologies to map controls, Ajax live regions, and events to accessibility APIs, including custom controls used for Rich Internet Applications. The primer also describes new navigation techniques to mark common Web elements such as menus, primary content, secondary content, banner information and other types of Web structures. These new technologies can be used to improve the accessibility and usability of Web resources by people with disabilities, without extensive modification to existing libraries of Web resources. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

This document provides a review and analysis of guidelines and articles relating to the needs of older people with Web accessibility needs due to ageing, and compares these with the needs of people with disabilities as already addressed in WAI guidelines. The focus is particularly on Europe but applies internationally as well. This review is being undertaken in order to inform the development of educational materials which can better promote the needs of people who have accessibility needs due to ageing, and potential development of profiles and/or extensions on WAI guidelines.

The Roadmap for Accessible Rich Internet Applications addresses the accessibility of dynamic Web content for people with disabilities. The roadmap introduces the technologies to map controls, Ajax live regions, and events to accessibility APIs, including custom controls used for Rich Internet Applications. The roadmap also describes new navigation techniques to mark common Web structures as menus, primary content, secondary content, banner information and other types of Web structures. These new technologies can be used to improve the accessibility and usability of Web resources by people with disabilities, without extensive modification to existing libraries of Web resources. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

This First Public Working Draft outlines the requirements that the User Agent Accessibility Guidelines Working Group (UAWG) has set for development of User Agent Accessibility Guidelines 2.0 (UAAG 2.0). These requirements are based on feedback from the use of UAAG 1.0 and will be used to determine if the UAWG has met its goals as UAAG 2.0 advances through the W3C Recommendation Track Process.

Requirements intended to be used for development of WCAG 2.0 Techniques, superceded by later plans.

This is a W3C Working Draft produced by the Web Content Accessibility Guidelines Working Group (WCAG WG). It describes requirements for Checklists and Techniques described by the Web Content Accessibility Guidelines 2.0 (WCAG 2.0). These requirements are related to but different from Requirements for WCAG 2.0 in that "Requirements for WCAG 2.0 Checklists and Techniques" specifies requirements for the technology-specific documents produced by the WCAG WG while "Requirements for WCAG 2.0" specifies general requirements for the general usability of documents produced by the WCAG WG. The Working Group encourages feedback about these requirements as well as participation in the development of WCAG 2.0 by people who have experience creating Web content that conforms to Web Content Accessibility Guidelines 1.0.