- From: Joanmarie Diggs <jdiggs@igalia.com>
- Date: Thu, 02 Apr 2015 09:29:04 -0400
- To: James Craig <jcraig@apple.com>
- CC: W3C WAI Protocols & Formats <public-pfwg@w3.org>
On 04/02/2015 02:13 AM, James Craig wrote: >> On Apr 1, 2015, at 9:16 PM, Joanmarie Diggs <jdiggs@igalia.com> wrote: >> >> The spec currently does not seem to allow nested rowgroups. Is that by >> design or omission? > > By design, primarily because HTML doesn't allow nested tbody elements. Ok, thanks! Regarding this: > The "rowgroup" role was mainly added so that we could define presentation inheritance to required child nodes in ARIA 1.0. e.g. <table role="presentation"> causes an implicit presentation role on the <tbody>, which in turn causes an implicit presentation role on the <tr>, etc. etc. Please see [1] and [2]. And if you have time to, please reply. The executive summary is that I don't think what you state above is actually necessary: Whether or not you put an ARIA rowgroup role on a tbody, that tbody, and its rows, and the cells in those rows inherit / are impacted by the presentational role on the parent table. And Joseph seems to think it's not technically allowed because it violates the required context role for rowgroup. > The rowgroup role was not intended to be mapped to AX APIs (they hadn't previously mapped thead/tfoot/tbody) and still isn't mapped by most User Agents. Firefox is the exception. IIRC, Alex added it a couple years ago, though the API mapping guide does require it. Understood. And I fully agree because I don't like unexpected things or "noise" in the accessible tree. And I've stated at a number of AAPI meetings, "rowgroup must not be mapped on my platform!" :) But then people said, "but what if it's focusable?" And as much as I hate to admit it, if a group of rows is focusable then that group of rows needs an accessible object. So unless we can state authors MUST NOT make multiple rows focusable, it's going to have to be conditionally mapped. To me, this is really the main use case for rowgroup. As for the nested question: Could you have a treegrid in which a rowgroup is collapsible/expandable? If so, could that rowgroup have child rowgroups that are also collapsible/expandable? If so, what if the author chooses to make those collapsible/expandable groups focusable? --joanie [1] https://lists.w3.org/Archives/Public/public-pfwg/2015Mar/0240.html [2] https://lists.w3.org/Archives/Public/public-pfwg/2015Mar/0251.html
Received on Thursday, 2 April 2015 13:29:41 UTC