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 19:40:30 +1000
Message-ID: <CAHp8n2mkxzDtOH48XsEE5bOt9ZegkEeD8Rsww+FhiSmX16E4VQ@mail.gmail.com>
To: Jirka Kosek <jirka@kosek.cz>
Cc: Cameron Jones <cmhjones@gmail.com>, Steve Faulkner <faulkner.steve@gmail.com>, HTMLWG WG <public-html@w3.org>
On Tue, Sep 11, 2012 at 7:17 PM, Jirka Kosek <jirka@kosek.cz> wrote:
> On 11.9.2012 10:46, Silvia Pfeiffer wrote:
>
>> 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.
>
> That's true. On the other shouldn't be everything inside <body> except
> <footer>, <header>, <menu> and <aside> aside considered as a "maincontent"?

That's the real question, indeed.

Or asked the other way around: is it possible to mark up a page such
that everything that is not main content can be contained in an
existing "semantic" tag or do we still have the need to create our
pages/applications with many <div> elements? If the latter is true,
then it can make sense to pick one <div> as the one to start reading
at.

Silvia.
Received on Tuesday, 11 September 2012 09:41:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 September 2012 09:41:20 GMT