Comments on: Headings in HTML 5 and accessibility

By: Some links for light reading (10/2/09) « Max Design

Some links for light reading (10/2/09) « Max Design — Fri, 29 Jan 2010 11:19:03 +0000

[...] Headings in HTML 5 and accessibility [...]

By: Bruce

Bruce — Mon, 25 Jan 2010 20:15:52 +0000

well spotted, Andy. Amended; thanks!

By: Andy Mabbett

Andy Mabbett — Mon, 25 Jan 2010 15:59:58 +0000

“from h2 to h3 with no intervening h4, for example”

Shome mishtake? I think you mean:

“from h2 to h4 with no intervening h3, for example”.

By: Wait till I come! » The Table of Contents script – my old nemesis

Wait till I come! » The Table of Contents script – my old nemesis — Wed, 06 Jan 2010 13:57:28 +0000

[...] they apply to as child elements (XHTML2 was proposing that and HTML5 has it to a degree – Bruce Lawson write a nice post about this and there’s also a pretty nifty HTML5 outliner [...]

By: davux

davux — Thu, 24 Dec 2009 02:53:22 +0000

As the HTML 5 spec clarifies, it’s perfectly OK to use, say, a h2 as first-level title of its own section. Since there’s no h1, the outline algorithm will treat it as a first-level header. Yet, in “section”-unaware devices, the whole page structure will stay consistent and understandable.

So this approach is perfect for everyone, except the light frustration one can have as an author to type an h2 without prior h1 (although this is semantically unambiguous, as I just mentioned). I personally think I’ll be able to deal with this frustration, and this approach is a nice way to combine semantically correct code and consideration to HTML 5 unaware devices.

At this point, it’s also important to take into account that e.g. Braille readers are pretty expensive. Moreover, as you pointed out, some vendors are not very responsive, so maybe they won’t release compliant devices anytime soon. Let’s change our first-level (in a given section) h2’s to h1’s later, whenever everyone’s ready, it won’t be a lot of work anyway.

By: Paul

Paul — Thu, 12 Feb 2009 13:36:49 +0000

@Rijk I am the designer of the H1 Debate, and wanted to emphasise the poll first and the comments second, hence setting the opacity at 50%. If you hover over a tweet, it’s opacity increases to 100%.

Although the poll numbers are important, the comments make are the key to the debate. Each tweet is a vote after all, and I have had some great feedback from some of the Webs’ most respected designers.