- From: Michiel Bijl <michiel@agosto.nl>
- Date: Tue, 29 Sep 2015 13:41:40 +0200
- To: Jason Kiss <jason@accessibleculture.org>
- Cc: Matt King <a11ythinker@gmail.com>, PF <public-pfwg@w3.org>
> But the newer definition of the grid role isn't as clear on this point, > since a sortable table of otherwise static tabular data won't > necessarily have two-dimensional navigation. I'm interested in how AT will handle this; are all keyboard interactions between AT the same for tables? And how will they differentiate tables and grids? And what about a table element with a grid? —Michiel > On 29 Sep 2015, at 02:28, Jason Kiss <jason@accessibleculture.org> wrote: > > Hi Matt, > > Small question regarding this first sentence / short description: "A > composite widget containing a collection of one or more rows that each > contain one or more cells where some or all cells are focusable by > using methods of two-dimensional navigation , such as directional > arrow keys." > > I read this as saying each row in a grid has to have at least one cell > that is focusable by two-dimensional navigation. I think it's the use > of the word "each". > > Couldn't a grid that has multiple rows with interactive cells have > some rows whose cells aren't interactive? If so, possibly rewrite as > something like: "A composite widget containing one or more rows with > one or more cells where some or all of the cells in the grid are > focusable by using methods of two-dimensional navigation, such as > directional arrow keys." > > Or, borrowing from the earlier definition for grid: "A composite > widget that contains tabular data arranged in rows, columns, and > cells, where some or all of the cells are focusable through methods of > two-dimensional navigation, such as directional arrow keys." > > On a slightly related note, I'm still wondering about simple tables > with sortable columns. Do these require the grid role? Based on the > current definition of the table role [1], it would seem they do. But > the newer definition of the grid role isn't as clear on this point, > since a sortable table of otherwise static tabular data won't > necessarily have two-dimensional navigation. > > Jason > > [1] http://rawgit.com/w3c/aria/master/aria/aria.html#table > >> On Tue, Sep 29, 2015 at 10:47 AM, Matt King <a11ythinker@gmail.com> wrote: >> Following is a summary of changes to grid and gridcell roles proposed in the >> mck_issue633 branch[1]. These changes incorporate feedback from the Sep 17 >> ARIA meeting and enable grid to be applied to some of the scenarios raised >> by issue 633. >> >> >> >> Changes to grid as compared to master[2]: >> >> 1. Expanded the definition of the role to clearly state grid can be used to >> not only present tabular data but also group interactive elements, such as a >> set of navigation links. >> >> 2. Clarified the intent and meaning of readonly when applied to grid. >> >> 3. Updated language related to colspan and rowspan to incorporate new ARIA >> 1.1 properties. >> >> 4. Removed unnecessary or eroneous references to treegrid. >> >> 5. Rearranged text to present requirements in a logical and easier to >> comprehend sequence. >> >> 6. Made editorial changes to simplify wording, fix grammar errors, and >> reduce use of passive voice. >> >> >> >> Changes to role gridcell as compared to master[2]: >> >> 1. Changed the word "active" to "focusable." in the phrase: "Gridcells may >> be focusable, editable, and selectable." >> >> 2. Other editorial changes, e.g., adding reference links and using the word >> gridcell in place of cell where it could affect the meaning. >> >> >> >> [1] mck_issue633 branch: >> >> http://rawgit.com/w3c/aria/mck_issue633/aria/aria.html#grid >> >> >> >> [2] master branch: >> >> http://rawgit.com/w3c/aria/master/aria/aria.html#grid >> >> >> >> Matt King >
Received on Tuesday, 29 September 2015 11:41:46 UTC