- From: Roberto Scano - IWA/HWG <rscano@iwa-italy.org>
- Date: Tue, 22 Jul 2003 10:25:24 +0200
- To: "Chris Brainerd" <Chris.Brainerd@cds.hawaii.edu>, "Chris Ridpath" <chris.ridpath@utoronto.ca>, "WAI WCAG List" <w3c-wai-gl@w3.org>
me too... ----- Original Message ----- From: "Chris Brainerd" <Chris.Brainerd@cds.hawaii.edu> To: "Chris Ridpath" <chris.ridpath@utoronto.ca>; "WAI WCAG List" <w3c-wai-gl@w3.org> Sent: Monday, July 21, 2003 11:39 PM Subject: RE: [#293] Summary for tables > > I concur. > > Chris Brainerd > Instructional Designer > Real Choices ACCESS > Center on Disability Studies > University of Hawaii > Chris.brainerd@cds.hawaii.edu > 808-956-9356 > > > > -----Original Message----- > From: Chris Ridpath [mailto:chris.ridpath@utoronto.ca] > Sent: Thursday, July 17, 2003 3:27 AM > To: WAI WCAG List > Subject: Re: [#293] Summary for tables > > > > > Layout tables should have a summary of "". > > > I agree that all tables should have a summary. But, is it not helpful > for some layout tables to have a summary that describes their layout? > Would people with cognitive impairments find this helpful? Would some > screen reader users find this helpful? > > I believe that we've now reached a point in our discussions where user > agents and checking tools can reliably determine the table purpose. User > agents can then have an option of giving the user the layout table > summaries or not. > > Chris > > >
Received on Tuesday, 22 July 2003 04:25:34 UTC