Its not specified any where that a single H1 is the right approach. SEO guys
have found that google search engine tends to read the H1 as the main
subject and decided to punish any page with more then one. the punishment is
not severe so not every one of the major sites obey.
In HTML 5 there is a h
The issue with having more then 1 H! tag is not the validity of the page as
XHTML or HTML5 or any other specification, its not even affecting WCAG1/2.
the only case that is affected is the search engines relationship with H1
that entitled it as the Content's Title. it is not mandatory that it will
I am not sure that a page with multiple important subject does not exist. so
IA wise and semantic wise this is not a must. google wise it is.
On Fri, Oct 16, 2009 at 10:55 PM, Jason Grant wrote:
> Tim,
> Well done for reading the spec - it's always a must.
>
> However, Google came after the HTML
I have somemore invites to give.
yara...@googlewave.com
On Sat, Dec 5, 2009 at 5:51 AM, Duncan Hill wrote:
> On Fri, 04 Dec 2009 16:04:52 -, Krystian Szastok
> wrote:
>
> I think it's a great idea.
>>
>> Problem is that wave is for group projects, so really, if we wanted to
>> roll it out
Am i the only one missing the name attribute in the samples?
On Thu, Dec 17, 2009 at 8:00 PM, Grant Bailey <
grant_malcolm_bai...@westnet.com.au> wrote:
> Sorry everyone, I just discovered what the problem was:
>
> I have multiple style sheets and the browsers were only applying one,
> not two as
omething?
> Grant
>
> -Original Message-
> *From:* li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] *On
> Behalf Of *Yuval Ararat
> *Sent:* Thursday, 17 December 2009 10:11 PM
> *To:* wsg@webstandardsgroup.org
> *Subject:* Re: [WSG] Using CSS to select a tag