inicio mail me! sindicaci;ón

Ask.com Turns Up the Heat

by Paula Thornton

ask.com.pngThe heat is on, on the street…”. The Glenn Frey hit song came into my head this morning as I saw 2.0 in action in an ask.com network TV commercial. They’re leveraging 2.0 features as a differentiator against the competiton, with middle America!

Of course, the association to a music track was incited by the commercial itself because they showed how the results interface displayed and recommended an audio clip that was immediately available to launch. But in the commercial there was a 3rd column that was decidedly missing in my test below.

A quick self test reveals the following 2.0 features:

  • auto-recommender in the entry field
  • a cleaner interface in general, including a results page that moves the entry box to the left, equi-distance to the top of the screen with the results (take a hint FAST)
  • results lines that can be ’saved’

What I didn’t see was the balloon pop-ups (that we typically reference netflix.com for their product roll-overs as an example) that were displayed in the commercial [I’m willing to give them the benefit of the doubt on this one — the Friends and Family commercials hit the airwaves just a few weeks after the IT group at MCI had been contacted to ‘consider’ the realm of changes that had to be put in place to support it].

I’d want to then see an assessment from my industry colleague Derek Featherstone (whose name didn’t come up in the auto-recommender!) as to how accessible all of these features are. 2.0 features are not inherently inaccessible — their creators simply have to be designing for accessibility from the start. Leaving the question unanswered, “Did Ask.com go the full design distance in their quest for differentiation?”

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google


1 Comment »

  Derek Featherstone wrote @ October 16th, 2007 at 10:31 pm

Ooooh, great question, Paula! The short answer is this: the web starts out being accessible by default, and then when we develop, we start to take that accessibility away.

Looking at the auto-recommender I notice a few things:

1. when I start typing, and the “Search Suggestions” pops on to the screen, how does someone that can’t see even know that it is there?
2. where in the source order/flow of the page is the “Search Suggestions” box? it appears to be at the end - after all of the links in the footer (once it shows up, start tabbing and you’ll see the tab focus move through the footer links and then through the suggested search terms)
3. does the JavaScript that reads the keystrokes for using the up and down arrows in the Search Suggestions box work properly when a screen reader is being used?
4. will the Search Suggestions box show up at all when voice recognition software is being used? maybe, maybe not…
5. I like the “Disable” link - a nice feature, but one that doesn’t persist. If I refresh the page the Search Suggestions are enabled again. If the functionality interferes with assistive technology use then the fact that it doesn’t persist makes it much less usable.

Ah, a lovely case study, requiring some testing :) Thanks for pointing it out, Paula!

Your comment

HTML-Tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>