WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Javascript - Compliance Issue

for

From: Sailesh Panchang
Date: Nov 3, 2010 12:06PM

>It is not clear, however, what WCAG 2.0 would require if the user
>comes to the site without JavaScript. In such instances, we always
>recommend that the site be built to fail gracefully. At a minimum, a
>message that indicates that they need JavaScript should be presented.
>While WCAG 2.0 does not clarify this, a site would be very difficult
>if it presented a broken or partially functional interface to those
>with JavaScript disabled (e.g., maybe a form is presented and can be
>completed, but it will not submit without JavaScript). The point,
>however, is that this would be equally inaccessible to everyone with
>JavaScript disabled, regardless of whether they have a disability. As
>such, it's not really an accessibility issue or a compliance issue,
>but more of a general usability issue.

Sailesh: If JavaScripting is "required" by the Web content, it should
be declared as a baseline or required technology in the
accessibility-claim.
Besides, WCAG 2 is quite explicit when it says:
"Technology features can only be relied upon to conform to WCAG 2.0
success criteria if they are used in a way that is "accessibility
supported".
Technology features can be used in ways that are not accessibility
supported (do not work with assistive technologies, etc.) as long as
they are not relied upon to conform to any success criterion (i.e.,
the same information or functionality is also available another way
that is supported)".
WCAG 1 required Web content to work without JS enabled and the Sec 508
standards allow accessible JS i.e. content or interactive elements
that are made accessible with "functional text". WCAG 2 requires
technology to be used in ways that are assistive technology supported.
Rightho,
Sailesh Panchang
Director Accessibility Services
www.deque.com