http://tc.eserver.org/dir/Articles/Web-Design/Accessibility/Standards A listing of the most recently indexed works about Articles and Web Design and Accessibility and Standards 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/Articles/Web-Design/Accessibility/Standards http://tc.eserver.org/35152.html http://tc.eserver.org/35152.html Let’s take a look at 10 ways to improve the accessibility of your XHTML website by making it standards-compliant. We’ll go the extra mile and include criteria that fall beyond the standards set by the W3C but which you should follow to make your website more accessible. Each section lists the criteria you need to meet, explains why you need to meet them and gives examples of what you should and shouldn’t do. http://tc.eserver.org/34642.html http://tc.eserver.org/34642.html It is six months since the release of WCAG 2.0 and I thought it might be interesting to see how extensively it has been adopted as a bench mark for determining web content accessibility. Over this time, I have felt that the rate of adoption has been relatively slow and the number of countries and other regulatory authorities now using WCAG 2 is lower than I expected. http://tc.eserver.org/34616.html http://tc.eserver.org/34616.html The World Wide Web Consortium recently approved new accessibility guidelines. Passed in December 2008, the new "Web Content Accessibility Guidelines 2.0" is now the official recommendation for web accessibility for the disabled. This new WCAG 2.0 document, a welcomed update, replaces the WCAG 1.0 W3C recommendation of 1999. This article is part one in a series discussing the impact of WCAG 2.0 on your website. http://tc.eserver.org/34619.html http://tc.eserver.org/34619.html The fourth principle of the Web Content Accessibility Guidelines requires new web documents to be “robust.” Robustness, future-proofing, user-agent independence, accessibility-supported: All are terms that suggest the same basic idea that your documents should follow standard, supported models for web document types. In many ways, this is the simplest and most testable requirement of the WCAG, but the details can be quite complicated. http://tc.eserver.org/33685.html http://tc.eserver.org/33685.html A simple checklist that presents the principles and techniques of WCAG 2.0 in a user-friendly, understandable format. The language has been significantly changed and simplified from the official WCAG 2.0 specification to make it more easily tested and verified for web pages. 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/32871.html http://tc.eserver.org/32871.html Kevin Leitch explains why he feels that the Web Content Accessibility Guidelines have failed in their mission to ensure that web content is accessible to all. http://tc.eserver.org/32520.html http://tc.eserver.org/32520.html This article demonstrates how to code accessible data tables in (X)HTML, enabling visually impaired users who employ assistive technologies to interpret the table data. Two views of a tabular data table are presented and discussed. http://tc.eserver.org/32508.html http://tc.eserver.org/32508.html Good markup is accessible by default. As long as you’re using HTML elements in a semantically meaningful way—which you should be doing anyway, without even thinking about accessibility—then your documents will be accessible to begin with. http://tc.eserver.org/32441.html http://tc.eserver.org/32441.html When I hold workshops for people who want to learn more about web standards and accessibility, I often notice that the attendants really have tried to improve their accessibility knowledge. But they get overwhelmed when they go to the official documentation from the W3C and try to understand it. http://tc.eserver.org/32446.html http://tc.eserver.org/32446.html Accessibility is one of the fundamentals of the Web, so how people who claim to be passionate about the Web and say that they deliver high quality can choose to ignore it is beyond me. 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/31626.html http://tc.eserver.org/31626.html This article reviews the new Web Content Accessibility Guidelines (WCAG) version 2.0 and was published in SPIN Magazine. The article summaries the new guidelines and identifies key revisions and changes made to the original WCAG version 1.0. http://tc.eserver.org/26849.html http://tc.eserver.org/26849.html In the first part of this article, we analyze a number of communication challenges and relate them to problems in conveying the November draft of the Web Content Accessibility Guidelines 2.0. Based on our analysis, the second part of our article offers a number of recommendations for improving the comprehensibility of the WCAG 2.0 for its various intended audiences. Although our discussion has the November draft as its focal point, the recommendations are more widely applicable to other complex documents with diverse audiences. In the final part, we propose a new vision for the WCAG. http://tc.eserver.org/26131.html http://tc.eserver.org/26131.html It's time to take a look at the working draft of WCAG 2.0. You'll see a fresh approach to a formidable challenge. http://tc.eserver.org/22938.html http://tc.eserver.org/22938.html Find out why self-confessed non-techie Bruce Lawson has been winning friends and influencing people with his support for web standards and web accessibility.