See also: IRC log
<trackbot> Date: 16 June 2011
<adam> adam is on the phone
<MichaelC> scribe: Bruce
URL in annoucement from Shawn, comments open through August.
Early comments appreciated!
Captcha Technique Strategy
<awk> gotta drop off - conflicting meeeing
RESOLUTION: Approach PF about working with them to update http://www.w3.org/TR/turingtest/
<David> me: sorry I'm late
<David> Failure assigned by tool But it should not fail because …
<David> Failure of 1.4.4 (resize text) by using fixed font sizes instead of relative font sizes such as % or em If the user can activate the browser zoom effectively on the content, then it will pass WCAG 2.0. Only if the browser’s zoom feature has been disabled and the fonts are fixed will it be a failure. This is what the WCAG 2.0 term “A mechanism is available…” means.
<David> Failure of 1.4.4 (resize text) because of fixed object sizes such as px, rather than % or em Same as above.
<David> Failure of 1.3.1 (Info and Relationships) because headings were not nested (e.g. H1 followed by H2 etc…) WCAG does not require “proper” nesting of headings. HTML 4, XHTML 1, and HTML 5 do not require properly nested headings either. It is a good practice, but it is not a failure of WCAG 2.0
<David> Failure of 2.4.4 (Link Purpose – in context) because of link text such as “click here” or “more”. If there is a way to determine the destination of the link from the enclosing sentence, paragraph or list of links, then there is no failure.
<David> Failure of 1.3.1 (Info and Relationships) based on not using the scope element on a data table The Scope element is only one way to meet semantic markup for a table, and is used mostly when there are headers in both the columns and the rows. It should not be a failure for tables that have simple headings at the top of each column.
<David> Failure of 1.4.3 based on clicking a link and opening to a new window. It’s only a failure of 1.4.3 if it produces an extreme change context on focus (which is when he user lands on the link), not when they click a link
Also related to current thread on testing tools looking for sufficient techniques.
<jamesn> another for tables is when tools insist that tables MUST have TH cells when TD cells with scope is fine too
Action item to David for Top 10 mistake list
<trackbot> Sorry, couldn't find user - item
Action David Lead on Top 10 miss understanding
<trackbot> Sorry, amibiguous username (more than one match) - David
<trackbot> Try using a different identifier, such as family name or username (eg. dmacdona, dtodd2)
Here is top of recent thread:
reasons why word doucments web content
can access via url and http
readily available software
cost free multiplatform viewers
it is clearly content linked from the web
authors link to .doc just like they link to .pdf, and PDFs are web content
RESOLUTION: question for survey
Interested in feedback from others not on call
Add other document formats to survey
<MichaelC> trackbot, end meeting
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 embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Found Scribe: Bruce Inferring ScribeNick: Bruce Default Present: Andrew_Kirkpatrick, Michael_Cooper, Adam_Solomon, Gregg_Vanderheiden, Bruce_Bailey, Wolf_Schmidt, +1.650.214.aaaa, Loretta_Guarino_Reid, Tim_Boland, James_Nurthen, David_MacDonald Present: Andrew_Kirkpatrick Michael_Cooper Adam_Solomon Gregg_Vanderheiden Bruce_Bailey Wolf_Schmidt +1.650.214.aaaa Loretta_Guarino_Reid Tim_Boland James_Nurthen David_MacDonald Agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2011AprJun/0154.html Found Date: 16 Jun 2011 Guessing minutes URL: http://www.w3.org/2011/06/16-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]