W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2013

Re: Rethinking the necessities of ARIA landmark role "main" and HTML5 <main> element

From: Ian Yang <ian@invigoreight.com>
Date: Wed, 27 Mar 2013 19:25:54 +0800
Message-ID: <CABr1FsezCx2_C0HoRMO_=BOFsgZT9Gwdi2OHjsrDevWhVJF6HQ@mail.gmail.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: Harry Loots <harry.loots@ieee.org>, W3C WAI ig <w3c-wai-ig@w3.org>, Ian Hickson <ian@hixie.ch>, JF <john@foliot.ca>
On Wed, Mar 27, 2013 at 7:07 PM, Steve Faulkner <faulkner.steve@gmail.com>wrote:

> Hi Harry,
>
> and Ian's proposal will form a perfect fail-safe when authors do not use
>> role=main or <main>.
>>
>
> problem is its not a perfect fail safe I have actually looked into a
> heuristic approach and like most heuristics it fails at times. From HTML
> data I collected and reviewed [1] I found that exclusion was not a reliable
> indicator.
>
> There is no reason why the two principles cannot co-exist
>>
>
> of course, bit one principle is a thought experiment, the other is
> implemented and used already, I urge anyone who thinks Ian's idea is
> worthwhile to define how it would work in practice and get implementers
> interested in making it real.
>
> [1] http://webdevdata.org/
>


Well, maybe it's like my two cents which was mentioned before.

>From document structure's perspective of view, Hickson is right. The
structure of a document doesn't need an explicitly defined "main" area.

>From accessibility's perspective of view, introducing role="main" and
<main> element is right. Developers need the "main" area to implement the
accessibility goal.

Since two views are right in its perspective, there's really not much to
debate.


Sincerely,
Ian Yang
Received on Wednesday, 27 March 2013 11:26:27 GMT

This archive was generated by hypermail 2.3.1 : Wednesday, 27 March 2013 11:26:27 GMT