http://tc.eserver.org/publisher/W3C A listing of works published by W3C in the field of technical communication. en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/W3C http://tc.eserver.org/35184.html http://tc.eserver.org/35184.html HTML 5 defines the fifth major revision of the core language of the World Wide Web, HTML. "HTML 5 differences from HTML 4" describes the differences between HTML 4 and HTML 5 and provides some of the rationale for the changes. http://tc.eserver.org/34737.html http://tc.eserver.org/34737.html When authoring document is HTML or XHTML, it is important to Add a Doctype declaration. The declaration must be exact (both in spelling and in case) to have the desired effect, which makes it sometimes difficult. To ease the work, below is a list of recommended declarations that you can use in your Web documents. http://tc.eserver.org/34007.html http://tc.eserver.org/34007.html One of the great things about XHTML is that it combines the well-known power of HTML as an hypertext markup language with the power of the tools developed to work on XML documents. Among those tools, one of the most ubiquitous technology developed for XML is the Extensible Style sheet Language (XSL), and especially its Transformation language that allows to transform a given XML document in another XML document with a set of declarative rules. This document lists a set of style sheets that takes advantage of XHTML being an XML language to make your XHTML documents more re-usable. http://tc.eserver.org/33471.html http://tc.eserver.org/33471.html Web Content Accessibility Guidelines (WCAG) 2.0 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of 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. Following these guidelines will also often make your Web content more usable to users in general. http://tc.eserver.org/33472.html http://tc.eserver.org/33472.html Let's work together as a community to make WCAG 2.0 a unifying force for web accessibility. There are so many websites and exciting new web applications being created today with accessibility barriers that make it difficult or impossible for some people with disabilities to use them. Let's change that, with WCAG 2.0. http://tc.eserver.org/32886.html http://tc.eserver.org/32886.html A customizable quick reference to Web Content Accessibility Guidelines 2.0 requirements (success criteria) and techniques. http://tc.eserver.org/32962.html http://tc.eserver.org/32962.html This document introduces the concept of harmonization and causes of fragmentation in the area of Web accessibility standards, and examines the impact of harmonization and fragmentation on Web developers, tool developers, and organizations. It also suggests action steps for promoting Web accessibility standards harmonization. http://tc.eserver.org/32833.html http://tc.eserver.org/32833.html 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. http://tc.eserver.org/32834.html http://tc.eserver.org/32834.html Web accessibility means that people with disabilities can use the Web. More specifically, Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web. Web accessibility also benefits others, including older people with changing abilities due to aging. http://tc.eserver.org/32852.html http://tc.eserver.org/32852.html This document shows how Web accessibility depends on several components working together and how improvements in specific components could substantially improve Web accessibility. It also shows how the WAI guidelines address these components. http://tc.eserver.org/32761.html http://tc.eserver.org/32761.html 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. http://tc.eserver.org/32264.html http://tc.eserver.org/32264.html 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. http://tc.eserver.org/28848.html http://tc.eserver.org/28848.html 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. http://tc.eserver.org/28741.html http://tc.eserver.org/28741.html 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. http://tc.eserver.org/28348.html http://tc.eserver.org/28348.html 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). http://tc.eserver.org/28347.html http://tc.eserver.org/28347.html 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. http://tc.eserver.org/27482.html http://tc.eserver.org/27482.html To demonstrate an example of some accessibility issues in HTML Forms, the following content intentionally has accessibility errors. http://tc.eserver.org/27483.html http://tc.eserver.org/27483.html 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. http://tc.eserver.org/25353.html http://tc.eserver.org/25353.html 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. http://tc.eserver.org/24175.html http://tc.eserver.org/24175.html W3 Compliant Sites is a collection of web sites that were created by designers that conform with the W3C standards. It provides the opportunity for them to display their work and ideas in a community that shares common interests. http://tc.eserver.org/23082.html http://tc.eserver.org/23082.html 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. http://tc.eserver.org/21000.html http://tc.eserver.org/21000.html 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. http://tc.eserver.org/20709.html http://tc.eserver.org/20709.html 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. http://tc.eserver.org/20659.html http://tc.eserver.org/20659.html 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. http://tc.eserver.org/20394.html http://tc.eserver.org/20394.html A free service that checks documents like HTML and XHTML for conformance to W3C Recommendations and other standards. http://tc.eserver.org/20204.html http://tc.eserver.org/20204.html 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. http://tc.eserver.org/20058.html http://tc.eserver.org/20058.html 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). http://tc.eserver.org/20049.html http://tc.eserver.org/20049.html 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. http://tc.eserver.org/19747.html http://tc.eserver.org/19747.html 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. http://tc.eserver.org/18632.html http://tc.eserver.org/18632.html 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. http://tc.eserver.org/18630.html http://tc.eserver.org/18630.html An initial introduction to resources for people new to Web accessibility. http://tc.eserver.org/18631.html http://tc.eserver.org/18631.html An online presentation explaining why Web accessibility is important and what the Web Accessibility Initiative does. http://tc.eserver.org/18633.html http://tc.eserver.org/18633.html Ten tips for making Web sites accessible, available on a business-card sized reference card. Can be ordered from Web site. http://tc.eserver.org/18634.html http://tc.eserver.org/18634.html 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. http://tc.eserver.org/13789.html http://tc.eserver.org/13789.html 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.