See also: IRC log
<trackbot> Date: 21 June 2012
<scribe> scribeNick: jamesn
https://www.w3.org/2002/09/wbs/35422/WCAG2ICT2/
<greggvanderheiden> WCAG was designed to apply only to controls that were displayed on a web page. The intent was to avoid describing controls solely via references to visual or auditory cues. When applying this to instructions for operating physical hardware controls (e.g. a web kiosk with dedicated content), tactile cues on the hardware might be described (e.g. the arrow shaped key, the round key on the right side). This success criterion is not intended to
<greggvanderheiden> prevent the use of tactile cues in instructions.
<greggvanderheiden> Add the following to the intent of SC 1.3.3 in Understanding WCAG: WCAG was designed to apply only to controls that were displayed on a web page. The intent was to avoid describing controls solely via references to visual or auditory cues. When applying this to instructions for operating physical hardware controls (e.g. a web kiosk with dedicated content), tactile cues on the hardware might be described (e.g. the arrow shaped key, the
<greggvanderheiden> round key on the right side). This success criterion is not intended to prevent the use of tactile cues in instructions.
RESOLUTION: Add the text above to SC1.3.3 in Understanding WCAG2
<greggvanderheiden> Add the following note to the INTENT section of SC 2.4.6. Note: This success criterion does not REQUIRE heading and labels, just that, if they are provided, they be descriptive. Also note that, if headings are provided, they must be programmatically determinable per 1.3.1.
RESOLUTION: Add Note to 2.4.6 Understanding doc - "Note: This success criterion does not REQUIRE heading and labels, just that, if they are provided, they be descriptive. Also note that, if headings are provided, they must be programmatically determinable per 1.3.1."
<greggvanderheiden> The following sentence be added to the INTENT section of SC 3.2.1
<greggvanderheiden> Note: What is meant by 'component' here is also sometimes called 'user interface element' or 'user interface component'. -- And -- the following sentence be added to the INTENT section of SC 3.2.2. Note: What is meant by 'component' and 'user interface component' here is also sometimes called 'user interface element'.
<greggvanderheiden> The following sentence be added to the INTENT section of SC 3.2.1 Note: What is meant by 'component' here is also sometimes called 'user interface element' or 'user interface component'. -- And -- the following sentence be added to the INTENT section of SC 3.2.2. Note: What is meant by 'component' and 'user interface component' here is also sometimes called 'user interface element'.
RESOLUTION: The following sentence be added to the INTENT section of SC 3.2.1 Note: What is meant by 'component' here is also sometimes called 'user interface element' or 'user interface component'. -- And -- the following sentence be added to the INTENT section of SC 3.2.2. Note: What is meant by 'component' and 'user interface component' here is also sometimes called 'user interface element'.
<greggvanderheiden> That the erratum for WCAG 2.0 reflect that in SC 3.2.1 the word component should be changed to “user interface component” and the following note added to the definition: Note: What is meant by 'component' or 'user interface component' here is also sometimes called 'user interface element'.
RESOLUTION: That the erratum for WCAG 2.0 reflect that in SC 3.2.1 the word component should be changed to �user interface component� and the following note added to the definition: Note: What is meant by 'component' or 'user interface component' here is also sometimes called 'user interface element'.
<MichaelC> WCAG 2.0 Errata
<greggvanderheiden> Add to errata “fix the link for “set of web pages” in SC 3..2.4 to point to the “set of web pages” definition instead of “Web Pages” and add to INTENT – “Note: the link above to Web pages should have been a link to “set of web pages”.
RESOLUTION: Add to errata �fix the link for �set of web pages� in SC 3.2.4 to point to the �set of web pages� definition instead of �Web Pages� and add to INTENT � �Note: the link above to Web pages should have been a link to �set of web pages�.
<greggvanderheiden> a b
<greggvanderheiden> Note: if labels are provided, the label relationship to the object labeled must be programmatically determined or described in text per SC 1.3.1.
<greggvanderheiden> queue
<greggvanderheiden> queue
RESOLUTION: Add note to 3.3.2 of " Note: if labels are provided, the label relationship to the object labeled must be programmatically determined or described in text per SC 1.3.1."
<greggvanderheiden> If authors do not write or edit markup languages directly they can assume this provision is met.
<David> scribe:David
RESOLUTION: : the WCAG group does not accept the following note: If authors do not write or edit markup languages directly they can assume this provision is met.
<greggvanderheiden> This is not meant to apply to markup languages that are not parsed by general purpose web browsers and assistive technologies.
RESOLUTION: The working group agrees with the sentiment but cannot find the right wording so returns it... for more consideration. "This is not meant to apply to markup languages that are not parsed by general purpose web browsers and assistive technologies."
https://www.w3.org/2002/09/wbs/35422/20120621_PF-UA/results
<greggvanderheiden> NOTE: With the exception of one success criterion (1.4.4 - that specifically mentions that the effect specified by the success criterion must be achieved without relying on an assistive technology) authors can meet the success criteria with content that assumes use of an assistive technology (or access features in use agents) by the user, where such assistive technologies (or access features in user agents) exist and are available to the
<greggvanderheiden> user.
RESOLUTION: add the
note... NOTE: With the exception of one success criterion
(1.4.4 - that specifically mentions that the effect specified
by the success criterion must be achieved without relying on an
assistive technology) authors can meet the success criteria
with content that assumes use of an assistive technology (or
access features in use agents) by the user, where such
assistive...
... technologies (or access features in user agents) exist and
are available to the user.
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/resolution/Resolution/ Succeeded: s/Resolution/RESOLUTION:/ Found ScribeNick: jamesn Found Scribe: David Inferring ScribeNick: David ScribeNicks: jamesn, David Default Present: Bruce_Bailey, Cooper, Peter_Korn, Andi_Snow_Weaver, Gregg_Vanderheiden, Marc_Johlic, David_MacDonald, Adam_Solomon, James_Nurthen Present: Bruce_Bailey Cooper Peter_Korn Andi_Snow_Weaver Gregg_Vanderheiden Marc_Johlic David_MacDonald Adam_Solomon James_Nurthen Regrets: Loretta_Guarino_Reid Moe_Kraft Kathleen_Wahlbin Found Date: 21 Jun 2012 Guessing minutes URL: http://www.w3.org/2012/06/21-wai-wcag-minutes.html People with action items:[End of scribe.perl diagnostic output]