W3C home > Mailing lists > Public > public-html@w3.org > June 2009

Re: Issues of @summary and use of data for "decisions"

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Tue, 23 Jun 2009 14:07:41 -0500
Message-ID: <1c8dbcaa0906231207o79c27cb2w268ff363552aa3a6@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Cc: Shelley Powers <shelley.just@gmail.com>, Sam Ruby <rubys@intertwingly.net>, HTMLWG WG <public-html@w3.org>
Hi Simon,

> I have heard arguments along the lines of "but captions and summaries are
> different" or "but captions should be short, summaries long", but I have not
> heard any argument as to why the user agent needs to be able to distinguish
> between the caption and the summary. (I might have missed it, please provide
> a pointer if so.)

Providing summary information visually by default would be extra
verbiage that most authors/designers would be reluctant to include
visually on a page because of redundancy. (For more info see sighted
use case).
http://esw.w3.org/topic/HTML/SummaryForTABLE#head-50bd1f9b6606cd0d63fc7e525c1db226aac36d9b

Most of the debate around providing a summary mechanism has been about
misunderstanding its purpose, so trying to merge its purpose with
another element's purpose may be problematic leading to more
confusion.

Related ref:
short and long text alternatives.
* These are different concepts with different uses and both should be
provided as separate functions. Short descriptions are read
automatically when the item is encountered. Long descriptions are read
only on user request.
http://www.w3.org/2009/06/Text-Alternatives-in-HTML5

Best Regards,
Laura

-- 
Laura L. Carlson
Received on Tuesday, 23 June 2009 19:08:22 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:04 UTC