#20659
This document summarizes the features of the Cascading Style Sheets (CSS), level 2 Recommendation ([CSS2]) known to directly affect the accessibility of Web documents. Some of the accessibility features described in this document were available in CSS1 ([CSS1]) as well. This document has been written so that other documents may refer in a consistent manner to the accessibility features of CSS.
#18632
Auxiliary Benefits of Accessible Web Design
This document is one of several resources created to assist the preparation of a business case for the implementation of Web accessibility. It describes the many business, technical and other benefits to the organization above and beyond the straightforward benefits to people with disabilities that can be realized by applying the Web Content Accessibility Guidelines (WCAG 1.0) to Web sites.
Arch, Andrew and Chuck Letourneau. W3C (2002). Design>Web Design>Accessibility
#20204
Cascading Style Sheets (CSS) is a simple mechanism for adding style (e.g. fonts, colors, spacing) to Web documents. Tutorials, books, mailing lists for users, etc. can be found on the 'learning CSS' page.
#27482
To demonstrate an example of some accessibility issues in HTML Forms, the following content intentionally has accessibility errors.
Abou-Zahra, Shadi. W3C (2004). Articles>Web Design>Accessibility>Forms
#20049
Evaluating Web Sites for Accessibility
This document outlines approaches for preliminary review Web site accessibility, and for evaluation of conformance to the Web Content Accessibility Guidelines 1.0. While it does not provide checkpoint-by-checkpoint testing techniques it does include general procedures and tips for evaluation during development of Web sites, and for monitoring of established Web sites. Other resources will be developed for in-depth compliance testing. The measures described here are intended to supplement an organization's existing procedures for content management and quality assurance on their Web sites. For information about why making Web sites accessible is important read the Introductions on the WAI Resources page.
#23082
Examples: WAI Web Content Accessibility Curriculum
Provides details or examples of one or more techniques that are associated with a particular checkpoint. Where possible, the examples are actually coded so that you will see how that particular technique displays or renders on your browser or user agent. In most cases, the markup that creates the 'live' example is also provided (although you can also 'View Source' to get the exact coding). Where necessary, some text is included to explain what is 'supposed' to happen (for example, if an HTML 4 attribute is not widely supported yet), or for user of non-graphical or older browsers.
Letourneau, Chuck and Geoff Freed. W3C. Design>Web Design>Accessibility>Education
#20709
Extensible Markup Language (XML) Activity Statement
The Extensible Markup Language (XML) is a simple, very flexible text format derived from SGML (ISO 8879). Originally designed to meet the challenges of large-scale electronic publishing, XML is also playing an increasingly important role in the exchange of a wide variety of data on the Web.
#18630
Getting Started: Making a Web Site Accessible
An initial introduction to resources for people new to Web accessibility.
Brewer, Judy. W3C (2002). Design>Web Design>Accessibility
#13789
There is no limit in the Web specifications to the graphical formats that can be used on the Web. You just need a MIME type so that the format is labelled correctly for transfer across the Web, and so that a suitable viewer (if one exists) can be located at the other end. In practice, certain formats are more widely understood than others; certain formats are more suited to one type of graphical data than another; so you should make an informed choice about what format to use.
#20058
How People with Disabilities Use the Web
This document provides an introduction to use of the Web by people with disabilities. It illustrates some of their requirements when using Web sites and Web-based applications, and provides supporting information for the guidelines and technical work of the World Wide Web Consortium's (W3C) Web Accessibility Initiative (WAI).
W3C (2001). Design>Accessibility>Web Design
#28741
The Inaccessibility of CAPTCHA: Alternatives to Visual Turing Tests on the Web
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.
W3C (2005). Design>Web Design>Accessibility>Security
#20394
A free service that checks documents like HTML and XHTML for conformance to W3C Recommendations and other standards.
#18631
Overview of the Web Accessibility Initiative
An online presentation explaining why Web accessibility is important and what the Web Accessibility Initiative does.
Brewer, Judy. W3C (2003). Presentations>Slideshows>Accessibility
#18633
Quick Tips to Make Accessible Web Sites
Ten tips for making Web sites accessible, available on a business-card sized reference card. Can be ordered from Web site.
W3C (2002). Design>Web Design>Accessibility
#21000
Resource Description Framework (RDF)
The Resource Description Framework (RDF) integrates a variety of applications from library catalogs and world-wide directories to syndication and aggregation of news, software, and content to personal collections of music, photos, and events using XML as an interchange syntax. The RDF specifications provide a lightweight ontology system to support the exchange of knowledge on the Web.
W3C (2003). Resources>Information Design>Standards>XML
#28848
Development and maintenance of a good Web site implies many consecutive steps involving various actors. These actors all have their own objectives and understanding of the process, but all are supposedly commited to the same overall goal: building the best possible Web site given the set of constraints.
Dubost, Karl. W3C (2003). Design>Web Design>Planning
#19747
The User Interface Domain seeks to improve all user/computer communications on the Web. In particular, the Domain is working on formats and languages that will present information to users with more accuracy and a higher level of control.
W3C (2001). Design>User Interface
#27483
Web Accessibility Evaluation Tools: Overview
Web accessibility evaluation tools are software programs or online services that help determine if a Web site meets accessibility guidelines. While Web accessibility evaluation tools can significantly reduce the time and effort to evaluate Web sites, no tool can automatically determine the accessibility of Web sites.
Abou-Zahra, Shadi. W3C. Design>Web Design>Accessibility>Software
#25353
The World Wide Web Consortium (W3C)
The World Wide Web Consortium (W3C) is an international consortium where Member organizations, a full-time staff, and the public work together to develop Web standards.
#28348
This Recommendation defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML [XHTMLMOD]. The purpose of this document type is to serve as the basis for future extended XHTML 'family' document types, and to provide a consistent, forward-looking document type cleanly separated from the deprecated, legacy functionality of HTML 4 [HTML4] that was brought forward into the XHTML 1.0 [XHTML1] document types. This document type is essentially a reformulation of XHTML 1.0 Strict using XHTML Modules. This means that many facilities available in other XHTML Family document types (e.g., XHTML Frames) are not available in this document type. These other facilities are available through modules defined in Modularization of XHTML, and document authors are free to define document types based upon XHTML 1.1 that use these facilities (see [XHTMLMOD] for information on creating new document types).
W3C (2001). Design>Web Design>Standards>XHTML
#28347
This document is version 1.1 of XHTML Modularization, an abstract modularization of XHTML and implementations of the abstraction using XML Document Type Definitions (DTDs), and XML Schemas. This modularization provides a means for subsetting and extending XHTML, a feature needed for extending XHTML's reach onto emerging platforms. This specification is intended for use by language designers as they construct new XHTML Family Markup Languages. This specification does not define the semantics of elements and attributes, only how those elements and attributes are assembled into modules, and from those modules into markup languages. This second version of this specification includes several minor updates to provide clarifications and address errors found in the first version. It also provides an implementation using XML Schemas.
W3C (2006). Design>Web Design>Standards>XHTML
#18634
This document provides guidelines for designing Extensible Markup Language (XML) applications that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). XML, used to design applications such as XHTML, SMIL, and SVG, provides no intrinsic guarantee of the accessibility of those applications. This document explains how to include features in XML applications that promote accessibility.
W3C (2002). Design>Web Design>Accessibility>XML
#32264
Checkpoints for Web Content Accessibility Guidelines 1.0
This document is an appendix to the W3C "Web Content Accessibility Guidelines 1.0". It provides a list of all checkpoints from the Web Content Accessibility Guidelines 1.0, organized by concept, as a checklist for Web content developers.
W3C (2005). Articles>Web Design>Accessibility>Standards
#32761
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. 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.
W3C (2008). Articles>Web Design>Wireless Web>Standards
#32833
Developing a Web Accessibility Business Case for Your Organization: Overview
There are initial costs for organizations implementing Web accessibility; however, the initial costs are often offset by a full return on investment. In order to be willing to invest the initial costs, many organizations need to understand the social, technical, and financial benefits of Web accessibility and the expectations of the returns throughout the organization.
Arch, Andrew and Chuck Letourneau. W3C (2005). Articles>Web Design>Accessibility>Business Case
