Web Content Accessibility Guidelines Working Group Teleconference

29 Mar 2012


See also: IRC log


Bruce_Bailey, adam_solomon, Cooper, Cherie_Ekholm, Loretta_Guarino_Reid, Kathy, Marc_Johlic


<trackbot> Date: 29 March 2012

<scribe> scribe: MichaelC

LC-2603 : Link text identical? https://www.w3.org/2002/09/wbs/35422/20120329misc/results#x2603

RESOLUTION: Accepted with edits

Failure Technique : Failure of Success Criterion 1.3.1 for not correctly marking up table headers https://www.w3.org/2002/09/wbs/35422/20120329misc/results#xtabhead

some doubt about whether example one is always a failure

example 2 seems like a failure but there are many ways to pass

test procedure is too strict, would rule out too much

<Loretta> Notes frm March 29, 2012 telecnference: We dn't think example is necessarily a failure. Split, and we can discuss separately? Example 2 is a failure; headers are not programmatically determined What about using id/header attributes to indicate headers? What about using ARIA to indicate headers? Suggestion: discuss common ways that headers can be marked up as part of the description; change test procedure to check that table headers are

<Loretta> a test, but should prevent us from overconstraining the author.

Failure Technique : Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes https://www.w3.org/2002/09/wbs/35422/20120329misc/results#xtabid

<Loretta> The description is not clear enough about what the problem is; we needed to study the code example clearly and discuss it together to determine that the problem was that data cells were being associated with the wrong headers. It was not, for instance, a syntax problem with the way that the id and header attributes were being used. Please write a longer description that helps people understand the problem clearly.

<Loretta> * This failure is applicable to any table that uses id and header attributes, not just to complex tables.

<Loretta> * We suggest that the description of the example explicitly point out which markup in the example is in error.

trackbot, end meeting

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2012/03/29 20:55:16 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: MichaelC
Inferring ScribeNick: MichaelC
Default Present: Bruce_Bailey, adam_solomon, Cooper, Cherie_Ekholm, Loretta_Guarino_Reid, Kathy, Marc_Johlic
Present: Bruce_Bailey adam_solomon Cooper Cherie_Ekholm Loretta_Guarino_Reid Kathy Marc_Johlic
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2012JanMar/0110.html
Found Date: 29 Mar 2012
Guessing minutes URL: http://www.w3.org/2012/03/29-wai-wcag-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

[End of scribe.perl diagnostic output]