And we have a winner

After reviewing the many entries to my little tagline contest, I have decided on a winner. It was hard to choose just one of all the good taglines that were suggested, but with a little help from some friends I settled for…

”456 Berea Street: Between Web Standards Boulevard and Accessibility Road”

It wins because it contains both “web standards” and “accessibility” and refers to the site name in a clever – but not too clever – way.

A copy of Getting Real is on its way to Michael Wales for coming up with that one.

But wait, there’s more. While going through the submissions I decided to hand out two more prizes. There were so many really clever and funny taglines posted that I was very tempted to pick one of them. However, as a couple of people have pointed out in the comments my content isn’t very humorous, so perhaps the tagline shouldn’t be either. But who knows, I may change my mind some day. So one of the extra prizes is for “Most humorous tagline”.

I also noticed that a few people have posted lots of entries. To show my appreciation for that, I’m also handing out a prize for “Best effort”.

Aaaand the winners are:

  • Most humorous tagline: “456 Berea Street: It’s not a tag(line), it’s an attribute!”, by JW.
  • Best effort: DaveMo, for posting 28 entries.

Michael Wales, JW, and DaveMo: check your inboxes for a copy of Getting Real.

I hope you enjoyed this. I sure did.

Posted on April 2, 2006 in Site news

Comments

  1. Spot on.. Good choice!

  2. Very good choice! I liked the humourus one :)

  3. Really great choice, I like it, I like it alot!

  4. Congrats Michael Wales, it’s well deserved to my opinion.

    I think DaveMo also really deserved a price, his submissions were clever and funny.

  5. April 3, 2006 by Ole Hansen

    Good choice. Michael’s idea was quite close to the reasoning behind my own suggestion, so I can definately aggree with that. And his was better than mine.

    So congrats from here to Michael as well.

  6. April 3, 2006 by stu

    Most humorous tagline: “456 Berea Street: It’s not a tag(line), it’s an attribute!

    Thats about as humerous as a developer saying “its a microsoft ‘feature’” every time a bug is found then laughing at there own joke.

  7. April 3, 2006 by stu

    The winning one is pretty good though - although the problem i have with it is why its pretty cool - does it actually tell me what the website does when looking in search engines as much as the last tagline did?

    Im not sure.

    In all fairness though, i found this site through the brilliance of its articles rather than the strapline, so maybe im missing the point.

  8. Although I really admire DaveMo’s efforts, does this mean that you support, and even encourage, spam? ;-)

  9. I like it, but it doesn’t really roll off the tongue. Why not shorten it to 456 Berea Street: At the intersection of Web Standards and Accessibility. Just my two cents…

  10. April 3, 2006 by Johan

    ”456 Berea Street: Between Web Standards Boulevard and Accessibility Road”

    why not:

    ”456 Berea Street: Always floating at the cross-roads of Web Standards and Accessibility”

  11. hahaha awesome. I love the final tagline.

  12. Great choice! Also enjoyed “456 Berea Street: It’s not a tag(line), it’s an attribute!” :D

  13. I reckon “Between Web Standards Boulevard and Accessibility Avenue” has a better ring to it. But then what do I know?

  14. April 3, 2006 by DaveMo

    I’d like to thank The Academy and all the “little people” that made this award possible! ;^J

    Call it annoying persistance if you will, I call it inspired lunacy! Actually, something about this particular contest kept the ideas popping in my head, but I was doing it mostly for fun and because I like Roger’s efforts and the information I get from his blog.

    (And in spite of Mr. Nyman’s backhanded compliment, I will STILL visit his site for continued enlightenment also! =^J )

    I wish I had a fraction of the knowledge, dedication and creativity of the folks who do your kinds of work gentelmen, but I continue to be inspired to improve my professional efforts as accessable and Web Standards compliant as I can.

    Congratulations and thanks to all!

  15. April 3, 2006 by Roger Johansson (Author comment)

    Like I said, I might change my mind some day. Or maybe tweak it a little. I’ll leave it as is for a while though.

    DaveMo: Hehe, yeah I could tell the ideas just kept on coming ;-).

  16. Nice - thanks for the prize! I consider it one hell of a “weddding/baby/coming home from a deployment/moving to a new base” gift.

  17. April 4, 2006 by Phil Ridlen

    I personally don’t care for the now tagline. It’s… I don’t know.

    Whatever.

  18. So if Berea Street is between Web Standards Blvd. and Accessibility St., what’s the cross-street?

    And with these new streets, why on Earth aren’t you now living on Web Standards Blvd. or Accessibility St.? (What — you don’t want us to find you? […Or do you, if you really do live on 456 Berea St.?])

  19. liked the humorous one best.

    it sounds like: “it’s not a bug, it’s a feature”

    hehe :)

    cheers.

  20. Sorry for being off topic here… But whats the idea behind removing direct links for those who comment? Is it for spam reasons?

    Just wondering, I have nothing against it at all!

    Btw. I stick to Nicholsons suggestion for the new tagline. Avenue “klingar” really great ;)

  21. April 4, 2006 by Roger Johansson (Author comment)

    D. Olsson: Yes, spam reasons only. I hope the direct links will be back eventually.

    Avenue instead of Road. Hmm. You have a point.

  22. April 20, 2006 by Search Engine Guru

    Your winning entry is too long and wordy.

    By not having the phrase: “Web Standards and Accessibility” as written here, then you are losing opportunities to be indexed more properly by search engines than compared to the example where the words boulevard and steet comingle with important terms. A simple and less customer-confusing tagline would be “The Road to Web Standards and Accessibility”.

Comments are disabled for this post (read why), but if you have spotted an error or have additional info that you think should be in this post, feel free to contact me.