This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title links to the most recent version of a document.
W3C Recommendations have been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and are endorsed by the Director as Web Standards. Learn more about the W3C Recommendation Track.
Group Notes are not standards and do not have the same level of W3C endorsement.
This document specifies Best Practices for delivering Web content to mobile devices. The principal objective is to improve the user experience of the Web when accessed from such devices.
The recommendations refer to delivered content and not to the processes by which it is created, nor to the devices or user agents to which it is delivered.
It is primarily directed at creators, maintainers and operators of Web sites. Readers of this document are expected to be familiar with the creation of Web sites, and to have a general familiarity with the technologies involved, such as Web servers and HTTP. Readers are not expected to have a background in mobile-specific technologies.
Provides HTML/XHTML authors with best practices for developing internationalized HTML supported by CSS to create pages for languages that use bidirectional text, such as Arabic, Hebrew, Persian, Thaana, Urdu, etc.
Provides HTML/XHTML authors with best practices for developing internationalized content, supported by CSS, and focusing specifically on advice about specifying the language of content.
This document supplements the Mobile Web Best Practices 1.0 by providing additional evaluatio ns of conformance to Best Practice statements and by providing additional interpret ations of these statements.
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.
Below are draft documents: other Working Drafts . Some of these may become Web Standards through the W3C Recommendation Track process. Others may be published as Group Notes or become obsolete specifications.
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.
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.
These specifications have either been superseded by others, or have been abandoned. They remain available for archival purposes, but are not intended to be used.
Provides HTML/XHTML authors with best practice for developing internationalized HTML supported by CSS, focusing specifically on advice about character sets, encodings, and other character-specific matters.