From BAD to Good

Using the W3C's Before-and-After Demo
Tom Jewett, tom [at] tomjewett [dot] com


Preparing presentations

Scenario: you are preparing a brief introduction to Web accessibility that will be given to a general audience who may not be familiar with the topic. Your outline might look something like this:

[ Top of page ]

Learning about specific barriers

In this section, we will focus on four potential barriers: keyboard, images, tables, and forms. As we demonstrate the barriers, we'll also test for problems using techniques contained in the W3C's [Rough Draft] Easy Checks - A First Review of Web Accessibility.

Keyboard-only access

Image text alternatives



[ Top of page ]

Understanding the implications of barriers

It can be difficult for fully-abled developers to appreciate how multiple barriers combine to deny Web access to many potential readers. Besides the ones we've discussed above, these barriers include improperly structured pages, incorrect use of styles, and many others.

[ Top of page ]

Writing evaluation reports

In this section, we'll examine the reports for both inaccessible and accessible Home pages, and discuss how the strategies used here could be applied in practice.

[ Top of page ]

Analyzing accessible coding

The Demo committee volunteers who coded this site (I was not one of them) are very talented professional programmers, and it shows in the result. Any Web developer can improve his or her accessibility skills by looking "underneath the hood" at the actual code here.

[ Top of page ]