See also: IRC log
<trackbot> Date: 15 September 2011
<scribe> scribe: marcjohlic
RESOLUTION: Accepted as proposed
RESOLUTION: Accepted as proposed
RESOLUTION: Accepted as proposed
RESOLUTION: Accepted as proposed
<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
<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
<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) for links to other resources for authoring and editing PDF documents for accessibility.
RESOLUTION: Leaving open - assigned to Mary
RESOLUTION: Accepted as modified (Michael's addition and Gregg's note)
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) Succeeded: s/our/ours/ Found Scribe: marcjohlic Inferring ScribeNick: marcjohlic Default 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 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 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2011JulSep/0159.html Found Date: 15 Sep 2011 Guessing minutes URL: http://www.w3.org/2011/09/15-wai-wcag-minutes.html People with action items: detlev[End of scribe.perl diagnostic output]