Microformats: Prefering machines over people
Anybody ever took a look at the Datetime Design Pattern at Microformats.org (via Georg Bauer (German))? It goes like this:
<abbr class="foo" title="YYYY-MM-DDTHH:MM:SS+ZZ:ZZ">Date Time</abbr>
I think this is a misuse of the abbrevation tag - and worse: it's completly ignoring user experience. Most of nowadays browsers display the text of the title attribut when you hover over the abbrevation. Now imaging a user browsing your microformatted page. When he hovers over a date like - say - May 4th 1970, which is my birthday, he'll see a tooltip stating "1970-05-04T18:10:52+01:00". Doh!
Not to tell that screenreaders usually read the abbrevation's title. So, a screenreader would read "One Nine Seven Zero Minus Zero Five Minus Zero Four T One Eight Colon..." Really well done, you microformat people.
Like Colin Lieberman writes on A List Apart:
The point of including expanded forms of abbreviations is to make sure that users can access those forms if needed. The value of the abbr element lies in its ability to tell screen readers what they should read (thus improving the flow of spoken text), while also providing additional useful information to visual users with learning or cognitive disabilities (or those coping with language barriers). The assertion that abbr is structural is misguided, as the point of the tag is the content of its title attribute.
He's right. Abbrevation is not structural. Even it it once was intended to be, in real life it isn't. It seems, this has been forgotten by the microformat astronauts.
Comment by ryan king
January 18, 2006 - 23:58
So, assuming <abbr> is inappropriate for publishing human and machine values, how should it be done?
Oh, and I prefer the term 'microformats agua-nauts.'