- From: Alexander Surkov <surkov.alexander@gmail.com>
- Date: Wed, 25 Mar 2015 15:25:38 -0400
- To: Joseph Scheuhammer <clown@alum.mit.edu>
- Cc: Richard Schwerdtfeger <schwer@us.ibm.com>, David Bolter <dbolter@mozilla.com>, PF <public-pfwg@w3.org>
- Message-ID: <CA+epNscbLwHTe1fpEdbG83PKx63vaD-HQ2RzNF3HbZU+vMcCRA@mail.gmail.com>
Hi, Joseph.
On Wed, Mar 25, 2015 at 2:44 PM, Joseph Scheuhammer <clown@alum.mit.edu>
wrote:
> Hi Alex,
>
> On 2015-03-25 1:22 PM, Alexander Surkov wrote:
>
>> Hi, Rich. I missed how 4 follows from 1, 2, 3 because row count and row
>> indexes seem unrelated with row groups, at least I don't see a reason why
>> they should be.
>> Thanks.
>> Alex.
>>
>
> Previously, you wrote (my emphasis):
>
> 1. I only see one use case for role="rowgroup" is to break rows into
>> groups, each groups is a separate set and *position inside it and set size*
>> are calculated independently.
>>
>
> We interpreted, perhaps by mistake, that your use of "position" and "set
> size" was actually row/col index and row/col count, since, for ARIA 1.1,
> the properties for sizes and positions in the context of a table or grid
> are aria-rowcount, aria-colcount, aria-rowindex, and aria-colindex.
> (Aside: aria-posinset and aria-setsize are not supported on role rowgroup).
>
Right. As I understand it aria-colcount and rowindex are used to "fix"
number of rows and row indexes in case of missed rows, they are not about
groping.
>
> Items 1, 2, and 3 are an argument that the counts and indices are not
> relevant to role rowgroup. You agree -- "row count and row indexes seem
> unrelated with row groups" -- although, the agreement might be a
> coincidence.
>
> Regardless, the point is that size and position have no impact with
> respect to role rowgroup.
Ok, I don't have a real world request for this, I just assume that
organizing table rows into groups should have its own use case. If lists
have it then why tables are much different.
> Hence, based on size and position only, elements with role rowgroup do not
> require an accessible in the a11y tree. The only reasons for an accessible
> are if the rowgroup element is focusable, or has some other ARIA global
> attribute. Otherwise, there is no accessible.
What is the point to put role="rowgroup" for the author if it doesn't have
accessibility mapping?
Thanks!
Alex.
>
>
>
>> On Tue, Mar 24, 2015 at 3:50 PM, Richard Schwerdtfeger <schwer@us.ibm.com
>> <mailto:schwer@us.ibm.com>> wrote:
>>
>> Alex,
>>
>> This is in response to your first bullet on rowgroup after today's
>> #aapi discussion:
>>
>> 1. The group has determined that the aria-rowcount needs to be
>> indicative of the total number of rows in the entire table or grid.
>> 2. The aria-rowindex is indicative of the index of the row within
>> the entire set of rows for the entire grid or table
>> 3. Due to 1 and 2 rowgroups have no impact on the values for
>> aria-rowcount and aria-rowindex
>> 4. So, a rowgroup will have no impact on context with respect to
>> row count. So, if it is focusable (has a tabindex attribute) or it
>> has an ARIA global attribute applied we will give a role of
>> "group" for MSAA based platforms or UIA, ATK/ATSPI will make it a
>> ROLE_PANEL otherwise it will not be mapped.
>>
>> Rich
>>
>>
>> Rich Schwerdtfeger
>>
>>
> --
> ;;;;joseph.
>
> 'Array(16).join("wat" - 1) + " Batman!"'
> - G. Bernhardt -
>
>
Received on Wednesday, 25 March 2015 19:26:07 UTC