usability fails are everywhere and it’s sad.
In: Uncategorized
18 May 2009Following up my last post about deaf accessibility with a post on iPod adapters may seem ironic. However, while I’m deaf, I do have a cochlear implant, and I do enjoy music. I drive back home to Lansing pretty frequently for visits, roundtrip about once every couple of weeks or sometimes more frequently. I’m not fond of driving, and the only way to make this trip tolerable for me is music – gotta have it, it’s an absolute requirement. Preferably loud and pounding. To this end, I’ve gone through a number of FM transmitters for the iPod, and have been sorely disappointed by the pickings. Let’s start at the beginning.

Brand X FM Transmitter
To be honest, this isn’t actually the exact one I bought, it just looks like it and cost around the same price. I don’t remember what brand it was exactly because I used it for all of two days. It failed at the very basic level: it couldn’t do what it purported to do. It gave such a weak signal that it was virtually incapable of broadcasting even the short distance to my car antenna, let alone defeating any traces of competing radio signal. It seems somewhat unneccessary to expound on its further fails, because if something doesn’t even WORK, usability is kind of a moot point, but what the hey, I’ll continue. It had a really narrow range of stations you could select from – only up to 91.3 or something like that. Additionally, its a station selector and LED display window was mounted ON the part that plugged into the cigarette lighter, which was way too far for me to be able to see from the driver’s seat even with squinting. And let’s be honest – my eyes should be on the road.

Monster iCarPlay Wireless FM Transmitter/Charger for iPod
I was actually pretty happy with this one, although at $70 (hey, I bought it at Best Buy, not Amazon) I learned that with these devices, you probably get pretty much what you pay for. Its main usability failing was that the radio stations were marked in teeny, tiny, little itty-bitty numbers, but since it was at the end of a cord I could actually bring it closer to my face. Still, it was too dangerous for me to look at it long enough to read which station it was on, but it compensated for that by using an absurdly bright LED light as the station selector, and splitting the stations among two columns. This allowed me to guesstimate which station I was broadcasting on by glancing at it and noticing that the light was, say, near the top of the right side and thus probably 88.5…ish. So I worked out a tentative peace with this device.
Alas, this peace was not to last. I got an iPhone and sold my iPod, and found out that an iPod cable is not necessary with an iPhone cable. If I didn’t turn on airplane mode it’d give off all kinds of crazy feedback. Naturally, this frustrated the hell out of me, but I didn’t want to have to pick between looking at a map and listening to music, so I bought yet another FM transmitter on Amazon, one purportedly compatible with the iPhone, and gave the Monster transmitter to the chick I sold the iPod to.

PDO CarFM transmitter for ipods and iphones
Little did I know I was actually purchasing the spawn of Satan. This thing aspired to ruin my life from the moment I unboxed it. It came with a baffling remote control (a remote control? Inside a car? I mean…okay, whatever) that didn’t actually work. And although it was supposedly compatible with the iPhone, it would bring up the old “not compatible, airplane mode?” prompt, although I could select “no” with no ill effects. It was horribly unusable. The LED display and selector buttons are actually on TOP of that contraption, which means that there’s no way to see what station it’s transmitting on unless you actually lean directly above that thing. The buttons were hard to press because they were shallow yet needed a lot of force to actually make the selection, so I would have to squeeze down on the buttons really hard to change the station. Worse yet, they had a very high latency so I couldn’t just hold them down, or repeatedly press them in rapid, mindless succession – I had to squeeze, wait a beat, squeeze, wait a beat, check to make sure the button presses have actually taken, squeeze again…
And worse yet, within a couple of months the speakers started transmitting this purportedly weird high-pitched noise. I say purportedly because it was actually out of the frequency range that my cochlear covers, so it never bothered me, but my passengers complained about it, and eventually it was pointed out that the high-pitched noise was actually blinking in time with a slight flickering of my clock and stereo lights. So, I stopped playing music when my passengers were in the car, but I was determined to keep using it because I was tired of buying FM transmitters. But then one day it actually BLEW OUT MY FUSE and killed everything in the stereo dashboard – the stereo controller, the clock, everything. Of course, I had no clue what happened, and figured it was a fluke, and put in a new fuse. Within a few seconds of plugging this horrible contraption back in, it BLEW OUT MY FUSE AGAIN, and it finally dawned on me that it was time to buy yet another freaking FM transmitter.

DLO TransDock Micro
So I got this thing. I’m fairly happy with it. It doesn’t have a great signal so it was tricky finding a station it worked with, but it is by far the most usable transmitter I’ve found so far, because of a genius feature I can’t believe I hadn’t come across before: you can push that little wheel and get it to automatically scan for an open station for you. Granted, this feature doesn’t actually work all that well, but it’s nice they’re trying. Usually, I just turn the wheel to manually tune it. It has big huge numbers on the front so you’re able to easily see which station you’re on. Of course, the usability fail in this case is that I drive a manual and it’s in just the right position that I can’t actually SEE the thing when I’m driving. The product picture on the website shows what must be a really idealized version of a dashboard and cigarette lighter, with the thing neatly out of the way, and of course, facing up at a very sharp angle.
You know, though, I’m starting to think that car FM transmitters are just a broken technology, plain and simple. It seems fairly difficult to actually make one that works well. FM transmitters need to afford ease of use while driving, and the user experience is just never gonna be integrated all that tightly, because even if the FM transmitter is fantastic, you still need to fiddle with the radio station itself. Next time my FM transmitter breaks, I might just break down and buy a car stereo that has an adapter for a headphone jack. I just need something that looks kinda like this:

A jack, and a volume knob. If ya wanna get really fancy, the ring around the jack would glow blue when the jack is seated properly, and LED indicators around the volume knob would glow according to how high you turned the volume up. Done. Of course, I suspect nothing this simple would ever make it to a car stereo shop.
In: Uncategorized
2 May 2009This is a very long post. The first half deals with my lifelong experience with TTY usability, and the second half deals with accessibility and usability.

I’m deaf and have a cochlear implant. I communicate extremely well face-to-face, but it’s extremely hard for me to understand most people on the phone, so since I was a little kid, I’ve had to use a TTY to make any phone calls. The picture above is of a TTY that I found in the Detroit Airport’s McNamara terminal. It basically works kind of like a very lo-fidelity modem – you align a phone handset on top of it, and as you type away the keys all make different sounds that get transmitted over the phone line. I’d estimate the upper limit at somewhere around 40 words a minute. Some places would have their own dedicated TTY lines, but to call most places, I had to call the Michigan Relay line (I still have the phone memorized, and it’s probably been a decade since I last used it), where an hearing operator with a TTY would say what I typed to the other person, and type back what they said to me. It’s an incredibly cumbersome way to communicate, but sometimes it’s been the only way that I can, first via this little dinging box, and then a few years back, this site called http://www.ip-relay.com showed up, which let you make TTY calls over the web.
My entire life, I’ve struggled to get AWAY from using TTYs because they’re so incredibly unusable. They’ve got a very slow rate of data transmission, even slower if the person you’re talking to isn’t a very fast typist, and you can’t both speak at the same time, so you have to use the code “GA” to indicate when its’ the other person’s turn to talk. Not only that, but very few other people are familiar with TTYs, let alone relay networks, so seriously half the time I have to call an utility company about a bill, I get hung up on because they think I’m a telemarketer. (I dunno, it doesn’t make sense to me either.) I can’t even call my bank this way, as my bank has a policy against accepting relay calls, because apparently the privacy restrictions imposed on the relay operators make it a pretty appealing cover for scammers. When I was trying to arrange for a visa to travel to Russia, I had to spend hours on the phone with this absolute nightmare of an agency whose employees were convinced that I was only calling them via TTY to make life difficult for them (again, baffling).
Not only that, but every phone call takes me twice as long to make as it would for a hearing person, because I have to connect to the relay operator, type to them who I want to call, and then have them very cumbersomely type out all the phone tree options (and then call back again and go through the whole thing again when the session timed out because it takes so long to type out everything). ip-relay’s interface doesn’t work like an IM interface, but more like a synchronous free text chat, which means there’s no beep or flashing to let you know when the operator’s typed something at you. The upshot of this is that when you’re on hold, you have to sit and STARE at the screen while the operator types “still holding … still holding …” every 15 seconds or so to let you know they’re still on the line. If you think being on hold is boring as a hearing person, imagine that you had NO WAY to be able to multitask. Truly, whenever I have to call a government office I want to stick a fork through my eyeballs. I’ve been on hold over an hour many times, just staring at the screen, waiting for someone to answer. And I get ‘accidentally’ hung up on a LOT because if it’s 4:30, the tech support person on the other end would much rather end their shift on time instead of dealing with a TTY customer, who are incredibly cumbersome to support. Don’t really blame them, but I still hate it.
In addition to the user experience problems, the ip-relay interface is painful! I love the service that ip-relay provides, but let’s take a look:

Besides the lack of notification mentioned, my biggest problem with the interface is that because it’s a Java applet, when I come back to it from another window, program or tab, I have to put the focus BACK into the applet to be able to type into it. This means that if I see a message I want to respond to, if I hit backspace, I accidentally go back to my last page, and of course, going forward again doesn’t help – I’ve lost that session. I can’t count the number of times I’ve accidentally ‘hung up’ on people that way. It’s doubly frustrating if I waited on hold for an hour and have to start the whole thing over. The interface has changed a little since I last used it, and maybe that “print” button works now, but last time I tried to save a transcript of a conversation, it didn’t work, and because I was reporting that Russian passport agency to the Better Business Bureau, I had to painstakingly scroll up and save a screenshot of each and every page…about 20 pages worth of pain. And of course, because it’s a heavy Java applet, every now and again my browser will throw a fit and crash.
Anyway, I have tons of stories about how a TTY protocol is painfully unusable, whether it be by old-fashioned machine or by relay website. So I’ve struggled to not use the phone, ever, because this mode of communication is just full of usability FAIL every which way I turn. And I’m lucky that it’s 2009 and there are so many millions of ways to communicate that I literally only have to use a TTY about twice a year. I use email, IM, SMS and Twitter, and these all more than fill in the gap for me.
Which means that if a company does force me to use a phone to interact with them, I get really, really cranky, because nobody likes to use a phone (see this spot-on post from 37 Signals, “why would you want to call me?“), least of all me. Example: this semester, I’d done a lot of traveling and as a grad student, needed to get a lot of work done in airports, so I signed up for a Boingo account. The signup was quick and easy – give ‘em a credit card, download a little program and boom! I have wireless access in any airport, Starbucks or McDonald’s for $9.95 a month! Not a bad deal, eh? After I got the brunt of my traveling done this year, I decided to cancel my Boingo account and just reactivate it next time I needed to fly.
Except that you couldn’t cancel online. You couldn’t cancel via email either. Verily, the only way to cancel was to call them (and, I assume, go through a rigamarole about why you weren’t happy with the service). As a hearing person, I wouldn’t want to take time to call and cancel when I can just click a button on any other website, and as a deaf person I get unduly cranky at the prospect of having to do so. This was deliberate, of course, and in my head I can almost see stakeholders in suits sitting around a mahogany table talking about ROIs and profits and deciding that they would make it hard for people to cancel in order to rake in profits from everyone who decided the exit barrier was too high a hurdle to jump. This made me incredibly cranky, of course, so I emailed them and explained not only my situation, but also that providing a high exit barrier makes people reluctant to dip in and out of their services as needed, and also creates unhappy customers that will tell everyone they know that Boingo is a difficult company to work with.
And then I followed this up with a tweet, because well, it’s 2009 and now we can complain with megaphones. And I wasn’t 100% surprised to get a response back from a Boingo rep on Twitter, who was very friendly and overly eager to smooth things over and I could tell his job was kind of to put out Twitter fires over things he wasn’t really in charge of, and I felt a little bad for him. And he was very nice and within an hour he’d gotten my account canceled for me and everything straightened out. So, I was still a little cranky, but very pleased by how quickly they responded on Twitter. (I had the same experience with the Omnigraffle team, and with the Peabody Hotel folks, so A++ to companies that invest in Twitter resources!) Funny thing is, the next day, a Twitter friend of mine, completely independently of my tweets, made the exact same complaint, and the poor Twitter rep was over there putting out fires again, except this time he told my friend that an online cancellation feature was the next thing that was getting released.
So yeah, I appreciate that they’re putting out fires, but this does make me think of one basic principle of disability accessibility: making something accessible for one person makes it accessible for everyone. Look at closed-captioning – it didn’t used to be ubiquitous. Only through legislating that most TVs released after 1993 have closed-captioning decoder chips did it become ubiquitous. And man, everyone uses them. Captioning is used in bars when TVs are on mute, captioning is used by our elderly parents, captioning gets turned on in movies with incomprehensible actors. Deaf people aren’t the only ones to benefit. And the same thing’s going on with Boingo – by making it easier for deaf people to do business with you, you make it easier for everyone to do business with you.
In: Uncategorized
30 Apr 2009This one comes from the FAIL Blog:

My first thought is: someone actually read the EULA?
My second thought is: this was actually a past issue to the extent that the lawyers wanted this in the EULA?
In: Uncategorized
16 Apr 2009ATTN: Recruiters,
Your job application form should never be so painfully unusable that I decide halfway through that the internship just isn’t worth it.
Love,
Me
In: Uncategorized
13 Apr 2009This is a tag off of a Batman t-shirt I bought a little while back. Isn’t it an adorable little fail?

In: Uncategorized
13 Apr 2009I just got back from a hectic week in Boston at the CHI 2009 conference. I spent a couple of days wandering around Boston, and I think it just may be my new favorite American city…what a wonderful place. Beautiful architecture, great food, amusing accents. Monday, we got down to brass tacks, and WantKnot and 9 other teams presented our Student Design Competition posters.

Although WantKnot didn’t make it into the final round, two very excellent teams from the School of Information did – TreasureHunter and MIFresh – and it was very exciting to see them clean up with 1st and 2nd place in the final round. Having never been a sports fan, I think I finally understand what it’s like when your school teams win a football game.
I went to so many presentations and learned so very much and, like IA Summit, I can’t possibly recap everything I saw. I did get a couple of major impressions, though. One is that when I’m reading academic papers, the methodology section often puts me to sleep, but when I’m watching a paper presentation, the methodology is very interesting and in some cases was the most exciting part of the presentation for me. For instance, the paper given by several Microsoft Researchers on developing user-defined gestures for surface computing was one of my favorite presentations, not because of the end results (although those are interesting too), but because it laid out an interesting and unique framework for how to do participant design right. Similarly, although I was annoyed by Eindhoven’s 10-minute recruitment videos, I appreciated learning about a design method that starts with music and ends with a tangible product to carry a specific feeling throughout a design in a very systematic way.
Another theme is that I was really, really interested in the interaction and mobile sessions. This probably pretty accurately reflects my growing interest in working to unify platforms for ubiquitous computing, of which I believe mobile interaction is a huge part. I also like learning about clever situations to tricky problems, and a lot of cool new interaction methods do that. For instance, on a mobile touch-screen, being able to detect thumb rolls (versus slides or taps) or having a side bezels that can be swiped inward to select things, opens up many possibilities of intuitive new ways to map actions and add in contextual menus. I also tried to attend some of the sustainability panels, but I was surprised by their relative paucity. I assumed that because of the Student Design Competition’s theme of sustainability, there would be a theme of sustainability in the conference too. Guess not!
Between CHI and the IA Summit, it’s hard to say which I liked better because the two were so different. I think if I were to shell out the bucks for them next year, I would probably rather attend the IA Summit. It was much smaller at around 500 attendees, but still an important enough conference that all the rock stars came out. This meant I had much, much better opportunities for networking! CHI was such a zoo all the time that it seems like I didn’t really get to know very many people, even though I was constantly shaking hands and exchanging business cards. IA Summit was also a lot more hands-on and practical, which makes sense, given that it’s a professional conference. Some of the topics seemed like pretty old news to me, but they were topics that could be put to work the next day.
One of the things that inspired me, but also really frustrated me, about CHI was the huge gap between a cool idea and any sort of practical implementation of it. I got the sense that this was all stuff that would be huge in a couple of years, but it’s up to me to figure out how. While that’s inspiring, I may not always be in a position where I get to design car windshields that have map overlays, you know? Inspiration shouldn’t be discounted, though, as getting to see all the clever solutions to all the wicked problems definitely gave me a lot of ideas for how to approach design challenges.
As an aside, I took lots of notes as usual, but this time, I did it a little differently. After re-learning how to draw last semester and missing my sketchbook, and after learning of a new study that says doodling increases focus and recall, I tried out taking sketchnotes.

I’m nowhere near as good as this guy, and my notes aren’t useful to anybody except me, but my notes are a lot more accessible to me after the fact in this format. Since I have to quickly take what someone says and try to figure out how to represent it visually, I actually do more analysis and less transcribing, so my brain is working now instead of storing things to sort through later (and much like your junk drawer, you never sort through those things later). Also, the notes are immediately visually sensible to me and are highly browsable, whereas my regular style of note-taking requires actually reading. Flipping through the notes for a human-readable 2D barcode system (another presentation that really excited me) makes me instantly remember how the nuts and bolts of the system come together – an abstract concept that might otherwise take me a while to recall and eventually be lost because of its lack of salience.

On top of all that…when someone is going rapid-fire through how an interaction works, it’s just easier to draw a picture than to attempt a quick verbal description.
In: Uncategorized
29 Mar 2009It’s been a week since I got back from the Information Architecture Summit. It was great, and fascinating, and interesting. There’s been a lot of food for thought churning in the back of my head, and now I’m going to try to make sense of it. One of the strongest themes was about pulling together IA as a field, and about how in-fighting about the definition of IA is weakening our position in the job market. This was manifested most strongly in Jesse James Garrett’s closing plenary speech, in which he declared that there was no such thing as an information architect, there never has been, and anybody who calls himself an information architect is a fool or a liar. Rather, we’re all user experience designers.
This is obviously a controversial move, and as a newbie to the IA field, I can’t help but wonder where this puts me. On one hand, I had hoped to leave IAS09 with a clearer idea of what it means to be an information architect, and on the other hand, simply being told that we’re user experience designers doesn’t quite ring right for me. It makes sense when I think about it in the way that Chiara Fox explains it, but it seems like we’re throwing the baby out with the bathwater. Perhaps the field of information architecture has evolved and we’re not all doing content inventories and taxonomies (but this seems inaccurate), but just because our tools have changed doesn’t necessarily mean that our job hasn’t. I wonder if one factor in what’s happening is a split between the job duties of the marketing, branding IAs who work with crafting cross-platform experiences and social websites, and the IAs who design business applications and heavily functional, database-driven websites. In the former case, I can completely see why the title user experience designer makes sense, but in the latter case, I don’t know that I could say with a straight face that digging into databases to redesign a report front-end is user experience design. That still seems like old-fashioned information architecture to me.
When I think back to the connections between real-life architecture and information architecture, and remember some of the lessons in de Botton’s Architecture of Happiness – namely, the concept that architects design space for use, to evoke certain feelings and actions, to guide people’s thoughts – it seems that the basic, fundamental concept behind information architecture hasn’t really changed. But I say all of this with a grain of salt – as a newcomer to the field, I don’t particularly have much invested in one job title or the other.
And who knows, maybe this is all JJG’s way of saying “IF YOU KIDS DON’T QUIET DOWN THERE I’M TURNING THIS CAR AROUND”.
Anyway, I saw some really great, non-politicized, educational sessions too.
Some of the ones that really stick out for me are Stephen Anderson’s “designing seductive interactions”, Jared Spool’s “design treasures from the Amazon”, John Pattengill’s “How to save mobile internet”, and Chiara Fox’s “what IAs need to know about Web 3.0″ (aka semantic web). I have tons of notes and impressions from all of these, so if you wanna hear more about what I thought, just ask me! For I must get ready for CHI 2009 and cannot sit here typing away at my blog any longer.
In: Uncategorized
29 Mar 2009Woohoo! To toot my own horn, the WantKnot project I’ve been working on won 2nd place in the expoSItion contest in the Social Computing category. Great work, guys! We’ll be going to CHI next week with our project, and that should be fun.
On to the fail: when I arrived in Memphis, I felt fortunate to see such a hilarious fail waiting for me in the hotel room. It’s not an UI fail, but arguably this inhibits the usability of the product for the lactose intolerant.


In: Uncategorized
25 Mar 2009Looks like blogs are trying harder and harder to monetize their sites. Jezebel has got one of the most infuriating ads I’ve seen in a while. The top of the site has long been a leaderboard for popular stories and takes up quite a bit of real estate, and as a long-time reader (hey! grad students need a break too) I’m used to going right to that spot and clicking on something that might catch my eye. Their new ads wait a few seconds after the page loads, cover up each leaderboard box, and then suck up my processing power doing a cool little flash fadeaway or whatever. Like so:



My train of thought goes something like this: “Omg, I hope Brangelina are doing okay! I shall hie on over to click on this story! Oh my god, THINGS ARE FLYING ON MY SCREEN! Where’d it go? Wait, I already clicked and now I’m somewhere completely different…Hit escape! escape! ESCAPE! What…so what is this? Wait, it’s going away before I can even read it…”
And of course, a blog post about monetization wouldn’t be complete without discussing Twitter. The NYT has an interesting discussion about how trying to develop and then monetize can potentially backfire, because users may resent paying for a tool that was once free. Based on what I’ve seen on the internet, I think this is a good point.
While I’m here, WordPress, don’t think I’m letting you off so lightly. Every time I have to upload a picture via your uploader, a small part of me dies. Firstly, because I can’t upload more than one picture at a time. Secondly, because you default to the flash uploader which always gives me an error (Error #2044: Unhandled IOErrorEvent:. text=Error #2038: File I/O Error – oh, is THAT all?), and well, you should really have the errors worked out before you make it the default tool.
I’m also not happy with the usability of the current template, and it pains me to have an ironically unusable blog about usability fail, but I haven’t had time to fiddle with the template yet. I’m reluctant to throw out the baby with the bathwater because the visual design appeals to me, but it needs work. Why do so few people make simple, usable WordPress layouts?
In: Uncategorized
23 Mar 2009I made a post last week criticizing TennCo’s wildly unusable form and hilariously sad infographic and then more or less forgot about it. They picked me up on time from the airport and gave me a quick ride and I had no complaints. Except they were terribly confused because I had specified online for them to drop me off at the Hampton hotel and pick me up at the Benchmark hotel, because I was crashing with Katie McCurdy for the first few nights and then switching hotels when she left. Anyway, they told me to call and follow-up with them on it, so I had the lady at the front desk do it for me because I am deaf and don’t do well on the phone. We discovered that even though my flight leaves at 7am, and their first shuttle doesn’t run until 6am, and it is a 25-minute ride, and thus between security and last call for boarding, it would be PHYSICALLY IMPOSSIBLE for me to get on my flight before it left, their site let me go ahead and book the trip anyway.
Yeah, that’s a big big big big BIG HUGE fail. Now I get the dubious pleasure of calling them and haggling for my money back.
On the upside, the lady working the Benchmark front desk was not only gracious about helping me out, she was so pissed off on my behalf that it made me feel a lot better. The Benchmark may be kinda skeevy and I may be afraid to take a shower (though lord knows I must), but I am grateful for good customer service.
Anyway, the Information Architecture Summit is over and it was mind-blowing. I took copious notes and livetweeted like mad, and I have all kinds of food for thought that I’m going to share on this blog. Unfortunately, a combination of a big pile of work to catch up on, and 2 hours of sleep due to food poisoning (FAIL) has left me too slap-happy to do this right now. But obviously, I wasn’t too slap-happy to report on this FAIL.
My name is Leanna Gingras and I'm a graduate student at the University of Michigan's School of Information. My main vice is angry muttering. Instead of angrily muttering to myself whenever I encounter an astonishingly ineptly-designed object, I will mutter about it here and you can read it and we can angrily mutter together. I'll also be posting about stuff I do, links I think are nifty, and places I go.