Guideline 8. Ensure direct accessibility of embedded user interfaces.
Source Article: http://www.w3.org/TR/WCAG10/#gl-own-interface
For most other web accessiblity reports, I have dealt many with standard programmatic functions. Most of it has been related to the common web page programming styles. However, scripting is increasing in popularity and does not allow all of the same access possiblities as xhtml markup. It is very important that it still be accessible to people with handicaps just as any other page would be.
This implementation is an absolute must if it the interface is the only way to access the content of the web page. If there is an alternate page available, this is only a priority 2. In other words, it really should be done but the user can still use your page without it. For more information about developing accessible applets, please refer to JAVAACCESS and IBMJAVA.
I haven't become a big fan of scripting and alternate interfaces as of yet. When I learn a little bit more about them, I will do my best to be sure that they do not destroy the usability of my pages by making them just as usable as the interface to the browser itself.
