Re: Only one h1 per page?

Sorry for my answere: I have a similar discussion in the development of a call client, and the heading is 100 procent similar. I therefore replied too fast, sorry again for sending this wrong!

Få Outlook for iOS<https://aka.ms/o0ukef>

________________________________
Fra: Morten Tollefsen <morten@medialt.no>
Sendt: mandag, desember 10, 2018 4:23 pm
Til: Michael Wayne Harris; Katie Haritos-Shea
Kopi: Steven Faulkner; raquel.moreno.carmena@gmail.com; WAI Interest Group
Emne: SV: Only one h1 per page?

This is a good example on what we’re talking about: humans not standard answers for everything regarding accessibility. This is comparable to asking which of 5 logos people prefere, you’ll get different answers.

As I said: I havn’t strong opinions on this, but in the Puzzel app I do believe h1 is most efficient and require as little mental thinking as possible. It is just to press 1 very fast to jump from heading to heading, not 1 then 2 or 3 etc. h do the same of course, but stop on all headings, and I suppose some widgets have subheadings. So, not a standard o follow here I am afraid, but if I had implemented this to my selves, I’d used h1.

Mvh: Morten Tollefsen
Sjekk SmartJa.no<https://smartja.no/>
90899305, www.medialt.no<http://www.medialt.no/>

Fra: Michael Wayne Harris <michaelwayneharris87@gmail.com>
Sendt: mandag 10. desember 2018 15.47
Til: Katie Haritos-Shea <ryladog@gmail.com>
Kopi: Steven Faulkner <faulkner.steve@gmail.com>; raquel.moreno.carmena@gmail.com; WAI Interest Group <w3c-wai-ig@w3.org>
Emne: Re: Only one h1 per page?

One reference point to consider: WebAIM’s recent screen teaser survey has some information about user preferences. “Improper headings” ranks as one of the most common frustrations, though I don’t think they define what “improper” means. https://webaim.org/projects/screenreadersurvey7/

I take that to be suggesting that heading nesting is a substantial enough usability issue that it warrants treating as a bug. WCAG conformance strikes me as a moot issue, practically speaking.

Sent from my iPhone

On Dec 10, 2018, at 9:15 AM, Katie Haritos-Shea <ryladog@gmail.com<mailto:ryladog@gmail.com>> wrote:
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<tel:703-371-5545> | ryladog@gmail.com<mailto: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<mailto: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/
--

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<mailto: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