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

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

From: Shelley Powers <shelley.just@gmail.com>
Date: Tue, 23 Jun 2009 18:35:17 -0500
Message-ID: <643cc0270906231635t28c37ccaq513601b431afca47@mail.gmail.com>
To: Simon Pieters <simonp@opera.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>
On Tue, Jun 23, 2009 at 6:18 PM, Simon Pieters<simonp@opera.com> wrote:
> On Wed, 24 Jun 2009 01:12:40 +0200, Steve Axthelm <steveax@pobox.com> wrote:
>
>> On 2009-06-23 Simon Pieters <simonp@opera.com> wrote:
>>
>>> How about the following statement?
>>>
>>> <caption> is read automatically when the table is encountered.
>>> summary="" is read only on user request.
>>
>> That's entirely dependent upon the combination of browser/AT/user settings
>> (if any).
>>
>> With default settings, Jaws 10 reads summary automatically with both IE7
>> and FF3. I believe Window Eyes does the same but I'd have to test. Not sure
>> about other AT.
>
> 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?

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.

Shelley
Received on Tuesday, 23 June 2009 23:35:53 UTC

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