PUBLIC MARKS with tag WAI

I first got to know Kim Patch when we worked together on the W3C User Agent Accessibility Working Group. As a resident of the Web since it’s inception and a long term voice input / non mouse user I was always fascinated to hear what she had to say about making web content, and how a browser interprets that content, accessible.

As a free public service, the Bureau of Internet Accessibility scans web sites and provides a complete analysis of their accessibility, along with the broken links discovered, for free.

Le W3C a publié le 27 mars 2012 un « early draft » d’une méthode harmonisée d’évaluation des sites web. Bonne nouvelle, en apparence, mais on y trouve une petite phrase de rien du tout, qui pourrait bien s’avérer lourde de conséquences.

This page helps you make your presentations, talks, meetings, and training accessible to all of your potential audience, including people with disabilities and others. Inclusive presentations have many benefits.

"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.

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.