Re: WCAG-ISSUE-23 (DavidMacD): We should consider a new "Failure to provide role=presentation on a layout table"

Hello all,

Although I agree that layout tables are evil and should die, I cannot 
see this as a WCAG failure. Simple layout tables (no <th>, no <caption>, 
no @summary) are usually ignored by most screen readers, even if they 
don't have the role="presentation", and behavior does not change 
whenadding it. Therefore, I cannot find a justification to include a 
failure that would force developers to add a role that has no practical 
effect on accessibility.

Regards,
Ramón.

Steve noted:

> Note: HTML5 requires role=presentation on layout tables
> 
> " If a table is to be used for layout it MUST be marked with the 
> attribute role="presentation" for a user agent to properly represent the 
> table to an assistive technology and to properly convey the intent of 
> the author to tools that wish to extract tabular data from the document."
> 
> http://www.w3.org/html/wg/drafts/html/master/tabular-data.html#the-table-element
> --
> On 1 June 2014 10:14, Web Content Accessibility Guidelines Working Group 
> Issue Tracker <sysbot+tracker@w3.org <mailto:sysbot+tracker@w3.org>> wrote:
> 
>     WCAG-ISSUE-23 (DavidMacD): We should consider a new "Failure to
>     provide role=presentation on a layout table"
> 
>     http://www.w3.org/WAI/GL/track/issues/23
> 
>     Raised by: David MacDonald
>     On product:
> 
>     We should consider a new "Failure to provide role=presentation on a
>     layout table." In the old days there were many wars about whether to
>     allow layout tables. wai aria has now solved the issue pretty well
>     and we should consider requiring it now on layout tables.
> 
> 
> 
>

Received on Sunday, 1 June 2014 12:07:10 UTC