W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2012

Re: is javascript considered good wacg 2.0 practice?

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Thu, 13 Dec 2012 09:37:35 +0000
Message-ID: <CA+ri+VnMVNjxwsxuiNMVODt=ZFnq9ZroGXvw8Z6aiuwEFixCQw@mail.gmail.com>
To: David Woolley <forums@david-woolley.me.uk>
Cc: Steve Green <steve.green@testpartners.co.uk>, Karen Lewellen <klewellen@shellworld.net>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Hi David,

Whether a user has JavaScript enabled or not is not an accessibility
A site that relies on Javascript for functionality is equally problematic
for all users who do not have Javascript enabled.

Whether the Javascript that is used is coded to provide the correct
information and interaction behaviours  is an accessibility concern.


On 13 December 2012 07:52, David Woolley <forums@david-woolley.me.uk> wrote:

> Steve Green wrote:
>  3. If Bell declare JavaScript to be part of their technology
> + baseline, then the website does not need to work without JavaScript
> + enabled.  However, all the JavaScript features must be implemented
> + in an accessible manner.
>>  There is no indication that this is a closed system.  Being able to
> declare a technology baseline sounds like a good way to avoid the nuisance
> of WCAG, if it applies to the general internet.
> Note that there is an increasing community of users of ARM based systems
> using the netsurf browser which has no scripting capability at all. That's
> as well as those who have to block it for security policy reasons.
Received on Thursday, 13 December 2012 09:38:45 UTC

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