Link: The truth about structuring an HTML5 page

I just read a fascinating article by Luke Stevens. It’s an excerpt from his book, The Truth About HTML5, and is over on .net Magazine. It’s pretty abrasive, and may have some people drama in it, but his criticism of HTML5 page structuring elements and how they made it into the spec was really interesting to me.

He goes into detail about ARIA (basically the role attribute) and also the importance of different HTML elements for screen readers / accessibility. I’ve never seen things explained quite like he did in the post. The statistical importance of h1-h6 elements on existing readers, and the lack of excitement from screen reader vendors about HTML5 were particularly enlightening.

He clearly doesn’t sing the same tune as most web professionals on the benefits of HTML5 elements as we’ve learned them. And he gives detailed reasons why. Also, not surprisingly, he details that many blogs and even some books are providing information that may not really be best practice. Shocking, I know.

It’s a great read. Probably the most important web-related article I’ve read in months. Give it a go.

3 thoughts on “Link: The truth about structuring an HTML5 page

  1. Thank you!
    I hate html5. Now I can explain why 🙂
    (I used to think that I’m dumb not to understand it)
    Eg: in singular post, should I remove header tag from the header and move it to post title or use twi ‘header’?
    Do I need to wrap post title and the content with ‘article’ or just the content.
    If I add ads in sidebar, and use aside, it’s not aside.
    If I use category widget in sidebar, do I need to use ‘nav’? related posts: a section, or nav, or both?

Leave a Reply