Topic awaiting preservation: Section 508 (Page 1 of 1)

I'm doing some work for a company that is developing software and html that is Section 508 and I've been wandering if any other Asylumites have any experience with this sort of work?

Well, I'm familiar with web accessability issues, but I've never actually dealt with it in a professional environment. Why do you ask?

Well I'm interested in "info-sharing" with anyone with a fair deal of Section 508 document creation experience. I'm interested in finding out what other people doing ...ie creating accessible html or accessible PDFs or both... what kind of problems have been encountered and what solutions have been found etc.

Boudga: We have a selection of links here:
http://development.gurusnetwork.com/links/177/

This is clearly going to be a Big Issue very soon.

___________________
Emps

FAQs: Emperor

Everything I do at work has to be ADA and 508 compliant.

I find it to basically mean, "Write good code," if you follow by all the paradims of separation of content from style, and you follow valid XHTML1.0 you are almost 99% of the way compliant.

It also depends upon what level of compliance you are looking for. Level 1 is pretty simple, getting down to level 3 and you will be shitting yourself with all of the different tasks you have to perform in order to make everything compliant. After a while it becomes pretty easy, as you are habituated to the rules, and it becomes second nature.

I am having trouble coming up with any specific advice to your situation, since you don't rely expand upon what you are doing.

Some simple rules I like to follow are:

1. summary attributes: make sure anything that can have a summary attribute has one, this is very important for tables.
2. alt for images: make sure your alt text is descriptive, very descriptive.
3. Make sure to have hidden attributes (or visible) to skip all sections of your page. (i.e. skip navigation, skip content) which dramactically helps those who do not use a mouse.


Me

quote:

---

I find it to basically mean, "Write good code"

---

That pretty much sums it up.

You have take into account a variety of user agents, and make sure your markup is good and clean.

I'm a little unsure what exactly you're after still as well, boudga....


Some useful links here on the issue as well - http://www.in-dented.com/links.php?cat=01&sub=028

Basically I'm looking for anyone that cares to share any experiences (good or bad) they've had with writing for Section 508 compliance....

Started an FAQ on this to track the issue:

:FAQ:

___________________
Emps

FAQs: Emperor

Every time this comes up, I mention Dive Into Accessibility. Now I have the satisfaction of putting it in the FAQ. *cheer*