Software Accessibility Redux

After the flurry of comments on my last post about accessibility on the web, I wanted to add another tidbit of interesting and related news. An aspect of accessibility that is often not thought of during software and web site design is the troubles that occur for users who are colour blind. Basic usability tenets hold that encoding meaning into colour needs to be done carefully for various reasons such as colour blind users and the large variance in cultural significance for a single colour.

But I’ve always wondered what colour blind users actually experience of my designs. It is a simple thing to activate a screen reader and check to make sure that it is able to convey the meaning of the screen verbally. But how do I check to see what a colour blind person sees?

I came across this neat blog entry by a programmer about a new tool that allows you to preview software in the 3 distinct “flavours” of colour blindness. Note that I did not say you can easily do the preview – it doesn’t look easy at all and seems to be limited to a specific means of building software. However I think tools such as this are a great idea and if we could make this kind of analysis easier and more commonplace I’d be a much happier guy.

Blind Man Sues Over Website Design

News has surfaced that a blind man has sued Target over its website’s inability to be used properly by blind computer users.  The link I’ve included is, frankly, embarrassing because I think of that online community at arstechnica as intelligent and typically non-reactive.  However if you follow the article’s discussion link you’ll see some really, really stupid responses.

This particular issue strikes a chord with me because in a past life I wrote a research paper on the experience blind users have on the Internet.  I interviewed a blind man and talked to him about his experiences with the Internet and the pages he uses daily.  The sad part is that he pointed out this exact problem to me though it was with the Vancouver Sun’s website at the time.  That was over 5 years ago now I believe.  Isn’t progress grand?

I am doubly perplexed by people’s comments that coding web pages for blind people is difficult.  Continue reading Blind Man Sues Over Website Design

Software Bugs – Benign to Lethal

A recent Wired article on the Top 10 Worst Software Bugs in History is an interesting read, but of course I have something to add.

On the list are two medical-device related software bugs. The first is the Therac-25 bug wherein patients were inadvertently exposed to large doses of radiation resulting in at least five deaths. This is a straightforward engineering bug. It’s interesting to note the various causes included in that Wikipedia link. It warms my heart to see so many systems being examined to see if they contributed to the error.

The second one occurred relatively recently (2000). The device’s designs were not followed or understood properly and technicians ended up killing at least 8 patients through massive radiation overdoses. More on this one below.

Here are a few links to other disasters or problems caused by software bugs:

  1. USS Yorktown: a US Navy ship suffers full system shutdown when someone enters 0 for a database value on ship.
  2. 2003 Blackout in North America: part of the reason the blackout was so extensive was alarms going off weren’t displayed due to a software bug.
  3. Full scale Soviet attack: in 1979 NORAD quite literally sat stunned as it witnessed a full-scale Soviet missile attack

Continue reading Software Bugs – Benign to Lethal

What a Great Interface!

Marty sent me a link to this baby name page that allows you to see the popularity of names in the US since the 1880s. While the content is interesting enough, I am totally impressed with the interface.

There are some clunky parts (like how do you know if your cursor is currently in the name typing space or not?) but otherwise this is a very good way to visualize this data. It incorporates a quasi-zooming interface that updates as you type. You can use the mouse to find further data on specific parts of the graph. Sadly they resort to the age-old blue=boy girl=pink colour scheme, but that’s forgivable considering the audience.

Overall I’d say this is a great use of technology! Hats off to the designer and coder.

You’ll note that the name ‘Kirk’ has fallen out of favour … I mean why even bother trying to get your kid to live up to that high of a standard? It’s just setting the kid up for a lifetime of disappointment .. unless it’s a girl… nobody’s named their girl ‘Kirk’ yet. Do we dare?

I Hate Internet Explorer

I’m currently designing a website interface for a personal project. Things are at the preliminary stages, but I’ve already stumbled across the one reason I hate working with web pages in terms of design …

Internet Explorer simply does not adhere to web standards.

What this means is that I can plan a layout for the website, code it according to industry standards, and test it in Firefox. It will look like this.

Website viewed in Firefox browser

Please understand that this is a preliminary design. Ignore the colours and layout as I’m using them to rough out my ideas. In all likelihood things will change dramatically as I build the site up. But at this point it is good to take a look at the basic structure of the site.

I then decide I should test it in Internet Explorer too, simply because I know everyone doesn’t use Firefox. Why that is I do not know, but I know the majority of people are still using Internet Explorer. OK, and here is how the page is rendered by I.E.

Website viewed in Internet Explorer browser

The exact same code, but with totally different results. Now I need to go and figure out if there are any known tricks I can use in order to make I.E. pretend it is standards compliant. I really hope I.E. 7’s CSS support is vastly improved when it comes out.

What Do I Do?

I’m moving into a new job tomorrow, and I’m being asked (understandably) what exactly I’ll be doing. Since I haven’t actually started the job yet, it’s tough for me to give concrete examples of what I’ll be doing, but let’s see if I can’t shed a little light on my super-secret mystery.

My official title will be “Systems Analyst / User Interface Designer”. Now that’s a mouthful. However it is also nice and descriptive. As you may or may not know, when it comes to computers, I’m deeply interested in usability and the user experience. I’m able to do programming when I want or need to, but in the end I’m not terribly passionate about the inner workings of programs. I’m more interested in how people interact with them.

So what does a Systems Analyst do? In a nutshell I’ll be looking at customer requests for improvements and new features in our software and I’ll be trying to figure out the best way to fix our software up. The best way may or may not be what the customer asks for exactly, but requirements elicitation should be part of the process so their initial needs may end up changing as our discussions continue.

It’s still a little abstract, I know. However I came across this great example of systems analysis (in the guise of the term “Information Architecture”) to a batch of today’s emerging music players. For anyone interested in IA or SA, it’s a neat, simple read. Anyone not familiar with the things we do, it’s a simple introduction because we all understand digital music players to some extent.

As for the title “User Interface Designer”, that’s where my heart lies. Designing the interface and workflow that users are confronted with when using software is my real area of interest. I enjoy the designing phase of things so much because I find it to be so creative – implementing mock-ups of the interfaces and running user trials to see how they work in real situations is just plain fun for me.

So this position is my first step away from supporting technology and users (Systems Administrator, that kind of thing) towards my real area of interest – usability. I’ve been dipping my toes into whatever Usability waters I can find, such as recently joining a project at Open Usability and participating in several discussions on the Gnome Usability Mailing List. And now I am finally moving into this fascinating area professionally.

Huzzah! Wish me luck!