RE: H1 elements should be used for titling the web site and sub page information of a HTML/xhthml based web resource

SC 2.4.2 requires page titles that describe topic or purpose. So the focus is merely the title element. No reference to headings.
I agree title should say the website's name and then contain something that describes topic of the specific page.But this is a branding issue and cannot be a technique sufficient or advisory ... sometimes the logo placed right at the page top (first element in BODY) says what the website's name is. Then authors may prefer to drop it from title element. In that case the title may contain major section of website + reference to particular page's topic:
e.g. Careers - Fresh college graduates


I do not agree that the  title element should be repeated in H1 element.  Continuing the example above, the h1 (main content) could begin with: " We  (or org's name) offer (s) an rewarding career for fresh college graduates"
i.e. something different from title element and yet something that is tied to topic of page.
Some authors dislike repetition as do some users.
Yet some authors may choose to have an h1 that is identical to title. Fine. That is author's and prerogative that may be aligned with site's design specs. Then the overriding requirement is to be consistent (again not accessibility requirement but just good design).  
I also do not agree that there should be no more than 2 h1 elements and at least one h1 element on a page. This is entirely up to page' content and structure. TThere could be zero to any number. 
Overall in the matter of headings, they should be used consistently across the site and convey hierarchy and structure of content.
Thanks,
Sailesh Panchang





 
--- On Thu, 7/14/11, Gunderson, Jon R <jongund@illinois.edu> wrote:

From: Gunderson, Jon R <jongund@illinois.edu>
Subject: RE: H1 elements should be used for titling the web site and sub  page information of a HTML/xhthml based web resource
To: "Loretta Guarino Reid" <lorettaguarino@google.com>
Cc: "WCAG" <w3c-wai-gl@w3.org>
Date: Thursday, July 14, 2011, 12:23 PM

Loretta,Thank you for your response.Thank you for submitting this technique. The working group has reviewed it and has the following feedback: We do not feel this is a sufficient technique for SC 2.4.2. In the absence of the <title> element, this would not satisfy the success criterion. So at most it would be an advisory technique for SC 2.4.2. It might also be considered an advisory technique for SC 2.4.10. I am not sure what you mean here. My technique requires the use of title and H1 element.  Could you clarify why you think the technique I submitted does not require the title element?See reference on the rules for implementation: http://html.cita.illinois.edu/nav/title/title-rules.php This technique itself contains no content, only references to other resources on the web. The details of the technique need to be included inline, so that the technique stands on its own. Links to other resources can supplement the technique but cannot define it. Is
 this a better example?http://html.cita.illinois.edu/nav/title/title-example.php We feel that many of the recommendations in the referenced sources are over-restrictive. Whether we would include them in a WCAG advisory technique would depend on exactly how the requirements of the technique were defined. My understanding is that the techniques document is informative.  This is a technique we have been using for over 8 years and has wide adoption and a technique that many developers and people with disabilities have found very useful.  Maybe this techniques does not work for everyone in all situations, but shouldn’t there be more than one way  to meet a success criteria, especially if it provides richer information that the current technique? Shouldn’t the techniques document provide people with useful alternatives, let developers choose the ones that work for them and their customers?Jon

Received on Friday, 15 July 2011 01:33:20 UTC