RE: issue-633 Updates to grid and gridcell roles

Tables should not support selection. It is just a table. 


Rich Schwerdtfeger



From:   Matt King <a11ythinker@gmail.com>
To:     "'Joseph Scheuhammer'" <clown@alum.mit.edu>, <public-pfwg@w3.org>
Date:   10/01/2015 11:06 AM
Subject:        RE: issue-633 Updates to grid and gridcell roles



I saw that comment in the code. 
I don't think we need to focus on selection in the short description.
Practically all interactive widgets support it and we do not consistently
call it out in the short description. It is enough to say that the grid is 
a
widget and supports navigation.

Matt

-----Original Message-----
From: Joseph Scheuhammer [mailto:clown@alum.mit.edu] 
Sent: Thursday, October 1, 2015 7:41 AM
To: public-pfwg@w3.org
Subject: Re: issue-633 Updates to grid and gridcell roles

Hi Matt,

There is an editor's note in the master branch that states (my emphasis):
" Now that 1.1 will include a table role, we need to differentiate the 
short
description more sufficiently. Emphasize that grids are "interactive" 
tables
that *maintain a selection state*."

One of the states that grid supports is aria-multiselectable, but this is
absent in the case of the table role.  Similarly, the gridcell role 
supports
aria-selected, but the cell role does not.

This is one of the main differences between grids/gridells and 
tables/cells,
and it should be underscored up front.  But, I'm having a tough time 
trying
to fit it into the new short description.

How about:

"A composite widget that supports a selection model, containing one or 
more
rows with one or more cells where some or all of the cells in the grid are
focusable using two-dimensional navigation, such as by directional arrow
keys."

--
;;;;joseph.

'Array(16).join("wat" - 1) + " Batman!"'
            - G. Bernhardt -

Received on Tuesday, 6 October 2015 18:02:51 UTC