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

Re: maincontent element

From: Cameron Jones <cmhjones@gmail.com>
Date: Mon, 10 Sep 2012 23:42:03 +0100
Message-ID: <CALGrgeu4u9G+koL5cm_NMWCGj=FhcT+FR=smrX70fKWUx7YUbQ@mail.gmail.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Cc: Steve Faulkner <faulkner.steve@gmail.com>, HTMLWG WG <public-html@w3.org>
On Mon, Sep 10, 2012 at 11:40 PM, Cameron Jones <cmhjones@gmail.com> wrote:
> On Mon, Sep 10, 2012 at 10:28 PM, Silvia Pfeiffer
> <silviapfeiffer1@gmail.com> wrote:
>> On Tue, Sep 11, 2012 at 6:21 AM, Cameron Jones <cmhjones@gmail.com> wrote:
>>> On Mon, Sep 10, 2012 at 8:59 PM, Steve Faulkner
>>> <faulkner.steve@gmail.com> wrote:
>>>> hi Cameron, the same arguments you are using for <maincontent> could
>>>> be used for role=main
>>>
>>> Not so, as i said at the end of the last mail:
>>>
>>> "The great thing about ARIA is that it requires people to be explicit,
>>> and with the intention of providing accessibility"
>>
>> Wouldn't it be nice it the page markup that every Web publisher
>> provides was automatically accessible without the need to explicitly
>> provide for accessibility?
>>
>> Silvia.
>
> Isn't that the ultimate goal?
>
> In which case, people will all be using ARIA roles anyway.
>

Sorry, i misread.

I don't think there can ever be that much flexibility without needing
attributes. So ARIA is the correct implementation.

Thanks,
Cameron Jones
Received on Monday, 10 September 2012 22:42:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 10 September 2012 22:42:31 GMT