W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2013


From: Pierre Dubois <duboisp2@gmail.com>
Date: Fri, 25 Jan 2013 11:57:06 -0500
Message-ID: <CAPGwD7jjNnE6_TwFNVbpttar=vunOkFbAhLW=J=odEzKntegQA@mail.gmail.com>
To: WAI Group <w3c-wai-ig@w3.org>
Cc: Userite <richard@userite.com>
Userite wrote Jan 25
> If the <tfoot> contains global information then it is in the wrong place. global information should be presented before the data (perhaps in the summary :)

Here some references to support it


Footnotes vs column summary (tfoot element)

As defined in the HTML5 specification, the tfoot element represents
the block of rows that consist of the column summaries (footers).

The question is: What exactly is a "column summary"?

Table footnotes (global information about the tabular data) is
definitely not "columns summary". Column summary is often know as the
"total" row or row group at the bottom the the table. So When you read
that row or row group you get a summary of the data per columns.

When a table have global information defined inside the tfoot, the
elements (tr, th, td) inside the tfoot is used for layout. That create
a hybrid data table combined with a layout table. That make it fail
the WCAG Level A. See F46: Failure of Success Criterion 1.3.1 due to
using th elements, caption elements, or non-empty summary attributes
in layout tables (http://www.w3.org/TR/WCAG-TECHS/F46.html).

Multiple tbody element and WCAG

Having multiple tbody have a role in the accessibility when you use
the technique H63: Using the scope attribute to associate header cells
and data cells in data tables

When you have an header cell (th) that is marked with the scope
"rowgroup" it needs to be anchored in a row group (tbody). See the
HTML5 specification:

What could be the full potential of using multiple tbody and multiple
colgroup by excluding the printing and the zebra stripping use case?

Here's my answer. What is yours?

When the WCAG technique H63 (scope attribute) or H43 (id/headers
attribute) is use to make a complex HTML table accessible, that can
create two different perception of the same table, one for the screen
readers and one for the visual user. My research to combine both
perception resulted in the elaboration of 12 techniques (WCAG 2.0
style). Also that research resulted to: a proposal to add a new
attribute (hassum) at the table element, a proposal to remove the
scope and headers attribute and a proposal to change the current table
algorithm. (https://github.com/duboisp/Table-Usability-Concept)

Here a few techniques (WCAG 2.0 style), that I drafted, where a visual
user and a screen reader can benefit equally of an HTML table that
have multiple tbody element and multiple colgroup element. (All the
technique and related documentation -
* Defining a Data Row Group -
* Summaries a Data Row Group -
* Summaries a Data Column Group -


Received on Friday, 25 January 2013 16:57:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:47 UTC