W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2017

Re: WCAG 2.4.6 query in relation to headers within frames.

From: Userite <richard@userite.com>
Date: Mon, 26 Jun 2017 17:55:27 +0100
Message-ID: <94C1A32E5163497BBCCED5CD097D85E2@RichardPC>
To: "Herin Hentry" <herinhentry@gmail.com>, "Sean Murphy \(seanmmur\)" <seanmmur@cisco.com>
Cc: "w3c WAI List" <w3c-wai-ig@w3.org>
Hi Herin and Sean,

Each HTML document should only have one top level heading (heading 1) in the same way that it only has one title in the head section. The purpose of the top level heading is to tell the user what the *page* is about overall.  As the user arrives at the page (especially blind users) this heading is important because it tells them what the PAGE is about and, if that is not of interest then the user can quickly return to something else without having to waste time searching the page.  If the page contains a series of articles then this top level heading might say “Series of articles about xxx” with each article starting with a level 2 heading.

Headings, and other semantic elements, are vital for assistive technology to understand the page and to present it in a meaningful way to the user.

I am sorry, but headings are mandatory for web pages.

With regard to Sean’s initial enquiry regarding iframes then yes each iframe *might* have a level 1 heading because each iframe loads a different document which may be used elsewhere where a H1 is required. The initial page must also have a top level heading that covers the purpose of the various documents being loaded via the iframes. 

HOWEVER please note that frames are terrible for accessibility and need to be used with care. Make sure you use the iframe title attribute. Also do not lock keyboard users inside an iframe !!

Regards
Richard
Technical Manager
www.userite.com


From: Herin Hentry 
Sent: Monday, June 26, 2017 1:24 PM
To: Sean Murphy (seanmmur) 
Cc: w3c WAI List 
Subject: Re: WCAG 2.4.6 query in relation to headers within frames.

Hi Sean, 

My understanding is - Headings are not mandatory requirements for WCAG. If headings are present they should convey the structure of content in the page. WCAG does not prohibit using multiple H1s. I personally do not prefer multiple H1s. But, if any page needs multiple headings, & as long as the Outline of the page clearly conveys the information and relationship, it's not a failure.


If there are multiple articles displayed on the same page and each has it's own heading and importance, multiple H1should be fine.

Also an interesting read I found here
https://webdesign.tutsplus.com/articles/the-truth-about-multiple-h1-tags-in-the-html5-era--webdesign-16824


Would like to know others interpretation of 2.4.6 as well.

Regards,
Herin


On Fri, Jun 23, 2017 at 4:19 PM, Sean Murphy (seanmmur) <seanmmur@cisco.com> wrote:

  All,



  In relation to 2.4.6, if the page has multiple iFrames. Is the heading order specific to the iFrame or the whole page regardless of the iFrames? For example:



  Main page

  … some elements …

  ** Iframe1 *** 

  Heading 1

  *** iframe ends 

  ** Iframe2 *** 

  Heading 1

  *** iframe ends 

  ** Iframe3 *** 

  Heading 1

  *** iframe ends 












                   
             
             
                   Sean Murphy

                                ENGINEER.CUSTOMER SUPPORT

                                seanmmur@cisco.com

                                Tel: +61 2 8446 7751




                               

                               
                               

                               
                               
                          Cisco Systems, Inc.

                                The Forum 201 Pacific Highway

                                ST LEONARDS

                                2065

                                Australia

                                cisco.com
                               
                         
                         

                                Think before you print.
                               
                                This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

                                Please click here for Company Registration Information.
                               
                         
                    
             
       









image001.png
(image/png attachment: image001.png)

image002.gif
(image/gif attachment: image002.gif)

Received on Monday, 26 June 2017 16:56:00 UTC

This archive was generated by hypermail 2.3.1 : Monday, 26 June 2017 16:56:04 UTC