Understanding Accessibility

Guideline 6. Ensure that pages featuring new technologies transform gracefully.

Checkpoint 6.5 - Ensure that dynamic content is accessible or provide an alternative presentation or page

How do I do it?

It's just as easy to make dynamic content accessible as any static page. The same principles apply. Use CSS for layout and design and code the HTML correctly. Even ASP and JSP pages only return HTML and CSS to the user - the scripts are executed on the server.

If you cannot make a dynamic page element accessible, you must create an alternative page which is updated as often as the original.

You can create a set of text-only pages which will load automatically using a <link> to stylesheet tag

html

<HEAD>
<TITLE>Welcome to ilikecake text-only</TITLE>
<LINK title="Text-only version"
rel="alternate"
href="text_only"
media="aural, braille, tty">
</HEAD>

Xhtml

<HEAD>
<TITLE>Welcome to ilikecake text-only</TITLE>
<LINK title="Text-only version"
rel="alternate"
href="text_only"
media="aural, braille, tty" />
</HEAD>

How do I check that it meets the WCAG criteria?

You may be able to run your page through webXact's accessibility checker to validate this checkpoint automatically, however no page that I have ever checked has triggered this checkpoint, so I am unsure whether webXact will automatically check it or not.

guideline 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 - 14