Design

This website was developed and coded using human and machine friendly, structured, semantic markup. Visually, the design is created using CSS.

Standards-based design and coding keeps content and appearance separate. Separation of content and presentation has many benefits. For example; browsing applications which do not support CSS (e.g., PDAs, screen readers) can still "read" the content, and other XML-type uses of the content are possible.

This website's layout is elastic (sizes are specified using EMs). Relative-unit design accommodates user-initiated resizing without breaking the layout.

Usability or Accessibility?

Accessibility, as the term is commonly used in web development — is a good thing. Making web content more "accessible" so those of us with disabilities can use it, benefits us all. Unfortunately, accessibility implies disability.

If accessibility means making content usable, then what does usability mean? Maybe the word "disability" is the problem. Considering we all have disabilities in some form or another. I.e., you can do something I cannot do.

Architects in the building industry approach the issue of "disability" more constructively, using the principle of Universal Design. In other words, designing physical space (or products and services) so all people can access and use it. Whether you are short or tall, young or old, or otherwise "disabled."

Accessibility is such a well-entrenched term it is probably not going away anytime soon. Don't you think "usability" is a better, more inclusive word?

This entire line of discussion is such a no-brainer … it will likely fade into wiki-history. After all, shouldn't all design be good design?