Besides being a great designer, Seth Nickel is a really good writer. Maybe that’s what it takes if you want to pass on your vision and ideas to stubborn developers. He wrote one paragraph yesterday that resonated with me:
…we’ve been framing the hacker<->designer conversation around low level usability. Maybe we could get more done if the default conversation was different? If it happened earlier? If it was about deep design rather than surface bodangles?
This is exactly how I feel about the designer<->accessibility-advocate conversation. Accessibility is too often an afterthought that is divorced from the design process.
In the past I did some contract work as an “accessibility engineer” on a certain project. It went something like this (at the risk of encouraging an annoying meme):
NO
projectmanager: It is soooo important for us that this application be really really accessible, and support ATK really really well. And that people with disabilities have really really good access to this. Also, if you could make sure your ATK support is good enough for automated testing, that would be greeaaaat.
accessibilityperson: I would love to help. I noticed that the color theme is hard-coded, this is problematic since users with visual impairments have different needs regarding color and contrast.
artsyfartspants: The color scheme is deliberate and has been very carefully thought out. And besides, it is white on black, which is technically high-contrast, so anybody could read it.
accessibilityperson: I also noticed that animations in this application are hard-coded and cannot be disabled. This is an issue since people may be very sensitive to animations and get motion sickness. The application should respect a system-wide animation-disable toggle.
artsyfartspants: Please see my answer above. The animation’s effect and timing have been very carefully thought out. This is old news, I wrote the design spec 6 months ago, you are wasting my time.
accessibilityperson: The user notification is transient, and disappears after a few, hard-coded, seconds. Users with cognitive disabilities, slow readers or users who are not native speakers of the interface’s language will have a hard time understanding the notification before it disappears.
artsyfartspants: By design, see above.
accessibilityperson: The user notification appears, hard-coded, in the upper right corner of the screen. Users with bad peripheral vision will miss these notification if their gaze is not set on the screen’s corner.
artsyfartspants: By design, go away.
accessibilityperson: But..
artsyfartspants: Bye!
A week later
accessibilityperson: I completed adding ATK support to the application, you could grab my branch and try it out. I have other concerns regarding accessibility issues in this application that need to be addressed.
projectmanager: Great! Could we now do automated testing on our POS and increase it’s quality a lot?
accessibilityperson: Sure. I also wrote an Orca script for the app so that screen reader users have a pleasant experience using it.
projectmanager: k. Write automated tests.
Do I have a good solution to all the accessibility issues I brought up? Not necessarily, that is why we have good designers.
YES
designguru: Here is a writeup and a few mockups for the app. I did my best at universal design and included a diverse array of users in the use cases I designed for.
hackmaster2000 : This looks good! I will implement this while making sure that mechanism and policy are separate so that edge-case users can be accommodated for without intrusive patches and hacks.
projectmanager: Great work guys! The universality of the design, and the modular implementation will allow us to make some extra cash as we deploy this app for mobile devices and e-readers with little modification.
accessibilityguy: Lookin’ good. I have a branch with ATK support, I am currently testing this app with different assistive technologies. Could I suggest just tweaking this and that?
projectmanager, hackmaster2000, designguru: Absolutely, making sure our software is accessible is very important for our project. We support all our users, not just the first 80%.
projectmanager: I can haz magic testing now plz?
Postscript
Máirín’s writeup about the accessibility discussions at the UX hackfest really made me happy. So glad Willie Walker made it there, I thought of going, but Willie really knows how to drive a point home.
My friend just came by and asked if I am blogging about Open Sores. I guess so!
After what feels like an eternity of anticipation, the first GNOME Accessibility Hackfest begins next week. To put this into perspective, this won’t be a casual event. It’s a large conference riddled with many sessions of interest, a huge showroom packed with a milling crowd, 14 GNOME a11y contributors trying to get the most done together in the space of a few days, and countless hordes of cute (yet unpettable) guide dogs.
