- From: Charles McCathieNevile <charles@w3.org>
- Date: Mon, 5 Nov 2001 05:49:25 -0500 (EST)
- To: David Woolley <david@djwhome.demon.co.uk>
- cc: <w3c-wai-ig@w3.org>
Directly accessible means that the functions themselves are accessible, as well as there being an alternative for them. Chaals On Mon, 29 Oct 2001, David Woolley wrote: > I need to clarify what the exact meaning is for checkpoint 8.1 "Make > programmatic elements such as scripts and applets directly accessible > or compatible with assistive technologies [Priority 1 if > functionality is important and not presented elsewhere, otherwise > Priority 2.]" I think that directly accessible means that there is a route to the functions that works without scripting/applets. The "compatible" clause seems to weaken this by allowing these features if some assistive technology tools can cope (although, in my view it weakens it too far, as it prevents people from applying good security practice, e.g. the advised immediate response to Nimda was to disable scripting; also, many cannot afford the document object model aware assistive technology that tends to be needed). Note that popup menus violate the no popups requirement unless there are clear and specific warnings that they will trigger a popup. In my view, they also make the site more difficult to learn to use as they differ in behaviour from the built in browser controls. I'm thinking in terms of older people who have never been computer literate, but I think this could also apply to some younger people. -- Charles McCathieNevile http://www.w3.org/People/Charles phone: +61 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI fax: +1 617 258 5999 Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia (or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Monday, 5 November 2001 05:49:42 UTC