[Sigia-l] 508 Compliance preparedness

[Austin Govella]

On 12/8/05, signal at received.com <signal at received.com> wrote:
> If anyone has any war stories (success or failure) related to this sort
> of effort, white papers or case studies that are publicly accessible, or
> any words of wisdom as we head down this path, I would be forever
> grateful to this community!

Optimizing for speed, using friendly URLs, and revamping bad code to
web standards will go a long, long way to making your site more
accessible. And it will also be faster and easier to maintain.

Retrofitting legacy code for accessibility takes a certain amount of
resources, and the retrofit won't necessarily improve any other aspect
of the website. However, if you adopt a strategic goal of improving
the overall user experience for the site, then optimization and better
code become part of your solution for delivering a more accessible
site.

Use your effort to *only* retrofit for legacy, or use it to improve
the entire experience. I think the second option is the best use of
resrouces.


--
Austin Govella
Thinking & Making: IA, UX, and IxD
http://thinkingandmaking.com
austin.govella at gmail.com