W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > March 2011

Re: Understanding WCAG 2- SC 1.3.1

From: Loretta Guarino Reid <lorettaguarino@google.com>
Date: Wed, 23 Mar 2011 09:33:45 -0700
Message-ID: <AANLkTimfiPNOB6BKWWoaKqDujKHWbkdfWuTQ6yNsd0zX@mail.gmail.com>
To: Sailesh Panchang <spanchang02@yahoo.com>
Cc: public-comments-wcag20@w3.org
On Fri, Oct 8, 2010 at 9:58 AM, Sailesh Panchang <spanchang02@yahoo.com>wrote:

> Refer: http://www.w3.org/WAI/GL/2010/WD-UNDERSTANDING-WCAG20-20100923/
> Understanding SC 1.3.1
> Under Intent it states:
> it may be most appropriate to duplicate some information (for instance, in
> an HTML table, providing the summary both in the paragraph before the table
> and in the summary attribute of the table itself).
> Comment: Not sure why summary attribute needs to be present  if it
> duplicates text in para abobe.
> This is giving fodder to those who wish to banish the summary attribute.
> If this duplication is alright,  why then  having alt that is identical to
> anchor text in image link not alright?
> Thanks,
> Sailesh Panchang
> Web Accessibility Specialist
> www.deque.com
> ==============================
Response from the Working Group
With the table, the text in the paragraph above is not programmatically
associated with the table (except if using WAI-ARIA). The summary is linked.
With your second example, both texts are programmatically associated to the

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
Received on Wednesday, 23 March 2011 16:34:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:13 UTC