- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Tue, 2 Mar 2010 07:18:58 -0600
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, "Gregory J. Rosmaita" <oedipus@hicom.net>
- Cc: "public-html-a11y@w3.org" <public-html-a11y@w3.org>
Hi Leif, Thanks for putting this Change Proposal together and for your thoughtful responses on the other thread, Leif. I'll be giving them serious thought. Your proposal removes much of what is wrong with Cynthia’s. As the recent survey was split and the discussion on the other thread seems to be at a stalemate, it might help if the group came to consensus on a table summary's current and future functional requirements. As mentioned previously [2], a survey on that might help. You have already answered these but if the group did it might help. * Is a summary's purpose to provide an overview of how data has been organized into a table or a brief explanation of complex data table as stated in WCAG2's H73 or is it to provide a long description as stated in HTML 4? * Text string, restricted inline content, inline content, or block level content? * Invisible, visible, or some combination (button) by default? * Visibility settings via user agent or markup or CSS or JavaScript? If the group agrees on the requirements in advance, writing a proposal would be much easier. Best Regards, Laura [1] http://lists.w3.org/Archives/Public/public-html-a11y/2010Feb/0572.html -- Laura L. Carlson
Received on Tuesday, 2 March 2010 13:19:33 UTC