Being used to the fairly sensible ways of Finnish trains and buses, the policies stated on the American Greyhound website seem quite odd:
While the ticket is schedule specific, it may be used for any schedule on the correct date for the origin and destination purchased.
Err, what? So they’re basically saying that the ticket is only for a specific schedule, and then saying it isn’t. Well, at least it’s cheap.
Solid, semantic and accessible HTML markup matters. When most people look at a web page, it doesn’t make much difference to them whether headings are coded with proper <h1> and <h1> tags or <span style="font-size: 20px">. Still, for someone using a screen reader, not to mention search engines and feed readers, it can make all the difference in making sense of a document. Luckily this specific issue is now rare, but in a world of plugins and cool themes that generate semi-adequate markup, we’re often not using HTML and CSS to their full potential in building solid, accessible and search engine friendly sites.
By we I mean me of course. WordPress is awesome, and it’s one of the few CMS’s around that has committed to accessibility on the admin end (I’m not saying it couldn’t be improved). Unfortunately tight schedules and the very fact that its so easy to whip up a site using a few plugins and occasionally ready-made themes means its very tempting to be lazy.
So here goes: I hereby promise to continue to build usable sites, with a renewed commitment to good semantic and accessible markup. Because the web should be for everyone (and there’s nothing like some sweet, elegant HTML is there?).
Trying out the new Quick Photo feature in WordPress for iOS 2.8… messy I know.
A panoramic view, taken from our balcony.
This wooden-framed TV had somehow found its way into the woods nearby. How does a TV end up in a place like this?
