The objective of accessibility is to ensure that our interactive properties will be usable and available to the largest possible number of readers, visitors, and customers. Section 508 requires that many sites accommodate people with disabilities ranging from limited mobility to a vast range of visual impairments. By conforming to basic accessibility guidelines we not only open our sites to those users with disabilities but also further enhance our sites for those users accessing our sites away from their customary environment; environments such as kiosks, palm pilots and limited browsers in airports and other public places. By conforming to the web standards demanded earlier in this document, most general accessibility issues will be addressed (ex: image alt tags).
Basic accessibility guidelines to follow:
Color
CSS
Text Size
JavaScript
Curious about the redesign? It's more of a design satire then a reflection of personal taste: Read More
Dont forget a descriptive title and h* element. And never use tables for layout, semantics is really important in accessibility.
Descriptive links is also important, most writers call their links “Read on/more”, but if you list all the links on the page(Opera can do this) you will only see a bunch of “Read on” links without having a clue to where they link. The title attribute is important.
I guess you already coverd most of accessibility in the third part.
Agree with you on all parts! Thanks for the feedback.
This was just a simple tutorial for those who know of “web standards”, but have no real design/development background — the business/project managers of the world. I’ve had too many ignorant co-workers/clients try and manage projects that require webstandards — it’s a painful sight.