E-mail List Archives
Thread: Javascript - Compliance Issue
Number of posts in this thread: 7 (In chronological order)
From: A J
Date: Thu, Oct 28 2010 7:09AM
Subject: Javascript - Compliance Issue
No previous message | Next message →
Hello,
I'm trying to find an answer for the question: "Some
part of the website is non-functional when JavaScript is disabled. Is this
acceptable?"
I read WebAim article and few more interesting thoughts
about this topic over the web, but could not find a straight answer as yes or
no. All the discussions were more of a debate. I understand that the topic is
debatable and really it depends on how we perceive it (am I wrong?). But still,
can anyone tell, if some part of site is non-functional when JavaScript is
disabled will make a compliance issue as per WCAG 2.0? Provided, we've tried
our best not use JavaScript wherever possible.
Regards,
Aj
From: Priti
Date: Thu, Oct 28 2010 7:27AM
Subject: Re: Javascript - Compliance Issue
← Previous message | Next message →
Hello Ajay,
As per WCAG 2.0, there would be no compliance issue if some part of the
website is not functional when Javascript is disabled. However, point to
remember from compliance perspective, it is required that the Javascript
used on the website is Accessible.
Thanks & Regards,
Priti Rohra
Head Accessibility Testing
Net Systems Informatics (India) Pvt. Ltd. & BarrierBreak Technologies
Web: www.n-syst.com | www.barrierbreak.com
Blog: www.barrierbreak.com/blog
Please don't print this email unless you really need to. This will preserve
trees on our planet.
From: Langum, Michael J
Date: Thu, Oct 28 2010 7:33AM
Subject: Re: Javascript - Compliance Issue
← Previous message | Next message →
AJ,
In my opinion the most important thing is to assure that users of AT have access to all the information and functions available to everyone else.
You can say "Some part of the website is non-functional when JavaScript is disabled," IF --
1. the JavaScript does not provide information or functionality (e.g. mouseover affects), OR
2. the functionality and information are also provided without JavaScript.
Otherwise, JavaScript that exclusively provides functionality and/or information must work with AT.
-- Mike
From: Steve Green
Date: Thu, Oct 28 2010 7:54AM
Subject: Re: Javascript - Compliance Issue
← Previous message | Next message →
Our interpretation of WCAG 2.0 is that a website is compliant even if it
does not work without JavaScript. JavaScript is considered to be an
'accessibility supported technology' insofar as it meets at least one of the
criteria specified in WCAG 2.0. You just need to state that it is a
requirement in your technology baseline.
This does not seem satisfactory to me, but I guess the WCAG thinking is that
everyone can easily and cheaply (or at no cost at all) obtain a user agent
that supports JavaScript. If there are constraints such as corporate IT
policy that prevent users from doing so, that is not an accessibility issue
- in fact it's not your problem at all.
Steve Green
Managing Director
Test Partners Ltd
From: Jared Smith
Date: Thu, Oct 28 2010 8:24AM
Subject: Re: Javascript - Compliance Issue
← Previous message | Next message →
On Thu, Oct 28, 2010 at 7:51 AM, Steve Green < = EMAIL ADDRESS REMOVED = > wrote:
> Our interpretation of WCAG 2.0 is that a website is compliant even if it
> does not work without JavaScript.
This is correct. WCAG 2.0 allows you to require JavaScript so long as
the content and functionality generated with JavaScript also is
conformant with the guidelines.
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.
Jared Smith
WebAIM.org
From: Christophe Strobbe
Date: Wed, Nov 03 2010 9:00AM
Subject: Re: Javascript - Compliance Issue
← Previous message | Next message →
Hi,
A few additions (with "CS: ").
At 15:24 28/10/2010, Jared Smith wrote:
>On Thu, Oct 28, 2010 at 7:51 AM, Steve Green
>< = EMAIL ADDRESS REMOVED = > wrote:
> > Our interpretation of WCAG 2.0 is that a website is compliant even if it
> > does not work without JavaScript.
>
>This is correct. WCAG 2.0 allows you to require JavaScript so long as
>the content and functionality generated with JavaScript also is
>conformant with the guidelines.
CS: And if you content no longer conforms when JavaScript is turned
off or not supported, JavaScript must be included in the "list of Web
content technologies relied upon". (I.e. you rely on JavaScript for
WCAG conformance.)
>It is not clear, however, what WCAG 2.0 would require if the user
>comes to the site without JavaScript.
CS: If the site does not conform without JavaScript but JavaScript is
listed as "relied upon" in the conformance claim, one needs to
evaluate the site with JavaScript turned on to determine whether the
site conforms. However, if there is no conformance claim, you don't
know if the site was intended to conform 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.
CS: That would help users with browsers that don't support
JavaScript. What about users with browsers that support JavaScript?
Most users probably don't know what JavaScript is, let alone how to
turn it off. So how about providing an option that gives access to a
less interactive interface? (See Jeremy Keith's techniques in
"Bulletproof Ajax" p. 100 & p. 147.) This alternative interface would
be the one for browsers without JavaScript.
Best regards,
Christophe Strobbe
>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.
>
>Jared Smith
>WebAIM.org
--
Christophe Strobbe
K.U.Leuven - Dept. of Electrical Engineering - SCD
Research Group on Document Architectures
Kasteelpark Arenberg 10 bus 2442
B-3001 Leuven-Heverlee
BELGIUM
tel: +32 16 32 85 51
http://www.docarch.be/
Twitter: @RabelaisA11y
---
"Better products and services through end-user empowerment"
www.usem-net.eu - www.stand4all.eu
---
Please don't invite me to Facebook, Quechup or other "social
networks". You may have agreed to their "privacy policy", but I haven't.
From: Sailesh Panchang
Date: Wed, Nov 03 2010 12:06PM
Subject: Re: Javascript - Compliance Issue
← Previous message | No next message
>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