Re: addition of HTML role requirement mappings

If table and table cell ARIA roles are supposed to be a part of browser
implementation then it looks like spec overbloating with no usecase.



On Fri, Feb 21, 2014 at 12:22 PM, James Craig <jcraig@apple.com> wrote:

> Yeah, I think this illustrates that we need to get table and cell roles in
> soon for ARIA 1.1. cell and gridcell can probably just be aliases, but
> table and grid are semantically different.
>
>
>
> On Feb 21, 2014, at 5:17 AM, Steve Faulkner <faulkner.steve@gmail.com>
> wrote:
>
> Hi all,
>
> hixie has added some role requirements and restrictions in the whatwg spec
> that will  soon come up for cherry picking [1] to the HTML 5.1 spec.
> previously we determined that some of the following were not appropriate,
> so am asking for ARIA folk to review:
>
> note: implementers MUST map to these roles and authors are restricted to
> applying the roles listed for each element (authors can also apply
> role=presentation).
>
> strong semantics:
>
> table element     grid role
> tbody element     rowgroup role
> td element     gridcell role
> tfoot element     rowgroup role
> thead element     rowgroup role
> tr element     row role
>
>
> implicit semantics:
>
> th element     gridcell role     Role must be either columnheader,
> rowheader, or gridcell
>
>
>
> [1]
> https://github.com/w3c/html/commit/5b5ad72b8e7bb36ab863effc942829eef82fe3c4#commitcomment-5449710
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> Regards
>
> SteveF
> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
>
>

Received on Friday, 21 February 2014 17:38:53 UTC