Question 8: Are embedded user interfaces compatible with assistive technologies?

What does this mean?

Java applets, media players (e.g., Windows Media Player, RealVideo, QuickTime), Flash animations, and Shockwave scripts require user interaction separate from the HTML-coded Web pages. These interfaces need to follow accessible design principles, such as device-independent access to functionality, keyboard operability, self-voicing, etc. Failing this, an accessible alternative should be included in the HTML pages describing the function of the elements and providing an equivalent function.

Why does this present a problem?

Some assistive technology cannot interpret scripted or programmed Web content, making the content inaccessible or unusable to some users.

What are the solutions?

1. Create directly accessible interfaces

If functionality
is important,
otherwise

Priority 2

Make these features directly accessible by following accessible principles or by providing an equivalent alternative.

TIP For further information about accessible interfaces, see W3C's User Agent Accessibility Guidelines (http://www.w3.org/TR/UAAG10/) and Authoring Tool Accessibility Guidelines (http://www.w3.org/TR/ATAG10/).

TIP WebAIM compares the accessibility of embedded and standalone versions of three media players in "To Embed or Not To Embed - A Comparison of Media Player Technologies" (http://www.Webaim.org/Articles/embeddedmp.php).

TIP Resources to assist you in making applets accessible:

Java Accessibility (http://trace.wisc.edu/world/java/java.htm) -- Trace R&D Center IBM Guidelines for Writing
IBM Guidelines for Writing Accessible Applications Using 100% Pure Java (http://www-3.ibm.com/able/snsjavag.html) -- IBM Accessibility Center
Active Accessibility, Microsoft (http://www.msdn.microsoft.com/library/ default.asp?url=/nhp/Default.asp?contentid=28000544)

What is the bottom line?

The bottom line, as stated in WCAG Guideline 8, is give the user access to embedded user interfaces.