- From: Charles McCathieNevile <charles@w3.org>
- Date: Wed, 29 May 2002 13:57:05 -0400 (EDT)
- To: Jon Hanna <jon@spin.ie>
- cc: <w3c-wai-ig@w3.org>
This is a difficult problem. I believe it has been discussed before, because I was thinking about it at the beginning of last year or end of 2000 and talked to people about it, but can't find it in archives. The approximate ideas I had were that with some good user testing, we could work out a rough guide to the time factor increase. (This is more or less what the Nielsen Norman group worked on as a basis for their guidelines). We could then use these to provide some more solid guidance for how we asign priority... cheers Chaals On Wed, 29 May 2002, Jon Hanna wrote: By taking an ad absurdum example it's easy to show that time is an accessibility issue - would you consider a wheelchair user travelling 20 miles under his or her own steam to be an equally accessible form of transportation to a wheelchair-enabled bus? One of the problems with time (and also effort, concentration, and other requirements that can increase when one is making use of an accessibility feature), is that it is hard to measure in a way that will be valid for all users, and hard to decide on clear limits for (how slow does something have to be before it really affects accessibility?). This is unsatisfying for those of us who attempt to come up with solutions, mainly technical, to these problems. -- Charles McCathieNevile http://www.w3.org/People/Charles phone: +61 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI fax: +33 4 92 38 78 22 Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia (or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Wednesday, 29 May 2002 13:57:42 UTC