RE: Accessibility

Andre's pretty much right on. I'll add a few items...

> - Dynamic menus such as pull downs (rendered with DHTML/JS) must be
> converted to standard anchor links.

More specifically, just be sure not to use null links:
 a href="#"
 a href="javascript:;"
Instead, make sure all href's have a resolvable URL in them.

Also, note that pull-down/fly-out menus may also pose usability issues in
addition to accessibility issues

> - Don't force font sizes since many users will use a large font for
> reading.  They need to be able to change font size on the browser end.

Or, if you do force a font size, give them a way to resize it on the page
itself (see http://www.wired.com/news as an example)

> - Test everything you build with a screen reader.  You might be
> surprised by what it picks up.

Som other useful tests:

 - unplug your mouse...can you still navigate the site?
 - disable javascript and CSS in your browser...can you still navigate?
 - view the page in a PDA emulator

> - Because a version for the disabled is typically so different from
> the 
> original, changing the CSS for the two versions is often not enough.
> Use two template sets 

You can actually do quite a bit with well formed HTML and swapping out
multiple CSS files. That said, using multiple templates gives you just
another level of control that can be a real plus (so I agree with Andre).

-Darrel