- From: Charles McCathieNevile <charles@w3.org>
- Date: Mon, 26 Apr 1999 12:18:37 -0400 (EDT)
- To: Gregg Vanderheiden <po@trace.wisc.edu>
- cc: "GL - WAI Guidelines WG (E-mail)" <w3c-wai-gl@w3.org>
I agree with this suggested resolution. Charles McCN On Mon, 26 Apr 1999, Gregg Vanderheiden wrote: ISSUE - 12: An AC Member thought that there was a topic missing in the guidelines. They felt that for applets it would also be nice to see a statement something like: "Only use technology that provides an Accessibility API to build applets from. This way assistive technologies are able to access the information contained in them." They felt that this way accessibility sensitized designers would have some guidance on what to look for in the technology the applet is to be based on and a user won't be forced to use some alternative to the applet when running in a browser that is able to display an applet. They noted that this did place a requirement on the user to have an assistive technology that is compatible with the Accessibility API but that that was something beyond the scope of these guidelines. PROPOSED RESOLUTION: This is covered in Guideline 8 which states 8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.] Using an Accessibility API can be discussed in the Techniques document as a strategy for doing this. SPECIFIC WORDING: No Change proposed to Guidelines doc itself. --Charles McCathieNevile mailto:charles@w3.org phone: +1 617 258 0992 http://www.w3.org/People/Charles W3C Web Accessibility Initiative http://www.w3.org/WAI MIT/LCS - 545 Technology sq., Cambridge MA, 02139, USA
Received on Monday, 26 April 1999 12:18:44 UTC