Discussion Locked

Web Accessibility Question

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

As a web developer, I recently received a question from a client on how to guarantee that web pages using color can also be Section 508-compliant without using color. Naturally, my first impulse was to deal with the problem by using JavaScript tocheck if the page is IE/Netscape compatible, and if so, to redirect the user to a color-based page. If however the browser the user is viewing the site with is not IE/Netscape-compatible, the JavaScript could redirect the client to an accessible, Sect. 508-compliant page.

The problem with this solution is that I am not 100% sure the JavaScript itself would be Section 508-compliant. In other words, if a blind user is browsing the web site using Lynx or screen reader software, will the JavaScript be able to run in the first place? Or is there perhaps a better, more accessible alternative solution to the client's request that I am just not thinking of? (My second idea was to somehow try to use style sheets to solve the problem, but I am not sure how plausible that is either since how would the style sheet differentiate between when to use color and when not to?)

5 replies

by tjc

Sounds like your friend works for the goverment. A friend of mine does and what me and him came up with (this same problem) to have a main page that asks the user to choose one type or the other, that way you don't have to worry about javascript, browser type or anything. That way then the subsite under the link would be 508-compliant and the other can be what ever you want. We used the terms "high profile" and "low profile" for our links so as not to offend any one.

by jay eckles

You definitely don't want to rely on Javascript to take a user to a 508 page; all of your pages should be 508 compliant. Otherwise, you'll be maintaining two complete websites, and there's no reason one of them shouldn't be compliant.

The answer to your question is not about technical issues like what HTML tags, it's about user interface design. For example, if you're using color to communicate something in your webpage, you have to use some other means of communication as well for someone who, say, is color blind, such as text or shape. For EVERY single image on your website, you should provide MEANINGFUL alternate text unless the image is there for layout purposes only, like a transparent spacer, in which case you want NO alternate text.

A huge key to accessibility is a simple one: write valid HTML! In doing so, you guarantee that any HTML compliant browser will be able to view your website. Another key is to separate presentation from content; the most obvious way to do this is through the use of Cascading Style Sheets. With CSS, you can write a very linear page that is very easy on text-based and reader browsers, yet still provide every bit as much "flair" as a page marked up for visual effectiveness.

As to your question on how would the stylesheet know when to use color and when not to, it doesn't have to "know". The stylesheet may be turned on or off, or it may have some of its rules overridden by the user's own stylesheet. A person with poor vision might have their own stylesheet that increases text size to 40 pt. Test your page without CSS. If it communicates the message, then your good. Assume your stylesheet will be turned off when testing how well you're getting your message across.

Good luck.

Jay Eckles

This discussion is closed to new replies.