Web Standards [The Basics Part Four] - Accessibility

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

  • If color is used to denote information (such as click-ability), reinforce it with other methods (for instances, bolding or underlining links).
  • Avoid referring to color in text. (ex: “Click the Yellow Box”).

CSS

  • Ensure markup conveys meaning when CSS is turned off. The hierarchy of elements should remain constant.
  • Don’t worry about aesthetics with style sheets turned off, unless it renders the site unusable.
  • Navigation included, if an appropriate navigation sequence is not present, “tabindex” must be used to guide the user.

Text Size

  • Avoid using pixel-based, non-resizable text.
  • Use style switchers that allow the users to control text sizes

JavaScript

  • Provide alternatives for non-mouse users
  • Use “onkeypress=” command in conjunction with “onclick=”
  • Use “noscript” to provide for those who can’t use JavaScript
  • Avoid using Image Maps (especially server-side image maps)
  • Add Skip Navigation Button (jump to content)

Web Standards
View Larger Images on Flickr

Rockin' 2 Comments

Agree with me, rant with me or complain your little heart out ... share a comment

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

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

Leave a Reply

Join in on the fun ... just no spam fun please

 

 

 

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>

Curious about the redesign? It's more of a design satire then a reflection of personal taste: Read More