Many of the methodologies used in the early phases of user centered design, such as card sorting and paper prototyping, are not accessible to people with disabilities. Anybody have any advice on alternative methods that can be used to include users with disabilities in these early phases of UCD?
|
|
Depends on the person. Depends on the disability. Ask them :-) For example I've done card sorts with people with visual impairments. After some conversation we ended up using bigger sheets of paper, thick pens and a large table (with the occasional verbal reminder). Worked well. I'd guess that similar "scale it up" techniques would work reasonably well for a bunch of visual/physical impairments. We also tried to use some swell paper for site maps (it's a kind of paper that you can print on then run through a sort of heating device that raises the black bits so you can detect them by touch.) That didn't really work though.. went back to just talking it through. Also did some tests where I "pretended" to be a text-to-speech browser - which was interesting.... but I don't think I'd had enough experience at the time with how they worked to make it as useful as it could have been. Would probably have been simpler to mock some XHTML and run it through that way - but I didn't come with the necessary hardware at the time. |
|||
|
|
|
"people with disabilities" is rather a very undefined user base. Usually the "standards" of disabilities minimum are dictated by govs for public sites, but those are usually also very irrelevant for actual use. Maybe we really need a definition (or standard?) of what really a "disabled" web user is. As of my experience disabled in web design translates to screen-readable. In this case usability testing is as simple as installing screen-reader and using it no-eyes. |
|||
|
|
|
First, define your personas, including, for example: blind and highly technical, blind and unfamiliar with my product, sighted but keyboard only user, visually impaired but not blind, deaf and technically-savvy, deaf and not technially-savvy, etc. Understanding those personas specifically should enable you to devise tests as needed, just like other personas (you wouldn't ask a child to tell you if your car buying website was easy to use because that data is nearly irrelevant). For example, if you want to know how a visually-impaired person would respond to the IA of your site, just create cards with extremely large font, or use an online card-sorting tool such as Optimal Sort. If you want to know how a blind person would respond, send then an email with the IA organized in header-structured outline because that is what they hear through screen-reader technology. But first, clearly identify WHY you are asking someone with a specific disability so that you are asking the right questions. |
|||
|
|
|
Well as adrianh pointed out it depends on who your user base is and what is "disablity" you are looking at. I have found that certain methods work better with certain groups:
Improving Deaf Accessibility in Remote Usability Testing I haven't worked with mute people or got the opportunity to observe any of my professors/friends work with them so I cant comment on what works and what doesn't but I would imagine that communication would be the key driving factor and the users should be provided with material which would help them communicate by using their other senses such as eyes,years and physical actions such as writing it out or even acting it out. Great Question ! These are some excellent links I found with regards to interacting with people with disabilities while working with them : |
||||
|
|
