Archive for the ‘Accessibility’ Category

The main element

Recently, main was formally added to the W3C HTML specification. Now that the dust has settled, it’s about time we dive in to find out where and when it’s appropriate to use main. Let’s get started.

Video Subtitling and WebVTT

We’ve been able to play video in the browser without a plugin for a couple of years now, and whilst there are still some codec annoyances, things appear to have settled down on the video front. The next step is adding resources to the video to make it more accessible and provide more options to the viewer.

Goodbye time, datetime, and pubdate. Hello data and value.

While HTML5 is stable and being implemented we’re still not past losing (or gaining) an element, as demonstrated by the removal of <time> and the addition of <data>. Rather than jumping into the ensuing brouhaha, we’ve spent some time figuring out what this really means. In short? Well… it’s complicated.

The time element (and microformats)

Please note that since this was written, <time>, datetime have been made more powerful, so this article is obsolete. Doctor Bruce has the low-down in his blogpost The best of <time>s. Microformats are a way of adding extra semantic information to a webpage using HTML classes — information like an event’s date and time, a […]

Your Questions Answered #4

Here we go with another post rounding up your HTML5 questions and sharing the answers with the world. We cover a wide range of topics this time, inlcluding ARIA, storage, offline capabilities, and document outlines, so read on to find the answers. We also want to know what areas of HTML5 you’d like us to […]

The section element

We doctors are a bunch of chums using HTML5 and writing about how we do it. And we realise that we’ve been using the section element incorrectly all this time. Sorry.

Accessibility & Native Drag and Drop

A few days before my native drag and drop article came out Gez Lemon wrote about accessibility in drag and drop, and touched on HTML 5. I then promised to look at implementing accessibility with native drag and drop, and here’s my findings.