W3C home > Mailing lists > Public > www-archive@w3.org > July 2008

RE: Request for PFWG WAI review of @summary for tabular data

From: Chris Wilson <Chris.Wilson@microsoft.com>
Date: Wed, 23 Jul 2008 16:27:11 -0700
To: "joshue.oconnor@cfit.ie" <joshue.oconnor@cfit.ie>, "wai-liaison@w3.org" <wai-liaison@w3.org>, Al Gilman <Alfred.S.Gilman@IEEE.org>, Judy Brewer <jbrewer@w3.org>, Michael Cooper <cooper@w3.org>
CC: W3C WAI-XTECH <wai-xtech@w3.org>, HTML WG <public-html@w3.org>, Dan Connolly <connolly@w3.org>, "Michael(tm) Smith" <mike@w3.org>, Ian Hickson <ian@hixie.ch>, www-archive <www-archive@w3.org>
Message-ID: <D12127075745E648BBC075EF46983E17102BCDFF72@TK5-EXMBX-W603v.wingroup.windeploy.ntdev.microsoft.com>

Any update on this request from the PF group?

-----Original Message-----
From: Joshue O Connor [mailto:joshue.oconnor@cfit.ie]
Sent: Thursday, June 26, 2008 7:33 AM
To: wai-liaison@w3.org; Al Gilman; Judy Brewer; Michael Cooper
Cc: W3C WAI-XTECH; HTML WG; Dan Connolly; Michael(tm) Smith; Ian Hickson; Chris Wilson
Subject: Request for PFWG WAI review of @summary for tabular data

The HTML 5 working group is debating the need for a suitable mechanism
to summarize a data table. Please note, the latest published version of
HTML 5 has no summary attribute.

However, HTML 5 needs a mechanism to provide a data table with a
summary. An explicitly associated, programmatic feature is required in
order to provide an overview of tabular data or a brief explanation of
how to navigate a data table for people who use assistive technology
(AT). This is because an AT user needs to easily form a mental image of
a tables contents in order to better understand its structure, or
semantic relationships. The mechanism needs to be explicitly associated
with the table or it becomes more difficult for AT to make that
association. A summary mechanism may seem irrelevant or redundant to
those with good eyesight because they have access to content
relationships at a glance.

However for users with visual impairments, additional semantics are
often needed as a vital aid to comprehension. These useful semantics,
such as those supplied by @summary, are often the difference between
"seeing" or "not seeing" the table as a whole. @summary therefore
provides a 'quick scan' feature for non-sighted users that requires no
complex user interaction beyond giving the table element focus.

The @summary is well supported by current AT and its implementation for
authors is also widely documented.

The issue is detailed at:
http://esw.w3.org/topic/HTML/SummaryForTABLE

In order for this debate to reach a satisfactory resolution, review and
advice from the PFWG and WAI on the potential accessibility impact of
not providing an explicit mechanism to summarize a table in HTML 5 would
be appreciated as well as helping to get clarification from the HTML 5
WG as to why the current @summary attribute was not included in the new
specification in light of its benefits.

Thank you.

Best Regards,

Joshue O Connor
Gregory J. Rosmaita
Steve Faulkner
Laura L. Carlson

--
HTML WG Members
Received on Wednesday, 23 July 2008 23:27:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 November 2012 14:18:19 GMT