RE: Minutes WCAG 15 September 2011

Apologies for my late regrets.  Phone problems.

________________________________

From: w3c-wai-gl-request@w3.org on behalf of Michael Cooper
Sent: Thu 9/15/2011 5:35 PM
To: List WAI GL
Subject: Minutes WCAG 15 September 2011


Minutes of the 15 September 2011 WCAG meeting are posted to http://www.w3.org/2011/09/15-wai-wcag-minutes.html and copied below.


Web Content Accessibility Guidelines Working Group Teleconference


15 Sep 2011


Agenda <http://lists.w3.org/Archives/Public/w3c-wai-gl/2011JulSep/0159.html> 

See also: IRC log <http://www.w3.org/2011/09/15-wai-wcag-irc> 


Attendees


	Present 
	Michael_Cooper, Mary_Utt, Katie_Haritos-Shea, Jon_Gunderson, Kathy_Wahlbin, David_MacDonald, Loretta_Guarino_Reid, +1.502.580.aaaa, Elle_Waters, Gregg_Vanderheiden, Marc_Johlic, Andrew_Kirkpatrick 
	Regrets 
	Tim_Boland 
	Chair 
	Loretta_Guarino_Reid 
	Scribe 
	marcjohlic 


Contents


*	Topics <http://www.w3.org/2011/09/15-wai-wcag-minutes.html#agenda>  

	1.	Issue LC-2490: Excessive use of clicking to navigate a website <http://www.w3.org/2011/09/15-wai-wcag-minutes.html#item01>  
	2.	Issue LC-2493: T3: Using standard text formatting conventions for headings <http://www.w3.org/2011/09/15-wai-wcag-minutes.html#item02>  
	3.	Issue LC-2551: H91, Example 6: 'selected' attribute <http://www.w3.org/2011/09/15-wai-wcag-minutes.html#item03>  
	4.	Issue LC-2555: H91, Example 3: value attribute <http://www.w3.org/2011/09/15-wai-wcag-minutes.html#item04>  
	5.	Issue LC-2492: F60 may either apply also to SC 3.2.2 (On Input) or need further specification (context change announced/expected, window type) <http://www.w3.org/2011/09/15-wai-wcag-minutes.html#item05>  
	6.	Issue LC-2496: "should" vs "must" <http://www.w3.org/2011/09/15-wai-wcag-minutes.html#item06>  
	7.	Issue LC-2537: Reflow and Order panel can not guarantee the reading order <http://www.w3.org/2011/09/15-wai-wcag-minutes.html#item07>  
	8.	Issue LC-2546: Embedded Flash content <http://www.w3.org/2011/09/15-wai-wcag-minutes.html#item08>  

*	Summary of Action Items <http://www.w3.org/2011/09/15-wai-wcag-minutes.html#ActionSummary>  

________________________________

<trackbot> Date: 15 September 2011

<scribe> scribe: marcjohlic


Issue LC-2490: Excessive use of clicking to navigate a website


RESOLUTION: Accepted as proposed


Issue LC-2493: T3: Using standard text formatting conventions for headings


RESOLUTION: Accepted as proposed


Issue LC-2551: H91, Example 6: 'selected' attribute


RESOLUTION: Accepted as proposed


Issue LC-2555: H91, Example 3: value attribute


RESOLUTION: Accepted as proposed


Issue LC-2492: F60 may either apply also to SC 3.2.2 (On Input) or need further specification (context change announced/expected, window type)


<greggvanderheiden> http://tinyurl.com/5rel6s6

<greggvanderheiden> http://tinyurl.com/5rel6s6

<MichaelC> ACTION: detlev to create failure technique for SC 3.2.2 to address coment LC-2492 [recorded in http://www.w3.org/2011/09/15-wai-wcag-minutes.html#action01]

<trackbot> Created ACTION-150 - Create failure technique for SC 3.2.2 to address coment LC-2492 [on Detlev Fischer - due 2011-09-22].

<MichaelC> action-150?

<trackbot> ACTION-150 -- Detlev Fischer to create failure technique for SC 3.2.2 to address coment LC-2492 -- due 2011-09-22 -- OPEN

<trackbot> http://www.w3.org/WAI/GL/track/actions/150

RESOLUTION: Accepted as amended


Issue LC-2496: "should" vs "must"


<awk> maybe in the non-normative documents we could link to the definition of these terms and tell people that they MUST read them...

<Loretta> http://www.w3.org/WAI/GL/2011/WD-WCAG20-TECHS-20110621/G141.html

<David> 100 musts in Techniques doc

<David> 1. Used to indicate obligation, duty, or correctness, typically when criticizing someone's actions: "he should have been careful".

<David> 2. Indicating a desirable or expected state: "by now students should be able to read".

<Loretta> We have added a discussion of the uses of "must" and "should" in techniques to the introduction to the Techniques document. We hope that this will clarify interpretations of the techniques. "Must" and "should" are not used in a normative way in WCAG itself, and since WCAG has 3 levels of conformance, the RFC 2119 definitions cannot be used in that context anyway. Please let us know whether this still leaves misinterpretations in our uses of these terms.

<Loretta> Since WCAG has 3 levels of conformance, "must" and "should" cannot be used as in the RFC 2119 definitions.

<David> Since WCAG has 3 levels of conformance, although "must" and "should" cannot are used as in the RFC 2119 definitions, it is not an exact mapping.

<David> Since WCAG has 3 levels of conformance, although "must" and "should" are used as in the RFC 2119 definitions, it is not an exact mapping.

<Loretta> We use "must" and "should" in ways that are similar to RFC 2119, although since WCAG has 3 levels of conformance, we cannot reference those definitions directly.

<Loretta> We have added a discussion of the uses of "must" and "should" in techniques to the introduction to the Techniques document. We hope that this will clarify interpretations of the techniques. We use "must" and "should" in ways that are similar to RFC 2119, although since WCAG has 3 levels of conformance, we cannot reference those definitions directly. Please let us know whether this still leaves misinterpretations in our uses of these terms.

<greggvanderheiden> We are not using RFC 2119 in our standard because it cannot be applied in a standard like ours with 3 levels of conformance.

RESOLUTION: Accepted as modified


Issue LC-2537: Reflow and Order panel can not guarantee the reading order


<awk> Note: Reordering content with the reading order is most appropriate for simple text content within a PDF since modifications made with the order panel can affect not only the reading order but the underlying structure of content contained within the PDF. This may impact the z-order for content on a page, including making some content become hidden behind other content. Authors should save their work before using the order panel and verify that the changes do

<awk> http://help.adobe.com/en_US/acrobat/pro/using/WS58a04a822e3e50102bd615109794195ff-7ce6.w.html

<awk> Authors are encouraged to refer to the PDF technology notes (http://trace.wisc.edu/wcag_wiki/index.php?title=PDF_Technology_Notes) <http://trace.wisc.edu/wcag_wiki/index.php?title=PDF_Technology_Notes%29>  for links to other resources for authoring and editing PDF documents for accessibility.

RESOLUTION: Leaving open - assigned to Mary


Issue LC-2546: Embedded Flash content


RESOLUTION: Accepted as modified (Michael's addition and Gregg's note)


Summary of Action Items

[NEW] ACTION: detlev to create failure technique for SC 3.2.2 to address coment LC-2492 [recorded in http://www.w3.org/2011/09/15-wai-wcag-minutes.html#action01]
 
[End of minutes]

________________________________

Minutes formatted by David Booth's scribe.perl <http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm>  version 1.136 (CVS log <http://dev.w3.org/cvsweb/2002/scribe/> )
$Date: 2011/09/15 21:33:32 $
-- 


Michael Cooper
Web Accessibility Specialist
World Wide Web Consortium, Web Accessibility Initiative
E-mail cooper@w3.org <mailto:cooper@w3.org> 
Information Page <http://www.w3.org/People/cooper/>