And then I see this:

Wait, what?

Okay, so let’s ignore the minor usability problems for a second, such as the red borders on the text inputs that scream “invalid”, the placement of the text explaining which fields are required after you’ve already filled out the form, and that big brown rectangle that’s actually a textfield, not to mention those awful indented buttons.  What we have here is a monumental failure to sanity-check your error correction against real-world data.  Yes, in case you haven’t guessed, this form will not accept the city “Ann Arbor” because it has a space in it.

Now, I know for a fact that computers have no problem whatsoever in storing data with a space in it.  (Heck, my full name has a space in it, and this form clearly accepted that.)  This can only mean that someone, probably a well-meaning but poorly-informed programmer, made an explicit and intentional choice to deny city names with spaces.   Really, couldn’t you think of a single example of a city name that legitimately has a space in it?  You didn’t think of New York City, Los Angeles, Las Vegas, San Antonio, or Kansas City – not even my hometown of North Plainfield, New Jersey?

I understand that this form is obscure enough that it wasn’t worth running a full-scale usability evaluation on it, and I could understand if this came up on the web form of a business too small to afford usability testing.   But I expect better from Harvard, one of the most prestigious universities in the world.

So, to finish this story, I took out the space and submitted the city name as AnnArbor.  (I think CamelCasing your city’s name should be the first step towards establishing the city as a hub for new technology – are you listening, SanFrancisco, SanJose and RaleighDurham?)  And sure enough, here’s what came the other day: