Category: CSS

Interested in improving site accessibility for all site visitors? The section 508 standards were written to assure that everybody can see your site, including people with vision and cognitive disabilities. Once you’re familiar with these standards, it’s not too hard to abide them. Why wouldn’t we want to have the broadest audience possible anyway?

What are these 508 standards and why do they exist? The United States Federal government put out an edict – ok it’s a law – that states that any federal website must be created in such a way as to allow everyone to “see” it or otherwise consume the information.

The main idea was to make sure to include folks with disabilities who might use alternative means of navigating the Web and to assure that anyone and everyone has equal access to the government. Every web page created by the federal government is checked against the following standards for compliance before being published.

Here are some suggestions on how to meet the standards (a – p) of Section 508 of the Rehabilitation Act, §1194.22. Be aware that the standards have been paraphrased for the most part and that this is only one interpretation on how to meet these standards.

Section 508 standards and how to meet them

a. Provide a text equivalent for every non-text element.

Use the alt attribute for every image or embedded media to explain what the media is portraying. Complex graphics may require a link to a new page for full explanation. Images that allow for interactivity must have their functionality explained, too. Audio content needs to be captioned or have transcripts provided. Graphics used for decoration, like borders or background color gradients, can have empty alt tags.

b. Multimedia presentations need to have their captions or transcripts synchronized with the presentation.

Videos without audio tracks should have audio descriptions created. Caption synchronizing can be accomplished with any media player using MAGpie, the “original free caption- and audio-description authoring tool for making multimedia accessible to persons with sensory disabilities.” It can also be used to create caption files for YouTube videos.

c. Information that is communicated with color must also be communicated without color.

Color cannot be the only means of communicating information. People who are color blind may not see links if they’re not underlined or highlighted in some other way. Contrast must be high in order for others to see the message.

d. Webpages need to be readable on their own, as if the stylesheet was missing.

Even though most web pages would look very plain without their associated stylesheet, they should be organized so that they’re readable without the stylesheet.

e. Text links should be provided for each active region of server-side image maps.

Use client-side image maps instead of server-side image maps. Each active region should be described in alternative means.

f. Client-side image maps should be used instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

Use client-side image maps instead of server-side image maps. Each active region should be described in accessible text.

g. Data tables need to have row and column headers described.

Use <th> in data tables. Don’t use tables for layout purposes.

h. Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.

Use the scope attribute to tell the browser or screen reader that everything under a column heading is associated with that column or that everything to the right of a row header is associated with that row. Complex tables should use ids or headers. Avoid spanned rows and columns and instead present the data in more simple terms.

i. Frames should have text for identification to describe the navigation.

If you can’t avoid the use of frames, make sure they have descriptive titles.

j. Assure that images do not flicker at a frequency greater than 2 Hz and lower than 55 Hz.

Avoid using flickering images.

k. If there is no way to provide accessible or alternative content for your message, a text-only page must be provided.

Keep things simple, but if that’s not possible make available text-only pages. Keep each text-only page up-to-date.

l. When using scripts to display content or create interface elements, assure that the same information is provided via functional text that can be read by assistive technologies.

This is going to require some thought for every instance of jQuery or other javascript components on a page.

m. When a web page requires a plug-in to interpret the page content, an accessible link for downloading each plug-in must be provided.

Download links must be provided for the plug-ins required to read PDFs or to view Java applets, for example.

n. Help people using assistive technologies to fill out your online forms.

Use <label> tags with the for attribute for each element of a form. Use descriptive titles and provide instructions on how to properly fill out the form.

o. A method should be provided that allows users to skip a series of navigation links.

Use skip links to let users pass the navigation menu and go directly to the content. A skip link is a link at the top of the page that plainly states that it ‘skips navigation’ or ‘skips the link list’ and jumps the reader to an anchor at the beginning of the content.

p. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Allow the user to have control over the timing of inputs.

So, the bottom line is to keep things simple. Use text to describe things on the page and to identify things that aren’t text. Be careful with scripting actions so that information is accessible to all.

In an effort to improve the status quo I’ll be taking a look at all my web properties with an eye for improving their accessibility. Do you have any hints on how you’ve accomplished the same?