- From: Charles McCathieNevile <charles@w3.org>
- Date: Mon, 3 Apr 2000 07:38:12 -0400 (EDT)
- To: Bruce Bailey <bbailey@clark.net>
- cc: joelsanda@yahoo.com, w3c-wai-ig@w3.org
Actually, I think that the WCAG group will be looking at just this thorny question in producing a version 2 of the guidelines - there are some simple things like making sure there are keyboard equivalents for mouse-based things, and looking for a better, device-independent model for trigering scripts in the first place. When WCAG 1.0 was released there were a lot of users running non javascript-capable browsers - has that changed? Until we decide that we are not going to support them (and for the moment we are bound to support them, hence 6.3 as a P1) we will still require that content be usable without scripts. But we do require that scripts and applets be directly accessible themselves, so the work on how this is achieved is important in the framework of the current recommendation. cheers Charles McCN Bruce Bailey wrote: Checkpoint 6.3 cuts hard and sharp and deep. Do YOU want to try and write clear unambiguous guidelines for when JavaScript is accessible and when its not? I wouldn't go near that task with the proverbial ten foot pole! -- Charles McCathieNevile mailto:charles@w3.org phone: +61 (0) 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI Location: I-cubed, 110 Victoria Street, Carlton VIC 3053 Postal: GPO Box 2476V, Melbourne 3001, Australia
Received on Monday, 3 April 2000 07:38:14 UTC