See also: IRC log
<trackbot> Date: 14 June 2012
<MichaelC> scribe: MoeKraft
<greggvanderheiden> https://www.w3.org/2002/09/wbs/35422/2012-06-14/results
<greggvanderheiden> This SC is not intended to require that two-way multimedia calls between individuals through web apps must be captioned regardless of the needs of users. Responsibility for providing captions would fall to the content providers (the callers) or the “host” caller, and not the application.
<greggvanderheiden> This SC is not intended to require that two-way multimedia calls between individuals through web apps must be captioned regardless of the needs of users. Responsibility for providing captions would fall to the content providers (the callers) or the “host” caller, and not the application.
<greggvanderheiden> This SC was intended to apply to broadcast of synchronized media and is not intended to require that two-way multimedia calls between individuals through web apps must be captioned regardless of the needs of users. Responsibility for providing captions would fall to the content providers (the callers) or the “host” caller, and not the application.
<greggvanderheiden> This SC was intended to apply to broadcast of synchronized media and is not intended to require that two-way multimedia calls between individuals through web apps must be captioned regardless of the needs of users. Responsibility for providing captions would fall to the content providers (the callers) or the “host” caller, and not the application.
<greggvanderheiden> This SC was intended to apply to broadcast of synchronized media and is not intended to require that two-way multimedia calls between two or more individuals through web apps must be captioned regardless of the needs of users. Responsibility for providing captions would fall to the content providers (the callers) or the “host” caller, and not the application.
<greggvanderheiden> This success criterion was intended to apply to broadcast of synchronized media and is not intended to require that two-way multimedia calls between two or more individuals through web apps must be captioned regardless of the needs of users. Responsibility for providing captions would fall to the content providers (the callers) or the “host” caller, and not the application.
RESOLUTION: To add the following to the understanding document for SC 1.2.4 This success criterion was intended to apply to broadcast of synchronized media and is not intended to require that two-way multimedia calls between two or more individuals through web apps must be captioned regardless of the needs of users. Responsibility for providing captions would fall to the content providers (the callers) or the “host” caller, and not the application.
<greggvanderheiden> This success criterion was intended to apply to broadcast of audio and is not intended to require that two-way audio calls between two or more individuals through web apps must be captioned regardless of the needs of users. Responsibility for providing captions would fall to the content providers (the callers) or the “host” caller, and not the application.
RESOLUTION: To add the following to the Understanding document for SC 1.2.9 This success criterion was intended to apply to broadcast of audio and is not intended to require that two-way audio calls between two or more individuals through web apps must be captioned regardless of the needs of users. Responsibility for providing captions would fall to the content providers (the callers) or the “host” caller, and not the application.
<greggvanderheiden> which element among multiple elements has the keyboard focus. If there is only one keyboard actionable control on the screen, the success criterion would be met because the visual design presents only one keyboard actionable item.
<greggvanderheiden> Note that a keyboard focus indicator can take different forms. One common way is a caret within the text field to indicate that the text field has the keyboard focus. Another is a visual change to a button to indicate that that button has the keyboard focus.
<greggvanderheiden> The purpose of this success criterion is to help a person know which element among multiple elements has the keyboard focus. If there is only one keyboard actionable control on the screen, the success criterion would be met because the visual design presents only one keyboard actionable item.
<greggvanderheiden> Note that a keyboard focus indicator can take different forms. One common way is a caret within the text field to indicate that the text field has the keyboard focus. Another is a visual change to a button to indicate that that button has the keyboard focus.
RESOLUTION: To Add
the following 2 paragraphs to Understanding document for SC
2.4.7 The purpose of this success criterion is to help a person
know which element among multiple elements has the keyboard
focus. If there is only one keyboard actionable control on the
screen, the success criterion would be met because the visual
design presents only one keyboard actionable
item.
... Note that a keyboard focus indicator can take different
forms. One common way is a caret within the text field to
indicate that the text field has the keyboard focus. Another is
a visual change to a button to indicate that that button has
the keyboard focus.
<greggvanderheiden> modify the end of the first paragraph of the INTENT of SC 3.3.4 to read: Likewise, it may be an unrecoverable error if users unintentionally modify or delete data stored in a database that they later need to access, such as their entire travel profile in a travel services web site. When referring to modification or deletion of 'user controllable' data, the intent is to prevent mass loss of data such as deleting a file or record. It is
<greggvanderheiden> not the intent to require a confirmation for each save command or the simple creation or editing of documents, records or other data.
<greggvanderheiden> https://sites.google.com/site/wcag2ict/
RESOLUTION: To
modify the end of the first paragraph of the INTENT of SC 3.3.4
to read: Likewise, it may be an unrecoverable error if users
unintentionally modify or delete data stored in a database that
they later need to access, such as their entire travel profile
in a travel services web site. When referring to modification
or deletion of 'user controllable' data, the intent is to
prevent mass loss of data such as deleting a file or
record.
... It is not the intent to require a confirmation for each
save command or the simple creation or editing of documents,
records or other data.
<MichaelC> Comment Tracker
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 Scribe: MoeKraft Inferring ScribeNick: MoeKraft Default Present: Bruce_Bailey, +1.206.544.aaaa, Marc_Johlic, Cooper, Alex_Li, Cherie_Eckholm, Robin_Tuttle, Gregg_Vanderheiden, +1.978.562.aabb, MoeKraft, Adam_Solomon, David_MacDonald, +1.617.584.aacc, Katie, Andrew_Kirkpatrick, James_Nurthen, Kathy, +1.613.806.aadd Present: Bruce_Bailey +1.206.544.aaaa Marc_Johlic Cooper Alex_Li Cherie_Eckholm Robin_Tuttle Gregg_Vanderheiden +1.978.562.aabb MoeKraft Adam_Solomon David_MacDonald +1.617.584.aacc Katie Andrew_Kirkpatrick James_Nurthen Kathy +1.613.806.aadd Agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2012AprJun/0098.html Found Date: 14 Jun 2012 Guessing minutes URL: http://www.w3.org/2012/06/14-wai-wcag-minutes.html People with action items:[End of scribe.perl diagnostic output]