Minutes WCAG 09 Aug 2012

Minutes of the 9 August 2012 WCAG meeting are posted to
http://www.w3.org/2012/08/09-wai-wcag-minutes.html and copied below.


  Web Content Accessibility Guidelines Working Group Teleconference


    09 Aug 2012

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

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


    Attendees

Present
    Katie_Haritos-Shea, Cooper, Peter_Korn, David_MacDonald,
    Bruce_Bailey, Gregg_Vanderheiden, James_Nurthen, +1.206.544.aaaa,
    Robin_Tuttle, Alex_Li, Marc_Johlic, Loretta_Guarino_Reid, adam_solomon
Regrets
    Kathleen_Wahlbin
Chair
    Loretta_Guarino_Reid
Scribe
    robin


    Contents

    * Topics <http://www.w3.org/2012/08/09-wai-wcag-minutes.html#agenda>
         1. Question from WAI-ARIA Task Force: Examples in WAI-ARIA
            techniques
            <http://www.w3.org/2012/08/09-wai-wcag-minutes.html#item01>
         2. Question from WAI-ARIA Task Force: Direction on ARIA states
            technique
            <http://www.w3.org/2012/08/09-wai-wcag-minutes.html#item02>
         3. 3.1.1 Guidance - submitted for approval
            <http://www.w3.org/2012/08/09-wai-wcag-minutes.html#item03>
         4. 3.1.2 Guidance - submitted for approval
            <http://www.w3.org/2012/08/09-wai-wcag-minutes.html#item04>
         5. 4.1.2 -- Approval of a note to Task Force Guidance for 4.1.2
            <http://www.w3.org/2012/08/09-wai-wcag-minutes.html#item05>
    * Summary of Action Items
      <http://www.w3.org/2012/08/09-wai-wcag-minutes.html#ActionSummary>

------------------------------------------------------------------------

<trackbot> Date: 09 August 2012

<MichaelC> Miscellaneous issues for 09 Aug 2012
<https://www.w3.org/2002/09/wbs/35422/20120809misc/results>


      Question from WAI-ARIA Task Force: Examples in WAI-ARIA techniques

*RESOLUTION: Question from WAI-ARIA Task Force: Examples in WAI-ARIA
techniques - there will be a discussion of this issue in the ARIA
technology notes. Examples that seem to contradict using semantic
controls when available will include a link back to that discussion.*

<jamesn> *ACTION:* jamesn to Create a Note for the WAI-ARIA techniques
so that examples which seem to contradict the "use semantic elements"
statement in the aria spec can refer to [recorded in
http://www.w3.org/2012/08/09-wai-wcag-minutes.html#action01]

<trackbot> Created ACTION-176 - Create a Note for the WAI-ARIA
techniques so that examples which seem to contradict the "use semantic
elements" statement in the aria spec can refer to [on James Nurthen -
due 2012-08-16].

<MichaelC> action-176?

<trackbot> ACTION-176 -- James Nurthen to create a Note for the WAI-ARIA
techniques so that examples which seem to contradict the "use semantic
elements" statement in the aria spec can refer to -- due 2012-08-16 -- OPEN

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

To the action, people can add thoughts to the action in the add notes field


      Question from WAI-ARIA Task Force: Direction on ARIA states technique

<adam> http://www.w3.org/TR/WCAG-TECHS/H91

<MichaelC> (btw choose "edit this action" first to get to the "Add
notes" field)

Question from WAI-ARIA Task Force: Direction on ARIA states technique –
Feedback for taskforce: explore combining a broad general technique on
states with more target techniques for different roles or classes of states


      3.1.1 Guidance - submitted for approval

<korn1> Where software platforms provide a "locale/language" setting,
applications that user that setting and render their interface in that
"locale/language" would comply with this success criterion.

<Zakim> MichaelC, you wanted to ask about if application doesn't support
the system's language

<korn1> Where software platforms provide a "locale/language" setting,
applications that use that setting and render their interface in that
"locale/language" would comply with this success criterion. Applications
that do not use the platform "locale/language setting" but instead use
an accessibility supported method for exposing the human language of the
software user interface would also comply with this success criterion.
Applications implemented in technologi

<korn1> Last sentence (slightly further modified): "Applications
implemented in technologies where Assistive technologies cannot
determine the human language and that do not support the platform
"locale/language" setting may not be able to meet this success criterion
in that locale/language."

<korn1>
https://sites.google.com/site/wcag2ict/home/3-understandable/31-make-text-content-readable-and-understandable/311-language-of-page

<korn1> See "New text discussed in WCAG WG in 9Aug12:"

<MichaelC> *ACTION:* cooper to write up language for WCAG2ICT support
for 3.1.1 that explains the conformance if the OS is set to one
language, the application doesn't support that and falls back to
another, and has no way to inform user that there is a desynchronicity
[recorded in http://www.w3.org/2012/08/09-wai-wcag-minutes.html#action02]

<trackbot> Created ACTION-177 - Write up language for WCAG2ICT support
for 3.1.1 that explains the conformance if the OS is set to one
language, the application doesn't support that and falls back to
another, and has no way to inform user that there is a desynchronicity
[on Michael Cooper - due 2012-08-16].

*RESOLUTION: 3.1.1 Guidance - submitted for approval – Accepted as
amended here
https://sites.google.com/site/wcag2ict/home/3-understandable/31-make-text-content-readable-and-understandable/311-language-of-page
See New text discussed in WCAG WG on 9Aug12*


      3.1.2 Guidance - submitted for approval

<Loretta> *ACTION:* peter to clarify role of inheritance in 3.1.2
Understanding Document with respect to nested elements. [recorded in
http://www.w3.org/2012/08/09-wai-wcag-minutes.html#action03]

<trackbot> Created ACTION-178 - Clarify role of inheritance in 3.1.2
Understanding Document with respect to nested elements. [on Peter Korn -
due 2012-08-16].

<korn1>
https://sites.google.com/site/wcag2ict/home/3-understandable/31-make-text-content-readable-and-understandable/312-language-of-parts

*RESOLUTION: 3.1.2 Guidance - submitted for approval – accept as amended
here
https://sites.google.com/site/wcag2ict/home/3-understandable/31-make-text-content-readable-and-understandable/312-language-of-parts
see “From WCAG WG meeting on 9Aug12:”*


      4.1.2 -- Approval of a note to Task Force Guidance for 4.1.2

*RESOLUTION: 4.1.2 -- Approval of a note to Task Force Guidance for
4.1.2 - accepted as proposed*

<greggvanderheiden> got dropped but no matter. thanks eveyone


    Summary of Action Items

*[NEW]* *ACTION:* cooper to write up language for WCAG2ICT support for
3.1.1 that explains the conformance if the OS is set to one language,
the application doesn't support that and falls back to another, and has
no way to inform user that there is a desynchronicity [recorded in
http://www.w3.org/2012/08/09-wai-wcag-minutes.html#action02]
*[NEW]* *ACTION:* jamesn to Create a Note for the WAI-ARIA techniques so
that examples which seem to contradict the "use semantic elements"
statement in the aria spec can refer to [recorded in
http://www.w3.org/2012/08/09-wai-wcag-minutes.html#action01]
*[NEW]* *ACTION:* peter to clarify role of inheritance in 3.1.2
Understanding Document with respect to nested elements. [recorded in
http://www.w3.org/2012/08/09-wai-wcag-minutes.html#action03]
 
[End of minutes]
------------------------------------------------------------------------
Minutes formatted by David Booth's scribe.perl
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/scribe/scribedoc.htm>
version 1.136 (CVS log <http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2012/08/09 21:33:31 $


-- 

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/>

Received on Monday, 13 August 2012 13:29:45 UTC