W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2014

RE: Hiding heading level ones

From: Gunderson, Jon R <jongund@illinois.edu>
Date: Tue, 25 Nov 2014 19:30:52 +0000
To: Laura Carlson <lcarlson@d.umn.edu>, Sailesh Panchang <sailesh.panchang@deque.com>
CC: w3c-wai-ig <w3c-wai-ig@w3.org>
Message-ID: <46739F12637CC94E82F75FF874E4A147365E83DC@CITESMBX6.ad.uillinois.edu>
Laura,

The design pattern I use for TITLE and H1 elements and note I would also include the MAIN[role="main"] element.

TITLE element content provides both website and sub-page information

H1 provides only sub-page information

<head>
  <title>Disability Services: Accommodation Services</title>
  ....
</head>
<body>

  .....

 <main role="main">
  <h1>Accommodation Services</h1>
.....
</main>

In terms of meeting 2.4.2 is really up to the individual unless your organization has its established its own technique requirements for meeting SC 2.4.2 and other success criteria.  WCAG 2.0 only standardizes the accessibility requirements, not the techniques to meet the success criteria.   This was done to allow developers to adapt to changes in technology and accessibility techniques without having to change WCAG 2.0. 

Hope this helps,
Jon
   

-----Original Message-----
From: Laura Carlson [mailto:lcarlson@d.umn.edu] 
Sent: Tuesday, November 25, 2014 9:43 AM
To: Sailesh Panchang
Cc: w3c-wai-ig
Subject: Re: Hiding heading level ones

Hi Sailesh,

Thank you very much for your reply. The page would have a <title> element. It would not have a visible <h1>. Would you consider not having a visible <h1> a failure of  SC 2.4.2?

Thanks.

Best regards,
Laura

On 11/25/14, Sailesh Panchang <sailesh.panchang@deque.com> wrote:
> Laura,
> True, SR users will have some h1 text to read but if the page does not 
> have a page title it will fail SC 2.4.2. Non-SR users will not see a 
> page title.
> Yes in some situations one may have an h1 and no content before the 
> next heading. But that is content that is available to all.
> Sailesh
>
>
> On 11/25/14, Laura Carlson <lcarlson@d.umn.edu> wrote:
>> Hi all,
>>
>> A Web developer in our marketing department has asked if the 
>> following markup, which is meant for use in Drupal themes and 
>> Dreamweaver templates throughout the organization, would meet WCAG AA 
>> with the notion that screen readers will be able to receive a good 
>> heading for the page and some snappy marketing text could go in the <h2>.
>>
>> <style>
>> .hidden {
>> position: absolute;
>> top: -9999px;
>> left: -9999px;
>> }
>> </style>
>>
>> <h1 class="hidden">Page Title</h1>
>>  <!-- No other content -->
>> <h2>THIS IS WHERE THE DOCUMENT HEADING GOES.</h2>
>>
>> Thoughts on that markup and WCAG AA?
>>
>> I stated that if he hides the <h1> he would be locking out people 
>> with cognitive and learning disabilities who would benefit from the 
>> ability to identify content by a visible <h1>. My advice to him was 
>> to keep the <h1> visible and intuitively easy to understand.
>>
>> I have cited Info and Relationships Success Criteria 1.3.1, "When 
>> such relationships are perceivable to one set of users, those 
>> relationships can be made to be perceivable to all."
>>
>> In addition I have pointed him to:
>> http://www.d.umn.edu/itss/training/online/structure/coding/index.html
>> #writing
>>
>> Other thoughts?
>>
>> Thank you.
>>
>> Best Regards,
>> Laura
>>
>> --
>> Laura L. Carlson
>> Information Technology Systems and Services University of Minnesota 
>> Duluth Duluth, MN U.S.A. 55812-3009 
>> http://www.d.umn.edu/itss/training/online/webdesign/
>>
>>
>


--
Laura L. Carlson
Information Technology Systems and Services University of Minnesota Duluth Duluth, MN U.S.A. 55812-3009 http://www.d.umn.edu/itss/training/online/webdesign/
Received on Tuesday, 25 November 2014 19:34:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:53 UTC