W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > December 2018

Re: Only one h1 per page?

From: Katie Haritos-Shea <ryladog@gmail.com>
Date: Mon, 10 Dec 2018 09:58:09 -0500
Message-ID: <CAEy-OxHVMzzPKt=q_APkASrOkrHu07M_YrY=LtAYS08TPCbXVg@mail.gmail.com>
To: Phill Jenkins <pjenkins@us.ibm.com>
Cc: Steven Faulkner <faulkner.steve@gmail.com>, raquel.moreno.carmena@gmail.com, WAI Interest Group <w3c-wai-ig@w3.org>, public-comments-wcag20@w3.org
Phill,

It is indeed a best practice - not a specific SC.

** katie **

*Katie Haritos-Shea*


*Principal ICT Accessibility Architect, Vice President of Accessibility at
EverFi, **Board Member and W3C Advisory Committee Rep for Knowbility *

*WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy,* *IAAP CPACC+WAS = *
*CPWA* <http://www.accessibilityassociation.org/cpwacertificants>

*Cell: **703-371-5545 <703-371-5545>** |* *ryladog@gmail.com
<ryladog@gmail.com>* *| **Oakton, VA **|* *LinkedIn Profile
<http://www.linkedin.com/in/katieharitosshea/>*

People may forget exactly what it was that you said or did, but they will
never forget how you made them feel.......

Our scars remind us of where we have been........they do not have to
dictate where we are going.




On Mon, Dec 10, 2018 at 9:51 AM Phill Jenkins <pjenkins@us.ibm.com> wrote:

> Katie and working group,
> if we did indeed "moved back to the one-H1, then H2, etc."
> then the sufficient techniques and failure techniques will need another
> review and edit.  For example, https://www.w3.org/TR/WCAG20-TECHS/H42.html
> has as *Example 2: Headings in a 3-column layout*
> . . . in the example, the layout could be presented with the first
> heading in each column at the same logical level (such as an h1),
>
> I do not believe there ever was guidance or agreement that only one-h1 was
> required always and everywhere, or it would have been a Success Criterion
> by itself.  I believe it is more of a guidance or best practice that most
> of the time and in many places it is recommended to have only one h1.
> George's example of an e-pub ( web site) of a book with chapters where
> every chapter heading is tagged (programmatically identified) as an h1 is a
> good example.
> ___________
> Regards,
> Phill Jenkins
> Accessibility Executive
> IBM Accessibility
> linkedin.com/in/philljenkins/ <https://www.linkedin.com/in/philljenkins/>
> www.ibm.com/able
> <http://ageandability.com/>twitter.com/IBMAccess
> ageandability.com
>
>
>
>
> From:        Katie Haritos-Shea <ryladog@gmail.com>
> To:        Steven Faulkner <faulkner.steve@gmail.com>
> Cc:        raquel.moreno.carmena@gmail.com, WAI Interest Group <
> w3c-wai-ig@w3.org>
> Date:        12/10/2018 08:21 AM
> Subject:        Re: Only one h1 per page?
> ------------------------------
>
>
>
> Raquel,
>
> Thanks Steve! The long and short of that article is that HTML 5 tried to
> implements new outline rules but it was never really implemented by the
> browsers - therefore - we moved back to the one-H1, then H2, etc.
>
> ** katie **
>
> *Katie Haritos-Shea *
>
>
> *Principal ICT Accessibility Architect, Vice President of Accessibility at
> EverFi, Board Member and W3C Advisory Committee Rep for Knowbility *
>
> *WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy, **IAAP CPACC+WAS
> = **CPWA* <http://www.accessibilityassociation.org/cpwacertificants>
>
> *Cell: **703-371-5545* <703-371-5545> *|* *ryladog@gmail.com*
> <ryladog@gmail.com> *|* *Oakton, VA **|* *LinkedIn Profile*
> <http://www.linkedin.com/in/katieharitosshea/>
>
>
> People may forget exactly what it was that you said or did, but they will
> never forget how you made them feel.......
>
> Our scars remind us of where we have been........they do not have to
> dictate where we are going.
>
>
>
>
> On Mon, Dec 10, 2018 at 8:42 AM Steve Faulkner <*faulkner.steve@gmail.com*
> <faulkner.steve@gmail.com>> wrote:
> hi Raquel,
>
> this may be helpful in regards to practicality of hading level usage
> *http://html5doctor.com/computer-says-no-to-html5-document-outline/*
> <http://html5doctor.com/computer-says-no-to-html5-document-outline/>
> --
>
> Regards
>
> SteveF
> *Current Standards Work @W3C*
> <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>
>
>
> On Mon, 10 Dec 2018 at 13:31, Raquel <*raquel.moreno.carmena@gmail.com*
> <raquel.moreno.carmena@gmail.com>> wrote:
> Hi,
> Recently, I made a talk about accessibility. I needed to talk about what
> I'd learnt after making a lot of mistakes, because of a lack of knowledge.
> I had a lack of empathy, because a lack of information/knowledge..
> I read a lot of documentation about accessibility and I found the
> recommendation about "only one h1 per page" in several resources, but now I
> realize that W3C doesn't include it explicitly.
> Now, I'm worry about it, because I also told it in my talk. I added a
> disclaimer at the beginning of the talk: I'm not a specialist on
> accessibility. But I would like to fix my errors if I told something wrong.
> I've continued reading about it and I've found several articles (not in
> WAI). They explain that it's a recommendation for previous versions of
> HTML, not for HTML5. You don't have to worry about the order of the rest of
> the headings if you add a <section>or <article>. In other words, you can
> start by h1 again in an <article>, for example. I wonder if assistive
> technology is ready for it.
> Please, where can I find more information about this issue? Is it a valid
> recommendation? Does this recommendation make sense with HTML5?
> I'll write a post about my talk very soon, so I can take that opportunity
> to clarify this issue. I can also fix my shared slides.
> Thanks in advance for your time!
> Best regards,
> Raquel
>
>
>
Received on Monday, 10 December 2018 14:58:45 UTC

This archive was generated by hypermail 2.3.1 : Monday, 10 December 2018 14:58:46 UTC