W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2011

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

From: Gunderson, Jon R <jongund@illinois.edu>
Date: Thu, 14 Jul 2011 11:23:34 -0500
To: Loretta Guarino Reid <lorettaguarino@google.com>
CC: WCAG <w3c-wai-gl@w3.org>
Message-ID: <A37F89DE961B7E4594F2AB47054DAE4E1AFC6FE58C@DSMAILBOX2.ad.uiuc.edu>

Thank you for your response.

Thank you for submitting this technique. The working group has reviewed it and has the following feedback:

 1.  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

 1.  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?

 1.  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?
Received on Thursday, 14 July 2011 16:24:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:08 UTC