W3C home > Mailing lists > Public > public-html@w3.org > January 2013

Re: Context of the main element

From: Ian Devlin <ian@iandevlin.com>
Date: Thu, 31 Jan 2013 19:08:58 +0100
Message-ID: <CAOYOhSuMxJfZS94q2ExK7+asZSKFXJ7gwOGVXn5yjiLPK4sdPA@mail.gmail.com>
To: Cameron Jones <cmhjones@gmail.com>
Cc: "HTML WG (public-html@w3.org)" <public-html@w3.org>
Perhaps there could be one <main role="main"> to rule them all, and then
multiple <maincontent> elements...

On 31 January 2013 18:56, Cameron Jones <cmhjones@gmail.com> wrote:

> On Thu, Jan 31, 2013 at 5:48 PM, Jeremy Keith <jeremy@adactio.com> wrote:
>> Cameron wrote:
>> > You will not achieve parity if an element is misused to the point that
>> it can no longer be relied upon.
>> I don't think you're grasping what I'm getting at: using main within
>> sectioning content other than the body element wouldn't be a *misuse*, it
>> would simply be *another* use. Just like using footer within sectioning
>> content isn't a misuse; it's perfectly acceptable …but only the footer
>> element that is scoped to the body carries the same meaning as
>> role="contentinfo". It could be the same for main: use the main element
>> scoped to the body (where it means role="main") but go ahead and use it in
>> other sectioning content too …but in those cases, it won't map to
>> role="main".
> But what is the main-main content of the page then? I need to direct
> accessibility users to the "main" content of the *whole* page. How can that
> be determined if there are more than one of them?
> That definition is also against the ARIA specification and also distinctly
> stated is *not* the aim nor purpose of the element.
> Thanks,
> Cameron Jones

ian devlin
e: ian@iandevlin.com
w: www.iandevlin.com
t: @iandevlin <http://www.twitter.com/iandevlin>
skype: idevlin

buy my book: html5 multimedia: develop and design<http://html5multimedia.com>
Received on Thursday, 31 January 2013 18:09:22 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:30 UTC