W3C home > Mailing lists > Public > public-webplatform@w3.org > December 2012

Re: That annoying duplicate <h1> issue

From: Michael Del Tito <mdeltito@gmail.com>
Date: Tue, 18 Dec 2012 09:08:08 -0500
Message-ID: <CAEChftXdtWAvjCM6xqmCpY+rmbhFd_r246VwYRQUGduTGG29ZQ@mail.gmail.com>
To: Jonathan Garbee <jonathan@garbee.me>
Cc: public-webplatform@w3.org
It would probably make more sense to leave those headings accessible to
screen readers by using the visuallyhidden technique which is also found in
h5bp:

http://css-tricks.com/places-its-tempting-to-use-display-none-but-dont/

This may also be better for SEO since I believe Google dislikes hidden H1
elements. Not that this really matters that much in the long term, but it
is an easy drop in replacement for display: none for the time being until
the headings are removed.
On Dec 18, 2012 8:52 AM, "Jonathan Garbee" <jonathan@garbee.me> wrote:

>  Multiple H1 is not bad for SEO or "semantics" if used properly. Further,
> forget about SEO completely; at this point we should focus on getting
> content updated and formatted properly and not worry about stupid SEO. The
> point is it is just annoying to have multiple title headings. For now,
> display none will work until we figure out how to have the pages generated
> properly.
>
> -Garbee
>
> On 12/18/2012 8:08 AM, PhistucK wrote:
>
> Duplicate <h1> is really bad semantically and due to this fact, it is also
> really bad for SEO reasons.
> This must be removed from the HTML itself, not only dynamically/using CSS.
>
>  ☆*PhistucK*
>
>
>
> On Tue, Dec 18, 2012 at 1:35 PM, Chris Mills <cmills@opera.com> wrote:
>
>> I was just thinking about that annoying issue we've got, where we have
>> duplicate <h1>s on a page: one of my personal pet peeves.
>>
>> The auto generated <h1> has got a class of firstHeading (and an ID the
>> same, for that matter). If just put
>>
>> .firstHeading { display: none; }
>>
>> In common.css, surely that would get rid of our issue?
>>
>> I haven't done it yet, because I thought I'd just check that it wouldn't
>> ruin anything on the site first. It does mean that we'd need to make sure
>> titles are manually added to all pages (via =a manual h1=, or by using the
>> title for field in the form templates.)
>>
>> Thoughts?
>>
>> Chris Mills
>> Opera Software, dev.opera.com
>> W3C Fellow, web education and webplatform.org
>> Author of "Practical CSS3: Develop and Design" (http://goo.gl/AKf9M)
>>
>>
>>
>
>
Received on Tuesday, 18 December 2012 14:18:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:57:36 UTC