Re: test24 Text equivalents for APPLETs must be updated if APPLET changes

Ken Kipnes writes:
 > All,
 > 
 > Text equivalents for APPLETs must be updated if APPLET changes

Applets shouldn't be treated under guideline 1.1. They are not
"non-text content". If this isn't already on the issues list (and I
haven't conducted a search), it should be.

Any audio or image generated by an applet is non-text content, but the
applet itself isn't. One could argue that anything possessing
interactional behaviour is non-text content, but then, every form
control would count as non-text content, which is not a desirable
result. If the necessary API's are available, the user interface
provided by an applet can be highly accessible. Thus apart from the
question of what "non-text content" means, the guidelines should allow
for the circumstance in which the applet makes proper provision for
its own accessibility. I recognize this is in part a "user agent
support" issue, but this case will become increasingly the norm in the
lifetime of the guidelines.

Received on Wednesday, 9 February 2005 07:31:59 UTC