- From: Phill Jenkins <pjenkins@us.ibm.com>
- Date: Sun, 2 Mar 2003 22:23:16 -0600
- To: w3c-wai-ig@w3.org
I would also summarize by saying that WCAG 1.0 Checkpoint 8.1 (see note 1)
is more the same as 508 paragraph L, in fact I agree with Jim that 508 and
WCAG are more like exact opposites here. WCAG 1.0 is much older and focused
on removing the need for JavaScript while 508 is more forward thinking and
is focused on making JavaScript directly accessible. WCAG 8 says:
"Guideline 8. Ensure direct accessibility of embedded user interfaces."
Ensure that the user interface follows principles of accessible design:
device-independent access to functionality, keyboard operability,
self-voicing, etc.
Checkpoint:
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.]
WCAG 1.0 is a little contradictory here, if the web site meets 6.3, i.e.,
runs with JavaScript turned off, then there would be no need to meet 8.1
and make the JavaScript directly accessible. In my opinion, the need to be
able to run without JavaScript is not a pure accessibility requirement now
that assistive technologies have and can be made to directly support
JavaScript. Use of JavaScript may still be of concern to some due to
security fears and older technology that doesn't support JavaScript, but
the important thing is to get it right in WCAG 2.0 by better defining what
directly accessible JavaScript is.
Removing this difference between 508 and WCAG 1.0 is a very important part
in harmonizing the standards.
Note 1 WCAG 8.1 checkpoint http://www.w3.org/TR/WCAG10/#gl-own-interface
Note 2 WCAG 8.1 techniques
http://www.w3.org/TR/WCAG10-TECHS/#tech-directly-accessible
Regards,
Phill Jenkins,
IBM Research Division - Accessibility Center
11501 Burnet Rd, Austin TX 78758 http://www.ibm.com/able
Received on Sunday, 2 March 2003 23:23:50 UTC