- From: Charles McCathieNevile <charles@w3.org>
- Date: Mon, 22 Oct 2001 09:24:40 -0400 (EDT)
- To: WAI GL <w3c-wai-gl@w3.org>
I thought this might be an interesting background for looking at techniques documents - both for WCAG 1 and the technology-specific approaches for WCAG 2 (go via the checkpoint mapping to see what it leads to). It is a piece from a draft of the ATAG techniques which details types of tool according to the kind of content they deal with. It then has suggestions for what checkpoiints would need to be tested if that content tool had a template or presupplied content. For example, it is reasonable to expect that a tool for multimedia content would have some clip-art, and so it should be checked whether there is an existing text equivalent (checkpoint 1.1). But a programming tool (e.g. a scripting environment) is less likely to have this, and instead it might have presupplied scripts, so one should test for a functionality of those when scripting is turned off (checkpoint 6.3) Anyway, the document is at http://www.w3.org/2001/10/wcag1-tooltypes - if nothing else the AU working group would be happy to have feedback on it... cheers Charles -- 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, 22 October 2001 09:24:40 UTC