unraveled

Holy Booklist Batman!

A great list of interaction design/information architecture/usability books is now available on Boxes and Arrows. If you’re going to buy one of these books, please buy it from that page; every purchase will help support Boxes and Arrows. Happy shopping!

  1. Heh…liked your Krug review *chuckle* krug as yoda…I can see that.

    hmm…question. On the URL input field…why not just have “http://” already set as the value instead of using the onblur event to place it there? Also…no first field focus? ;b

  2. I don’t set “http://” as the value of the URL field because if the form is submitted without the user entering a full URL, it will still link they’re name to http:// which doesn’t do much good.

    As far as automatically focusing on the first field, I hadn’t though of that, but it’s a possibility. Do you know how that affects screen readers? I would be cautious to use that if it took someone where they didn’t want to go on the page.

  3. Are the majority of your readers blind?

  4. hmm…after some thought you make an extremely good point.

    I wonder if screen readers work on cursor placement? What about voice browsers?

  5. After some research (http://www.w3.org/TR/REC-CSS2/aural.html) it looks like web pages get converted to plain text before being feed to the screen readers. Cursor placement wouldn’t be a factor then. However, I guess first field focus should still be one of those “right tool for the right job” sort of things.

  6. Thanks for checking that out, Dan. Useful information.

    I believe that every aspect of a design should be the “right tool for the right job.”

Go back to the top of this entry

Comments are now closed for this entry