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

Re: That annoying duplicate <h1> issue

From: Chris Mills <cmills@opera.com>
Date: Tue, 18 Dec 2012 13:13:29 +0000
Cc: "public-webplatform@w3.org" <public-webplatform@w3.org>
Message-Id: <B634E68F-09E3-4435-9FC8-5AD43E0F40A2@opera.com>
To: PhistucK <phistuck@gmail.com>
Yup, you are absolutely right, so we ought to get it removed form the markup eventually. But I thought my quick fix would be worthwhile in the short term, until we get it fixed properly, as long as it doesn't mess anything else up.

On 18 Dec 2012, at 13:08, PhistucK <phistuck@gmail.com> 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 13:14:02 UTC

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