I’m slightly late with this, but I was happy to see that Opera have launched their first Web Standards Curriculum for teaching best practice in client-side development. With developers in the Netherlands setting up what could well be the world’s first front-end professional guild, and a full British Standard for accessibility in the works, the signs are promising that we’re entering into a new phase of professionalism in web development.
One of the hardest things about Microformats is explaining their benefits to people. You can say “It’s a standardised format of marking-up content, which is both human and machine readable!” until you’re blue in the face, but until you can show people a practical benefit they usually remain unmoved.
Luckily there are a few tools out there which will help you show off the benefits of using Microformats, and involve little work from you.
Read the full article
I’ve been doing a bit of thinking recently.
I’ve been thinking about HTML 5 and the new semantic sectioning elements it proposes to introduce: header, footer, section, article, nav and aside.
I’ve also been thinking about the way microformats use data format standards and reserved class and id values to organise content.
Then thinking about this 2005 research into reused class names, which shows that, probably mostly unconsciously, website makers were already using the proposed HTML 5 elements as class names to organise their data.
Read the full article
[We work] with email client developers and the design community to improve web standards support and accessibility in email.
The Email Standards Project
It’s fair to say that a large chunk of the web industry now understands the importance of standards; from browser makers to designer/developers, we’ve taken on board the years of evangelising by early adopters and in turn it informs everything we do (I sincerely hope I’m speaking for the majority here).
But there’s one area of web development where standards break down; where we place elements where they’re not supposed to go, where we (whisper it) use tables for layout. Not because we want to, but because we have to. That area is, of course, HTML emails.
Read the full article