Re: Hiding heading level ones

Hi Sailesh,

I'm so sorry that I wasn't clear in my first message. Apologies. Thank
you for your followup message.

Over use of off-screen method  is what I fear too.

Best Regards,
Laura

On 11/25/14, Sailesh Panchang <sailesh.panchang@deque.com> wrote:
> Laura,
> If there's a valid title element then it does not fail 2.4.2. Your
> email suggested the h1 contains an off-screen page title, so I thought
> it was the intent to not have a visible title element.
> If the page structure and UI design requires an h1 and an h2 with no
> content in between, that's fine. I'd only caution on over use of
> off-screen method ... how is it helping accessibility here? Pages do
> not have  to have an h1 ... if that is followed consistently across
> the site. Main content can begin with h2 if one chooses and it is
> consistent on the site.
> Sailesh
>
> On 11/25/14, Laura Carlson <lcarlson@d.umn.edu> wrote:
>> 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/
>>
>


-- 
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 20:50:32 UTC