PUBLIC MARKS with tag WAI

"Techniques for WCAG 2.0" provides information to Web content developers who wish to satisfy the success criteria of Web Content Accessibility Guidelines (WCAG) 2.0 [WCAG20]. Techniques are specific authoring practices that may be used in support of the WCAG 2.0 success criteria. This document provides "General Techniques" that describe basic practices that are applicable to any technology, and technology-specific techniques that provide information applicable to specific technologies. The World Wide Web Consortium only documents techniques for non-proprietary technologies; the WCAG Working Group hopes vendors of other technologies will provide similar techniques to describe how to conform to WCAG 2.0 using those technologies. Use of the techniques provided in this document makes it easier for Web content to demonstrate conformance to WCAG 2.0 success criteria than if these techniques are not used.

On December 11th, 2008 the W3C WAI released the WCAG 2.0 This site pretends to show what they are and how to accomplish them.

Summary: Why/How ARIA?

AJAX techniques have helped Web developers create live applications within Web browsers. The AxsJAX framework helps inject accessibility features into these applications so that users of adaptive technologies such as screen readers and self-voicing browsers experience the same level of interactivity that is now taken for granted by users of Web 2.0 applications.

Although WAI ARIA is a brilliant technology which does awesome things, it has a clear downside. A lot of screenreader users don't yet use software that supports it. At the moment, WAI ARIA is a great way to progressively enhance already accessible applications to be even more usable when WAI ARIA is available. WAI ARIA is not yet an effective way to make inaccessible applications accessible.

Forms that are laid out vertically with the prompts to the left of the form control have the advantage that the user can quickly scan down the left-hand side to determine what type of information they are required to provide. This is generally the best approach, although not always practical. For example, in languages such as German (emphasis added) where some words are a lot longer than others, it can create a situation where some prompts may be a long way from their associated form control, which obviously has an impact on usability. In these circumstances, positioning the prompt above the form control may be more appropriate.

bloddy German

“Excessive distances between some labels and their input fields forced users unnecessarily to take more time to interact visually with the form.”

how form layout performs.

The Colour Contrast Check Tool allows to specify a foreground and a background colour and determine if they provide enough of a contrast "when viewed by someone having color deficits or when viewed on a black and white screen"

better color checker

The objective of this technique is to make sure that users can read text that is presented over a background. For Success Criterion 1.4.3, this technique describes the minimum contrast ratio for text that is less than 18 point (if not bold) and less than 14 point (if bold). For Success Criterion 1.4.5, this technique relaxes the 7:1 contrast ratio requirement for text that is at least 18 point (if not bold) or at least 14 point (if bold).

with the formula and advices

The Social Accessibility Project is a service whose goal is to make Web pages more accessible to people with disabilities. The service gathers users' input and uses the power of the open community while not changing any existing content.

One could argue that the Web will become more immersive, more visual, more haptic, more identity-driven through avatar technology. Is it likely? I don’t know. Is it possible? You bet.

Bug 12132: Implement ARIA to enable dynamic web appliations

Porn for the Blind is a not-for-profit organization dedicated to producing audio descriptions of sample movie clips from adult web sites. This service is provided free of charge.

People with disabilities (using desktop or laptop computers) and people without disabilities who are using mobile devices have similar interaction limitations and experience similar barriers when interacting with Web sites. There is also significant overlap between the design solutions for both. For more information, see:

I’ve already stopped using ems as a relative unit for layout and sizing and have gone back to pixels because of the zoom for IE7 that works like Opera.