Hi. I was wondering if this site is accessible. I ran it through the bobby checker but I cannot tell what applies to my page and what doesn't. It is a page for our high school's technology class. I designed it to be valid html but I am new to the subject of accessibility. Your help is much appreciated!
Thanks for your suggestions! I will start working on those right away.
I have this news page (which is powered by Blogger) which seems to look fine in Lynx (I am looking at it through delorie.com). This page is xhtml as opposed to html and uses less tables. If I add a "Skip Navigation" link at the top, would this be 508 approved?
Last edited by liamk; 03-30-2005 at 05:43 PM.
Reason: additional questions (third paragraph)
508 was written a long time ago, before anybody realized that TABLEs for layout would become such a problem, and that there would be such an easy way to avoid their use. So yes, a TABLE with a "skip to content" link at the top meets the 508 requirements. But 508 is really wimpy. Shoot for Web Content Accessibility Guidelines 1.0 level A or Double A.
There is absolutely no advantage to using XHTML for web pages and quite a few disadvantages. However, there is a great advantage in using one of the strict DTDs. I strongly suggesting using HTML 4.01 Strict. XHTML 1.0 Strict or XHTML 1.1 is fine but only if you follow the HTML Compatibility Guidelines.
“The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.”
—Tim Berners-Lee, W3C Director and inventor of the World Wide Web
Thanks very much for your help! I have added a hidden "skip navigation" link and have changed a few colors so I believe the page is now 508 approved. I will begin working on a completely new site aimed towards the WCAG you mentioned. My friend Peter has been working on a table-free site powered by php or something so maybe we will switch from my site to his once he finishes it. Thanks again!
I would advise against making the "skip navigation" link hidden, as this will hide it from some screen readers. Also, anyone using just a keyboard or other alternative input device could not take advantage of it if they cannot see it.
You also do not necessarily need to use PHP instead of tables. You can just use CSS for marking up the presentation of the page and the proper HTML elements for marking up the content.