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

Re: maincontent element

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Tue, 11 Sep 2012 18:46:07 +1000
Message-ID: <CAHp8n2ner5sYEEBgMJN8Th7xNyAOQ7Zy22NhxysQHqf_EsB9qw@mail.gmail.com>
To: Cameron Jones <cmhjones@gmail.com>
Cc: Steve Faulkner <faulkner.steve@gmail.com>, HTMLWG WG <public-html@w3.org>
On Tue, Sep 11, 2012 at 8:40 AM, 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.

Providing ARIA roles is explicit accessibility markup, while
<article>, <menu> etc provide implicit accessibility markup. The
latter does not require people to think about accessibility when they
are developing their pages and the Website becomes "automatically"
accessible. Instead of having to teach everyone ARIA roles, which is a
non-goal for me.

Received on Tuesday, 11 September 2012 08:46:55 UTC

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