RE: Agenda: August 27, 2015 WAI-PF ARIA Caucus (Correction I am still chairing this week)

> You disagree then, with the current AXAPI mappings.

Yes, because it can never support interoperability.


-----Original Message-----
From: Joseph Scheuhammer [mailto:clown@alum.mit.edu] 
Sent: Thursday, September 10, 2015 9:33 AM
To: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>; James Craig <jcraig@apple.com>; Richard Schwerdtfeger <schwer@us.ibm.com>
Cc: PF <public-pfwg@w3.org>
Subject: Re: Agenda: August 27, 2015 WAI-PF ARIA Caucus (Correction I am still chairing this week)

Hi Bryan,

> I disagree, this is specifically relevant when aria-owns is used to map the proper nesting structure of a Grid or Table, and is equivalent to the thead, tbody, and tfoot grouping structures within that arrangement.

AXAPI does not provide accessibles for rowgroup, thead, tfoot, nor tbody in their accessibility tree.  See https://bugs.webkit.org/show_bug.cgi?id=146239.


> If aria-owns upon role=grid or role=table points to a role=rowgroup node, which in turn uses aria-owns to point to child role=row nodes, the accessibility tree structure is broken if rowgroup is nonexistent in the accessibility tree.

They are non-existent in the AXAPI accessibility tree, currently.

> Also, role=rowgroup is used in role=treegrid structures for nesting levels is it not?

Perhaps, but, as noted above, the rowgroup is not exposed by AXAPI.

As you say, you disagree.  As such, you fall into the camp that says that rowgroup (thead, tbody, and tfoot) has semantic value and should be exposed in the accessibility tree.  You disagree then, with the current AXAPI mappings.

--
;;;;joseph.

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

Received on Thursday, 10 September 2015 16:44:53 UTC