W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2004

Re: Accessibility of Java Applets

From: Matt May <mcmay@w3.org>
Date: Tue, 27 Jul 2004 14:23:43 -0700
Message-ID: <4106C7DF.60807@w3.org>
To: RUST Randal <RRust@COVANSYS.com>
Cc: w3c-wai-ig@w3.org

RUST Randal wrote:
> Can Java Applets running inside of the browser comply with WCAG 1.0?

Yes, up to double-A.

WCAG 1.0 refers to "applets" in several places, including:

6.3 Ensure that pages are usable when scripts, applets, or other 
programmatic objects are turned off or not supported. If this is not 
possible, provide equivalent information on an alternative accessible 
page. [Priority 1]

6.4 For scripts and applets, ensure that event handlers are input 
device-independent. [Priority 2]

6.5 Ensure that dynamic content is accessible or provide an alternative 
presentation or page. [Priority 2]

7.1 Until user agents allow users to control flickering, avoid causing 
the screen to flicker. [Priority 1]

7.2 Until user agents allow users to control blinking, avoid causing 
content to blink (i.e., change presentation at a regular rate, such as 
turning on and off). [Priority 2]

7.3 Until user agents allow users to freeze moving content, avoid 
movement in pages. [Priority 2]

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.]

9.2 Ensure that any element that has its own interface can be operated 
in a device-independent manner. [Priority 2]

10.1 Until user agents allow users to turn off spawned windows, do not 
cause pop-ups or other windows to appear and do not change the current 
window without informing the user. [Priority 2]

The techniques document contains a section titled "Directly accessible 

Hope this helps,
Received on Tuesday, 27 July 2004 17:23:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:29 UTC