See also: IRC log
<trackbot> Date: 28 September 2012
<scribe> scribe: MaryJo
<Pierce> +q
Discussion on the note for 3.3.1 and how to make it more succinct as shown in proposal #6.
What constitutes sufficient information given to the user? Sometimes the error message provided will cover both SC 3.3.1 and 3.3.3.
The text must be both programmatically determinable and visible text.
<Pierce> +q
<korn1> Enter a value between 3 & 5: [ ]
<Pierce> +q
If the user enters a value of 2, the value is automatically changed to a 3 and the '3' is only visually styled to indicate it shows up.
Members of WCAG would probably say that this example doesn't pass the 3.3.1 SC because a description of the input error was not given to the user in text.
Mainframes don't have the ability to notify the user of an error such as this. So it isn't possible to implement in some software.
The level A, AA, and AAA were set by WCAG based on both importance as well as implementability.
<Pierce> mainframes are a current technology
<Loic> q
<Andi> the proposal being discussed is Proposal #6
We can't say it doesn't apply to software when not all technologies can support it.
<Andi> If a user enters a value that is too high or too low, and the coding on the page automatically changes that value to fall within the allowed range, the user's error would still need to be described to them as required by the success criterion.
<korn1> Consider adding: "This error description and new changed value may also address SC 3.3.1"
<korn1> Or "Such an error description and new changed value..."
<Pierce> +1
<Pierce> +1
<Pierce> +q
<greggvanderheiden> If a user enters a value that is too high or too low, and the coding on the page automatically changes that value to fall within the allowed range, the user's error would still need to be described to them as required by the success criterion. Such an error description telling the person of the changed value would meet both this this success criterion (Error identification) and success criterion 3.3.3 (Error Suggestion).
<Pierce> +1
<Pierce> +1+1
RESOLUTION: Accept 3.3.1 proposal 6 as written.
https://www.w3.org/2002/09/wbs/55145/SEP262012/results#xq2
We'll skip this because edits are not found in 2.2.1.
https://www.w3.org/2002/09/wbs/55145/SEP262012/results#xq3
RESOLUTION: Accept note to be sent to WCAG for 3.3.4 as written.
<korn1> +1 Gregg - that's fine.
<Pierce> +1
<Pierce> + q
<Pierce> -1
<Pierce> +q
<Pierce> +1
<Andi> Accept proposal on 2.2.1 Timing Adjustable labeled "Send the following to WCAG" for 2.2.1, 2.2.2, and 2.2.3
RESOLUTION: Accept proposal on 2.2.1 Timing Adjustable labeled "Send the following to WCAG" for 2.2.1, 2.2.2, and 2.2.3.
Andi is currently not being notified when a proposal is ready, so you need to send an email to tell her when the proposed resolution is ready for survey.
Would like for the 'assigned' field to be changed to the person that is working on the proposal.
https://www.w3.org/2002/09/wbs/55145/SEP262012/results#xq4
<korn1> +1 to MaryJo's text.
Responses to these comments will always be preceded by a polite introduction and thank you for your comment, so reading the response by itself may seem abrupt on its own but will be toned down by the introduction.
<Pierce> +q
Some of the language from some of the other responses could be added to this, but would have to review the other comments to determine the details.
<korn1> +1
RESOLUTION: Accept the proposed resolution as amended in LC-2663.
<Pierce> Here is a good statement to consider for this and other "SW won't fit" comments...or something similar
<Pierce> We agree that additional requirements are needed especially for software acting in platform role(s). However, we are not charged with determining what the overall requirements for ICT should be. As you point out, these are the purview of the US Access Board and the EU M376 standards development team.
https://www.w3.org/2002/09/wbs/55145/SEP262012/results#xq13
This comment is going to the same person as the previous issue.
RESOLUTION: Accept the proposed resolution to LC 2672.
Combine LC-2672 - Applying WCAG to non-web ICT is an overreach with the previous one LC-2663.
https://www.w3.org/2002/09/wbs/55145/SEP262012/results#xq5
<Mike> +1
<korn1> +1 to that.
Proposal was made to edit the response to include groups' comments.
RESOLUTION: Accept LC-2655 as amended.
<korn1> +1 Andi
https://www.w3.org/2002/09/wbs/55145/SEP262012/results#xq6
<korn1> +1 to the text
RESOLUTION: Accept LC-2692 as amended.
https://www.w3.org/2002/09/wbs/55145/SEP262012/results#xq7
RESOLUTION: Accept LC-2657 as amended.
RESOLUTION: Accept LC-2668 as amended.
RESOLUTION: Accept LC-2690 as amended.
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/programmatically determinable text./both programmatically determinable and visible text./ Succeeded: s/Resolution: Accept the proposed resolution to LC 2672./RESOLUTION: Accept the proposed resolution to LC 2672./ Succeeded: s/2665/2655/ Succeeded: s/zakim, make minutes// Succeeded: s/RESOLUTION: Accept LC-2690 as amended.// Succeeded: s/LC-2655/LC-2655 - Why no acknowledgement of MSAA, IAccessible2, iOS VoiceOver, ... etc./ Succeeded: s/LC-2672/LC-2672 - Applying WCAG to non-web ICT is an overreach/ Succeeded: s/Accept LC-2655 - Why no acknowledgement of MSAA, IAccessible2, iOS VoiceOver, ... etc. as/Accept LC-2655 as/ Succeeded: s/- Why no acknowledgement of MSAA, IAccessible2, iOS VoiceOver, ... etc.// Found Scribe: MaryJo Inferring ScribeNick: MaryJo Default Present: Andi_Snow_Weaver, Peter_Korn, Bruce_Bailey, Mary_Jo_Mueller, Shadi, Kiran_Kaja, Mike_Pluke, Judy, Pierce_Crowell, Gregg_Vanderheiden, Janina_Sajka, Loic_Martinez, David_MacDonald Present: Andi_Snow_Weaver Peter_Korn Bruce_Bailey Mary_Jo_Mueller Shadi Kiran_Kaja Mike_Pluke Judy Pierce_Crowell Gregg_Vanderheiden Janina_Sajka Loic_Martinez David_MacDonald Found Date: 28 Sep 2012 Guessing minutes URL: http://www.w3.org/2012/09/28-wcag2ict-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]