W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > August 2015

Re: Example not accessible

From: Andrew Kirkpatrick <akirkpat@adobe.com>
Date: Thu, 27 Aug 2015 15:38:06 +0000
To: "public-comments-wcag20@w3.org" <public-comments-wcag20@w3.org>
Message-ID: <2ED5B10F-1E8D-46C9-8AFF-C0A06F1C052C@adobe.com>

Thank you for commenting. You are correct in stating that this example depends on JavaScript and if scripting is disabled that the functionality is not available to those users. We agree that it is best practice to provide the same functionality if JavaScript is on or if it is off, but the point of this technique is to demonstrate a way to support Success Criteria 3.2.2 and 3.2.5 so the JavaScript fallback was not critical for this example, and in fact the technique itself would not function without scripting.

Regarding the use of JavaScript in general, authors can conform to WCAG 2.0 even if they do not provide a fallback for situations when JavaScript is disabled. For an author to rely on a specific technology it must be accessibility supported (see Conformance requirement 4 [http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-conformance-requirements-head] and ) and Understanding Accessibility Support [http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-accessibility-support-head]) but as JavaScript is in most settings regarded as accessibility supported authors can choose to rely on it.

That said, the Working Group suggests that authors make every effort to support every possible user whenever possible, and this includes users with scripting disabled.

(This issue was discussed and approved here: https://github.com/w3c/wcag/issues/111)


Michael Cooper

Andrew Kirkpatrick

Joshue O Connor
Received on Thursday, 27 August 2015 15:38:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:15:03 UTC