WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Multiple H1 tags in an HTML5 web page

for

From: Greg Gamble
Date: Mar 10, 2014 2:16PM

Well, considering the cats already out of the bag ... If the relevant content in a section deserves an H1, as per the current specification (spec), how would this be a problem for a user?

All I've heard is that it's not correct. OK, fine ... but why is it not correct? And I'm not talking about a missing "outlining algorithm " or a unknown bug ... I'm talking about a user with current technology.

What difficulties, if any, would they have navigating a page? Is there anyone on this list, who is a user of AT , that can give me first hand knowledge?

I try to create pages that work for all users, and that includes users who are accessing my pages via AT. If doing something by a current spec causes problems for the majority of the users, I'm not going to follow that spec. Conversely, if a spec is deemed by some as incorrect, but works ... I'm going to use it.

Just trying to do what's right for my end users.

Greg


-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Steve Faulkner
Sent: Monday, March 10, 2014 12:51 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Multiple H1 tags in an HTML5 web page

--

Regards

SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>;


On 10 March 2014 19:29, Jukka K. Korpela < <EMAIL REMOVED> > wrote:

> 2014-03-10 21:12, Steve Faulkner wrote:
>
> As i pointed out previously the HTML5 spec strongly encourages using
>> headings as per their outline depth.
>>
>
> I'm not sure I have quite followed the discussion, but at
> http://www.w3.org/TR/html5/sections.html#the-h1,-h2,-h3,-
> h4,-h5,-and-h6-elements
> the W3C HTML5 CR presents two approaches, one using heading elements
> by nesting depth and one using <h1> inside <section>, and adds:
> "Authors might prefer the former style for its terseness, or the
> latter style for its convenience in the face of heavy editing; which
> is best is purely an issue of preferred authoring style." I cannot see
> this as encourageing, even mildly, the use of the former approach
> (which is surely much more practical).


thanks for pointing this out, it needs to be reworked I have filed a bug
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24992


>
>
> It does not encourage authors to use
>> H1s to represent anything other than a H1, if that is unclear it is a
>> bug and needs to be fixed.
>>
>
> Well, the question is what an H1 is. The old definition is simple and
> understandable: it is a 1st level heading in a document. The HTML5
> definition is less simple, but consistent as such: it is a 1st level
> heading relative to something defined by HTML5
>
> Personally, I don't like this modern style of speaking about "bugs".
> Long ago, I learned that a bug was a software error or, more exactly,
> failure to work by a specification. A specification, by this
> definition, cannot have bugs; it can have inconsistencies or just
> something that someone regards as wrong.
>

this is a term the editors of the HTML (including myself) spec use refer to aspects of the advice and requirements on implementers and authors in the spec that are at issue.

>
> In this case, I don't think it's a matter of "bugs" in any useful sense.
> People may disagree on what a specification should say. We can debate
> over such things, rationally or irrationally, but it is confusing, and
> probably an accessibility issue too, to cognitively challenged people
> at least, to call differing opinions "bugs".
>

Call them whatever suits you, I call them bugs and file bugs on the issues, when a resolution involves a change in what the specification advises or requires i consider that a bug has been resolved.

>
> Yucca
>
>
>
> > > list messages to <EMAIL REMOVED>
>