W3C home > Mailing lists > Public > public-html-a11y@w3.org > November 2012

Re: main spec updated - changes to parsing and rendering

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Sun, 18 Nov 2012 08:39:09 +0000
Message-ID: <CA+ri+VnhdKT7MTzgfP3B1ohmkVrWer6osxkVxtdNEFzYtwsRpQ@mail.gmail.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hi Silvia,

>this should be something that every Web page/application provides for.

It should be something that authors/developers add when the content of the
document contains a sub content area that can be logically identified as
the main content, distinct from other sub content areas.


As specified main is not a required element nor is it expected that
browsers will add an implied main semantic to every document, which is why
there is no requirement to parse every web page as per your example.

regards
SteveF



On 17 November 2012 23:35, Silvia Pfeiffer <silviapfeiffer1@gmail.com>wrote:

> Hi Steve,
>
> I have a question about the proposed <main> element. I'm taking this
> discussion into the a11y TF, since I think this is the right place to have
> this discussion first.
>
> To me, the <main> element is primarily a replacement for the @role=main
> use case with some secondary positive implications for semantic document
> analysis and for page styling.
>
> As the use case for @role=main is such that we want to give accessibility
> users a means to directly access the main content of a Web
> page/application, this should be something that every Web page/application
> provides for.
>
> Thus, in my understanding, browsers will need to parse every Web page into
> the following document structure:
> <html>
>  <head>
>  </head>
>  <body>
>    <main>
>    </main>
>  </body>
> </html>
>
> rather than what currently happens:
> <html>
>  <head>
>  </head>
>  <body>
>  </body>
> </html>
>
> It doesn't seem like this is included in your extension spec. Is this
> something you have considered? And what are your thoughts on this, and the
> implications?
>
> Regards,
> Silvia.
>
>
>
> On Tue, Nov 13, 2012 at 12:54 AM, Steve Faulkner <faulkner.steve@gmail.com
> > wrote:
>
>> After discussion on the WHATWG list [1],[2] I have updated the main spec
>> with suggested changes to parser behaviour and rendering
>>
>> https://dvcs.w3.org/hg/html-extensions/raw-file/tip/maincontent/index.html
>>
>> feedback welcome!
>>
>>
>>
>> [1]
>> http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Nov/0045.html
>> [2]
>> http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Nov/0054.html
>>
>> --
>> with regards
>>
>> Steve Faulkner
>> Technical Director - TPG
>>
>> www.paciellogroup.com | www.HTML5accessibility.com |
>> www.twitter.com/stevefaulkner
>> HTML5: Techniques for providing useful text alternatives -
>> dev.w3.org/html5/alt-techniques/
>> Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
>>
>>
>>
>
Received on Sunday, 18 November 2012 08:40:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:32 UTC