Understanding Accessibility
by Vivienne Trulock
Users of this site also found these sites useful
Guideline 8. Ensure direct accessibility of embedded user interfaces.
Checkpoint 8.1 - Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies
How do I do it?
Scripts, applets and objects may not run on all systems, so a text alternative should be provided explaining the function of the script or how the script affect the content display, or how to otherwise achieve what the script does. Where a <script> tag is found in the <head> area of a page, a <noscript> tag should also follow in the page <body>.
<noscript>
<p>this script is a fix for css differences between netscape and internet explorer</p>
</noscript>
Applets and objects which allow movement should also provide a mechanism to stop to animation.
When using <object>, add in a text alternative, in case the object cannot be executed.
</OBJECT>
When using <applet>, add in a text alternative, in case the applet cannot be executed.
</APPLET>
How do I check that it meets the WCAG criteria?
Using the Edit > Find function in Notepad, pages should be scanned for ‘script’. Where scripts are found, the page will be again scanned for ‘noscript’. If there are scripts on the page and an equal number of noscripts cannot be found, the page will have failed.
Pages should also be scanned for ‘applet’. Where an applet is found it should have an ALT attribute, otherwise the page will have failed.
Pages will also be checked for ‘object’. Objects should have a TITLE attribute, otherwise the page will be deemed to have failed.
Applets and objects which allow movement should also provide a mechanism to stop to animation. Where this is not provided, the page will fail the check.
