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

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

From: Simon Pieters <simonp@opera.com>
Date: Wed, 24 Jun 2009 01:55:55 +0200
To: "Shelley Powers" <shelley.just@gmail.com>
Cc: "Steve Axthelm" <steveax@pobox.com>, "Laura Carlson" <laura.lee.carlson@gmail.com>, "Sam Ruby" <rubys@intertwingly.net>, "HTMLWG WG" <public-html@w3.org>
Message-ID: <op.uvz4rhfpidj3kv@simon-pieterss-macbook.local>
On Wed, 24 Jun 2009 01:35:17 +0200, Shelley Powers  
<shelley.just@gmail.com> wrote:

>> Thanks.
>> If this is the case, then it seems to me that the user agent does not  
>> need
>> to be able to distinguish between caption and summary, and thus  
>> <caption>
>> can be used for both purposes.
>> --
>> Simon Pieters
>> Opera Software
> Simon, are you being deliberately obtuse?

No, not deliberately. :-)

> He is talking about what happens with screenreaders. The summary is
> targeted at screenreaders.
> What is the difference in behavior when someone like me, who is
> sighted, looks at the table using Opera? I see the caption, I don't
> see summary.
> Therefore one field cannot be used for both.

It has been argued that summaries would likely be more useful on avarage  
if they were visible by default. It has also been argued that some  
summaries are useful also to visual users. These are two reasons why HTML5  
proposes to put the summary in <caption>, AIUI.

Simon Pieters
Opera Software
Received on Tuesday, 23 June 2009 23:56:51 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:44:49 UTC