{"id":1134,"date":"2024-06-05T10:20:24","date_gmt":"2024-06-05T10:20:24","guid":{"rendered":"https:\/\/html5accessibility.com\/stuff\/?p=1134"},"modified":"2024-06-05T15:43:09","modified_gmt":"2024-06-05T15:43:09","slug":"doing-my-heading-in","status":"publish","type":"post","link":"https:\/\/html5accessibility.com\/stuff\/2024\/06\/05\/doing-my-heading-in\/","title":{"rendered":"Doing my heading in"},"content":{"rendered":"

\"Beganyito<\/p>\n

Interviewed by Mat Marquis<\/h2>\n

Earlier in 2024 I was approached by Mat Marquis<\/a> to answer some questions on HTML headings. At the time I was only vaguely aware that the interview would become part of a printed Zine<\/a> (pleasant surprise face), published by Mat with profits going to support Trans Lifeline<\/a>.<\/p>\n

So waste no time<\/strong> and buy a copy<\/a> and get to read all the great stuff Mat has gathered and edited, by others including Eric Bailey<\/a> and Heydon Pickering<\/a>.<\/p>\n

\"Multipage<\/p>\n

Q: (Question) Who are you, what\u2019s your whole deal, etc.<\/h3>\n

I consider myself to be a Wanker<\/i> (Whatareya? (You’re A Yob or You’re A Wanker<\/a>) I am also a Web Accessibility Worker<\/a>, have been so for too long (20 odd years). I have also been a Web Standards worker (at W3C) since 2006. I am also now one of 4 directors\/partners in TetraLogical<\/a>, an accessibility consultancy based in the UK, where I have lived for 18 years, although I still identify as an Australian. Outside of my main job I do Web Standards consulting for Vispero\u2122, working with some old chums from Freedom Scientific\u2122, the makers of JAWS\u2122 to help improve<\/a> JAWS support for HTML<\/a>\/ARIA. In my spare time I write stuff<\/a> and I design and sell Web Standards Leisurewear<\/a>.<\/p>\n

Q: Pretend for a moment that I\u2019m a different, worse guy: what do headings have to do with accessibility?<\/h3>\n

Many HTML elements and attributes are mapped to accessibility semantics<\/a> in the browser. For example, <h1><\/code> has a role=heading<\/code> and a property level=1<\/code>. This information is used by assistive technology (AT), such as screen readers, to convey meaning to users aurally<\/a>, just as text size and placement conveys meaning to users who consume the UI visually. AT users find the information useful<\/a> by being able to understand which content is acting as a heading, being able to access the UI structure and navigate by headings.<\/p>\n

Q: So, what happened? How did headings end up so busted in the first place?<\/h3>\n

I think the genesis of the HTML headings fiasco started with the choice of the original standardistas<\/i> to opt for a hard coded level based definition for headings in HTML<\/a>. This worked ok for a while, but as the web developed and HTML started to be used for more complex User Interfaces (UI) and UIs became more dynamic and componentized, the hard coded structural nature of H1-H6<\/code> became a brittle semantic, that caused issues for the new kids. Not that it wasn’t fragile to start with:<\/p>\n

documents should<\/a> not skip levels (for example, from H1<\/code> to H3<\/code>), as converting such documents to other representations is often problematic.<\/p><\/blockquote>\n

Source:<\/strong> HTML 2 –\u00a0 https:\/\/www.w3.org\/MarkUp\/html-spec\/html-spec_5.html#SEC5.4<\/a><\/p>\n

It is also the case that developers don’t understand the fundamentals of HTML semantics or don’t care much about conveying an accurate document structure non visually. So even when HTML headings are used, oftentimes, the heading element used does not match their implied semantics.<\/p>\n

Q: Then HTML5 set out to fix it?<\/h3>\n

I first encountered the HTML outline algorithm at a W3C meeting in 2008. It was in a breakout<\/i> session at TPAC<\/a>. It was being spruiked<\/em> by 2 of the movers and shakers of the burgeoning WHAT WG. In essence the Outline algorithm moved the semantics of a heading level from being derived from a headings name h1-h6<\/code>, to being derived from the nesting level of a heading within sectioning content<\/a>. The obvious issue with this method is that it was never implemented in browsers. Yes the CSS styling was implemented, but the actual exposing of the headings with the level they theoretically represented was not. Thus the W3C HTML5 spec included a warning<\/a> I added to make it clear to developers that the outline algorithm was a fiction.<\/p>\n

\"Warning!<\/p>\n

As at the time there were 2 versions of HTML I also filed an issue<\/a>, in 2015, on the WHATWG HTML spec to add a warning.<\/p>\n

Q: [Seems sensible enough.] What went wrong?<\/h3>\n

I waited<\/a>, and waited<\/a>, and waited some more<\/a>, until 2022 when I realised that unless someone other<\/em> than the editors did the work the WHATWG HTML spec would continue to have a decade old theoretical fiction masquerading as HTML truth. Note by this time the spec wars<\/em> were long over and the only maintained specification was WHATWG HTML. There had been lots of discussion and hand wringing by various Web Standards Celebrities<\/em>, but no actual changes in the spec or implementations of the outline algorithm in user agents. So I decided to do it myself with a Pull Request (PR): replace current outline algorithm with one based on heading levels<\/a>.<\/p>\n

My thinking at the time was that at least if the HTML spec<\/a> reflected some sort of reality, after a decade of misdirection, developers would no longer be misled into thinking that the nesting of headings in sectioning elements actually did anything.<\/p>\n

Note the process of updating the spec was positively facilitated by the WHATWG editing gang at the time.<\/p>\n

Q: Speaking of HTML5, what was wrong with hgroup<\/code> \u2014 it makes sense on paper, yeah? \u201cMade?\u201d<\/h3>\n

During my time as an editor of the HTML5 spec (at W3C) I ended up removing <hgroup><\/code> as what it represented<\/a> was meaningless as it derived its semantics from a fiction and in reality was nothing more than a styling hook (think <div><\/code>) that lead developers to use h1-h6<\/code> elements as subheadings, when they did not work as such. I did try to work with the editors of the WHATWG HTML spec at the time, to make <hgroup><\/code> more meaningful, to no avail. It remained in the WHATWG HTML so when I came to do the PR to update the outline algorithm, rather than re-litigate the uselessness of <hgroup><\/code> I decided to recast hgroup<\/code><\/a> in a form that mitigated its negative effects.<\/p>\n

Q: Where do you land on this proposed headingstart<\/code> attribute?<\/h3>\n

To be honest I have pretty much tuned out of the discussion, I find my attention span is fairly limited for this particular rabbit hole and prefer to work on the myriad other web standards opportunities that present themselves. Having read through the issue<\/a> it seems reasonable and the right heads are involved in the discussion. If it gets implemented interoperably<\/i>, bravo!!<\/p>\n

Q: While we wait to see how that plays out, what should we be doing right now?<\/h3>\n

Use h1-h6<\/code> as described<\/a> in the HTML spec. Also have a read of Subheadings, subtitles, alternative titles and taglines in HTML<\/a><\/p>\n