- From: Loretta Guarino Reid <lorettaguarino@google.com>
- Date: Tue, 11 Dec 2007 15:29:31 -0800
- To: "aurélien levy" <aurelien.levy@free.fr>
- Cc: public-comments-wcag20@w3.org
There is no requirement in 1.3.1 that every data table must have a caption. A heading preceding a data table suffices to provide information about the relationships in that web page, so it is not necessary to have identical information in a heading and a caption for a table. Since your initial scenario does include information and relationships and captions are not mandatory for all data tables, your initial scenario would pass 1.3.1. Regards, Loretta Guarino Reid, WCAG WG Co-Chair Gregg Vanderheiden, WCAG WG Co-Chair Michael Cooper, WCAG WG Staff Contact On behalf of the WCAG Working Group On Nov 4, 2007 2:34 AM, aurélien levy <aurelien.levy@free.fr> wrote: > > Issue ID: 2029 > http://lists.w3.org/Archives/Public/public-comments-wcag20/2007Jun/0150.html > > I understand your review but my concern is much more about the caption element than the summary attribut. If I follow the rule in my example it result an useless redundancy of element. Can we use # describedby or# labelledby of the Aria spec instead to have just one element used as title for the table event if it's not a caption. > > In every case I think you must add this statement to be more revelant : it may be a judgement call about what information should appear as table caption and if the caption would need to be directly associated with the table > > Yes, user can navigate from table to table but he can do the same with h1, h2, etc and the same with form so if perfectly follow you it will result to something like : > > <form> > <fieldset> > <legend>shopping cart</legend> > <h3>shopping cart</h3> > <table><caption>shopping cart</caption> > .... > </table> > <input type="submit"> > </fieldset> > </form> > > > > >
Received on Tuesday, 11 December 2007 23:30:19 UTC