Re: PF Response: @Summary

Henri Sivonen writes:
> On Jul 6, 2009, at 20:50, Joshue O Connor wrote:
>> Ok, if you look at the following complex table at Gez Lemons site,  
>> Juicy
>> Studio. [1]
>> For a suitable @summary overview you could say something like:
>> <table summary="A complex table of two halves. Firstly, there are 7
>> columns with the headings Child Investment, Type, Status, Allocation,
>> Total Cost of Ownership, Return on Investment, Net Present Value, with
>> their corresponding values in rows beneath them. The table is then
>> followed by a column called Property that has two sections of
>> sub-headings of Budgeted, Actual and Forecasted with their  
>> corresponding
>> running cost values for three weekly periods starting from the 12th of
>> December 2005 to the 26th">.
>> [1}
> I observe that the actual summary looks like this:
>> <table summary="Child investment portfolios with budgeted, actual and 
>> forecast running costs for particular dates">
> It's much shorter, and it's caption-like.
And it makes an inadequate summary,k though it would make a great

Please notice that your "caption" text says nothing about how the data
is structured. That's important, very important. Jo;sh's summary has
that information. Your caption does not.

Is anyone getting it yet?


> I think this anecdotal case study supports the notion that @summary  
> isn't actually used as prescribed--not even by experts.
> -- 
> Henri Sivonen


Janina Sajka,	Phone:	+1.202.595.7777;
Partner, Capital Accessibility LLC	http://CapitalAccessibility.Com

Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada
Learn more at http://ScreenlessPhone.Com

Chair, Open Accessibility	
Linux Foundation

Chair, Protocols & Formats
Web Accessibility Initiative
World Wide Web Consortium (W3C)

Received on Tuesday, 7 July 2009 12:56:24 UTC