On Jakob Nielsen's website useit.com, he recently wrote two articles on the problems with web usability in 2005. He wrote The Top Ten Web Design Mistakes of 2005, and Weblog Usability: The Top Ten Design Mistakes. They're both interesting reads, as well as both being fairly applicable to this website. So out of my own interest, I ended up seeing how grepping meaning fares against these mistakes. For each, I'll summarize the problem and respond with either a rebuttal, perceived compliance or what needs to be done.

They're not long reads, and they're rather scannable, so I'd suggest reading them over. Especially if you run some sort of blog of your own. Not all of them will apply to you, but it's good to have an understanding of what makes a page an interesting and readable page.

Web Mistakes

1. Legibility Problems:
   • bad fonts
   • re-sizable text
   • contrast

   Check. Standard fonts are used, without reliance on them. Only relative sizes are displayed, so the browser can display the page as the user wishes.

2. Non-Standard Links
   • making obvious what's click-able
   • explanations of linked content
   • and not opening pages in new windows

   I'm a strong proponent of not opening links in new windows, and letting the user make his choice, and I avoid the use of using words like "click here" as the link text. Only perceived problem here: difference in visited and unvisited links aren't apparent.

3. Flash
   • Jakob's guidelines for flash

   Don't really use it here, so moving along.

4. Content That's Not Written for the Web
   • making content that's short, scannable and to the point

   I use this space for links and rambling, though I've always considered myself a concise writer. I agree with these problems, and think I'm problem free in this area. Titles could probably use some work though.

5. Bad Search
   • having a search feature that actually works

   I find this site too simple for search, so my reliance is entirely upon Google here.

6. Browser Incompatibility
   • people use other browsers than Firefox, and your page should work in them

   It's simple, and true. From a practical perspective and a 'correctness' perspective. This site displays exactly how I wish it to on the major browsers.

7. Cumbersome Forms
   • they're used to often
   • too big
   • and ask too many unnecessary questions

   I really agree with this, and would also kinda add that they're often laid out poorly, but that's more of a technological limitation, I think. The only form I use is both necessary and simple. Check.

8. No Contact Information or Other Company Info
   • phone numbers, email, physical mailing addresses

   Doesn't really apply to me, but a necessary point for corporate pages, regardless.

9. Frozen Layouts with Fixed Page Widths
   • websites are either too small on big resolutions or too big on small resolutions

   Any site that assumes a specific resolution of their reader is doomed. Luckily, I think this site does fine at all resolutions, because of it's really simple layout. The only thing I think I fall short on here is text-width of the content. To improve readability, these content boxes should only be ten or so words in length per line. I'm still not sure where I stand on this one, though. Personally, I don't mind long line length. With a fluid layout, if the user finds things too wordy, showing less words per line just means having a narrower browser window (which I know a few people who run high resolutions and never maximize the width of their browser for this purpose).

10. Inadequate Photo Enlargement
    • having a large photo size that isn't actually detailed and large

    Doesn't really apply to this site, but a valid frustration regardless.

So, ignoring things that don't apply to this site at all, I'd say I scored a 6 / 7.

Weblog Mistakes

1. No Author Biographies
   • having an about me page to give yourself less anonymity

   I have a lot of personal information, the music I listen to, the blogs I read, the friends I have, my location and even my latest nethack death. My about me page, however, sucks. I'd denote this as a failure.

2. No Author Photo
   • to give a personable impression of the author
   • it connects the meatspace you to the virtual you

   I have an image of me, but it's a caricature of myself (as drawn by KEv). It's a personable impression, but no connection to the meatspace Qed. Another failure.

3. Nondescript Posting Titles Already touched upon.
4. Bad Linkage Already touched upon.
5. Classic Hits are Buried
   • not hiding your better written pieces in the archives, rather displaying them on the home page

   I really don't consider any of my writing to be notable in this regard, so I could technically say that I pass this one, but that's a cop out. I could mention my interest in usability and thus this article, for instance.

6. The Calendar is the Only Navigation
   • timelines are good, but so are categories
   • and not going overboard with categories is also a good thing

   I think my directory structure works well for the grouping and separation of what I write here. There's a large amount in my random folder, but that's because I post a lot of links. Overall, success.

7. Irregular Publishing Frequency
   • having a schedule, and sticking to it

   I'm not even going to touch this one. MacHall has been doing better than me recently. Failure.

8. Mixing Topics
   • specialized sites rule the web

   This site has a specific topic, mainly being a personal blog for myself and friends. So in that regard it succeeds. Otherwise, it's not really applicable. I know my readership, but I doubt I really stick to any topics.

9. Forgetting That You Write for Your Future Boss
   • how will this look to a hiring manager in ten years?

   In ten years I'll have changed a lot more. I mean, I'll be ten years older. But I don't think a personal blog should be too concerned with looking nice in ten years. A reasonably intelligent hiring manager will realize that this is mainly a personal blog, and this was ten years ago. A lot of change can happen in that time. It does give a good snapshot of who I was then though, which is information, and looking on it, it's information I'm happy with.

10. Having a Domain Name Owned by a Weblog Service
    • letting somebody else own your name means they own your destiny, adding any sort of obtrusive advertising and possibility of closure

    Everything's fine on this regard. Sure I don't have an QQQ.com address, but I do have absolute control over this page. Eventually I'll probably move to my own hosting situation, but that's for someone who isn't constantly broke.

This one gets a 5 / 10. Overall, I now see a few places I could really improve this page. And this time it's not actually from a code perspective. So, feel free to add your ideas and opinions in the comments section, regarding this list or your usability problems with this website.