Posted over 1 year ago
tlnt.co/p/1vt

Ready for some controversy? Luke Stevens is stirring some up over the benefits of HTML5's "semantic" tags such as header and nav, particularly for assistive-device users. This is an excerpt of a longer piece, which probably goes on to examine using these new tags with ARIA role attributes for compromise.

You might also like

accessifyhtml5.js
The Secret to the Page Flip in HTML5/Canvas for Windows8 and iOS
The Making of Fastbook: An HTML5 Love Story

Comments

Default_thumb
Dave Everitt

Some of Luke Stevens' polemic will undoubtedly help sales of the book (it worked for me—added to my wishlist) and his page of links is a good one-stop-shop for keeping up with HTML5. Derek Featherstone's Sitepoint article Real World Accessibility is a less Tarantino-like article that focusses on adding ARIA attributes to address the fact that assistive tech hasn't yet caught up with HTML5.

Later:

Just finished reading the article and laughed when I saw the This is wrong. Don't do this image. When I first used HTML5 that's exactly what I did!

But it's a great article and some of the best points were about document structure and screen readers e.g.:

"The spec says <header> and <footer> elements define areas within a section, but do not define sections themselves, and so won’t show up in a document outline."

I think this really sums up the issue:

"the community is trying to implement HTML5 markup in a way that doesn’t have much relation to the actual HTML5 spec".

I'm guilty as charged, despite reading up on the HTML5 spec and thinking I understood.

over 1 year ago   Like_icon 0 likes  

Talentopoly Newsletter

A once-weekly round-up of the best programming and design posts.

Join 2050+ subscribers

We will never spam or share your email address. Easily unsubscribe

Liked_post_header
15b2f7b_speck Jared_gaze_speck Default_speck