- From: Al Gilman <asgilman@iamdigex.net>
- Date: Wed, 07 Mar 2001 08:42:13 -0500
- To: <w3c-wai-ig@w3.org>
Wow, what a great resource Mike's reply is! Just one little thing. I got lost just at the end. At 07:55 AM 2001-03-07 -0500, Mike Paciello wrote: >Kynn -- > >However, the usability processes and methodologies created to perform >quality usability testing can be employed with/for people with disabilities. >The key is accommodatation. I have found this to be the greatest challenge >for mainstream usability companies. > Can you expand just a bit on what you mean by 'accomodation' in this sentence? What is it that the mainstream of usability skills and practice doesn't quite prepare you for in doing disability access evaluations? Al >Hope this helps. > >- Mike > >> -----Original Message----- >> From: w3c-wai-ig-request@w3.org [<mailto:w3c-wai-ig-request@w3.org%5DOn>mailto:w3c-wai-ig-request@w3.org]On >> Behalf Of Kynn Bartlett >> Sent: Wednesday, March 07, 2001 5:55 AM >> To: w3c-wai-ig@w3.org >> Subject: Process/Procedure for Accessibility Testing of Software >> >> >> Hi folks -- anyone got any pointers to references/material on how >> to test specific pieces of software to see if they are >> "accessible" (for common definitions of the word)? I need to gather >> some things to show my QA/testing folks that they can understand. >> >> --Kynn >> -- >> Kynn Bartlett <kynn@reef.com> >> Technical Developer Liaison >> Reef North America >> Tel +1 949-567-7006 >> _________________________________________ >> ACCESSIBILITY IS DYNAMIC. TAKE CONTROL. >> _________________________________________ >> <http://www.reef.com/>http://www.reef.com >> >
Received on Wednesday, 7 March 2001 08:22:48 UTC