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

Re: Use and abuse of @summary

From: Robert J Burns <rob@robburns.com>
Date: Wed, 18 Feb 2009 10:30:51 -0600
Cc: "Steven Faulkner" <faulkner.steve@gmail.com>, "Ian Hickson" <ian@hixie.ch>, "HTML WG" <public-html@w3.org>, "Janina Sajka" <janina@rednote.net>, "W3C WAI Protocols & Formats" <w3c-wai-pf@w3.org>, wai-liaison@w3.org
Message-Id: <E25C9457-E21A-4416-A7FF-B7E4934623CE@robburns.com>
To: "Simon Pieters" <simonp@opera.com>
HI Simon,

On Feb 18, 2009, at 8:16 AM, Simon Pieters wrote:

> On Wed, 18 Feb 2009 11:20:32 +0100, Steven Faulkner <faulkner.steve@gmail.com 
> > wrote:
>> On digging into philips data a little bit and measuring its effect  
>> upon
>> users who's screen reading software provides access to the  
>> information it is
>> found that in the overwhelming majority of cases the incorrect uses  
>> of
>> @summary are not announced to screan reader users. Why? Because  
>> screen
>> reading software (JAWS and Window eyes) that supports @summary also  
>> uses
>> heuristics to suppress the announcement of layout tables to users
> I think it would be useful to specify an algorithm for deciding  
> whether a table is a layout table or not -- not just for deciding  
> whether or not to use summary='' but also e.g. for deciding whether  
> <td> should be a sectioning root or not.

I agree. I think it might also be useful to specify an attribute to  
allow authors to indicate a layout table as well (which could then be  
incorporated into the algorithm).

Take care,
Received on Wednesday, 18 February 2009 16:31:39 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:42 UTC