[wp-meta] [Making WordPress.org] #4112: Proposal to change the headings hierarchy in the Home page

[Making WordPress.org]

#4112: Proposal to change the headings hierarchy in the Home page
--------------------------------+---------------------
 Reporter:  afercia             |       Owner:  (none)
     Type:  defect              |      Status:  new
 Priority:  normal              |   Milestone:
Component:  General             |  Resolution:
 Keywords:  headings-hierarchy  |
--------------------------------+---------------------

Comment (by afercia):

 > is it better to have 2 h1 tags on a page, or no h1.

 None of the two options is ideal. There should be one H1, which identifies
 the main topic of the document.


 > on Rosetta sites, the heading is the h1 and the Locale is a h2 (which it
 shouldn't be most likely).
 Yup, that isn't ideal (see attached screenshot). Having the Locale in the
 headings hierarchy doesn't make much sense. Also: headings should be used
 to identify ''sections'' of content. Using headings as "subtitles"
 directly after another heading isn't so appropriate. Subtitles are not
 headings: they don't introduce new sections of content.


 Why a correct headings hierarchy matters for assistive technology users:
 https://make.wordpress.org/core/2015/10/28/headings-hierarchy-changes-in-
 the-admin-screens/
 > Putting it simply, one of the first things screen reader users do in a
 web page to find relevant content is to press the 1 key on their keyboard
 to jump to the first `<h1>` heading and then they will try the key 2 to
 find the `<h2>` headings and so on. Thus, it’s extremely important for
 WordPress to provide a correct headings hierarchy, ensuring no headings
 levels are skipped.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4112#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org