W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2014

Re: [whatwg] ARIA semantics of implied rows

From: Daniel Trebbien <dtrebbien@gmail.com>
Date: Fri, 26 Sep 2014 14:39:38 -0400
Message-ID: <CABrgu5TDLD0ginC4NLcNdKXUBEdjigNeAo4Ex3-AjJMoy08jJw@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: WHATWG <whatwg@whatwg.org>
(sorry, forgot to copy the list)

On Fri, Sep 26, 2014 at 2:09 PM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Fri, Sep 26, 2014 at 7:59 PM, Daniel Trebbien <dtrebbien@gmail.com>
> wrote:
>
...

>
> > One issue is that the ARIA semantics for "implied rows" are not defined.
>
> I'm not sure I understand why ARIA would come into play at all when it
> comes to tables. Weren't tables "accessible" (I realize it has always
> been somewhat hard to convey them properly) long before ARIA existed?
>

The issue is that, as far as I can tell, HTML 4.01 does not support
"implied rows":
http://www.w3.org/TR/html401/struct/tables.html
This is new to HTML5.

WAI-ARIA does define roles for a table (grid, row, rowgroup, gridcell,
etc.), but you can't specify the role and state attributes for HTML5
implied rows.

I ran through the "forming a table" steps (
https://html.spec.whatwg.org/multipage/tables.html#forming-a-table ) on
paper for the example and I came up with x_width is 3 and y_height is 15.
If the table model has 3 columns and 15 rows (9 of which are implied), then
browsers should expose 3 columns and 15 rows.
Received on Friday, 26 September 2014 18:40:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:31 UTC