Re: [ARIA] Table and cell roles have been added to the spec.

It is not necessary to make a sortable table into an interactive read-only 
grid where the entire grid is navigable with arrow keys.
It is just as valid to leave it as a static table where each header is a 
tab stop.

Matt King
IBM Senior Technical Staff Member
I/T Chief Accessibility Strategist
IBM BT/CIO - Global Workforce and Web Process Enablement 
Phone: (503) 578-2329, Tie line: 731-7398
mattking@us.ibm.com



From:   Jason Kiss <jason@accessibleculture.org>
To:     Joanmarie Diggs <jdiggs@igalia.com>, 
Cc:     "W3C WAI Protocols & Formats" <public-pfwg@w3.org>
Date:   06/14/2015 07:48 PM
Subject:        Re: [ARIA] Table and cell roles have been added to the 
spec.



Based on the definition of the table role, I'd just like to confirm
that a simple, otherwise static table that can be reordered by column
(e.g. via links in or on the column headers) effectively becomes an
interactive grid, and so should rightly use role="grid", if that role
is not already exposed somehow by the browser? Does that sound right?

Thanks,

Jason

On Sat, Jun 6, 2015 at 3:43 AM, Joanmarie Diggs <jdiggs@igalia.com> wrote:
> Hi all.
>
> As per yesterday's meeting [1], I have merged the table and cell roles
> into the spec. I will propose clarifying text to address the readonly
> and required properties being inherited by columnheader and rowheader as
> per action-1646 [2]. Lastly, I'll create a branch with some
> mostly-editorial changes for the grid-related content in the spec,
> probably some time next week.
>
> The new roles can be found here:
> https://rawgit.com/w3c/aria/master/aria/aria.html#cell
> https://rawgit.com/w3c/aria/master/aria/aria.html#table
>
> --joanie
>
> [1] http://www.w3.org/2015/06/04-aria-minutes.html#item01
> [2] https://www.w3.org/WAI/PF/Group/track/actions/1646
>