W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2011

Minutes WCAG 13 January 2011

From: Michael Cooper <cooper@w3.org>
Date: Fri, 14 Jan 2011 08:22:33 -0500
Message-ID: <4D304E19.2010400@w3.org>
To: List WAI GL <w3c-wai-gl@w3.org>
Minutes of the 13 January 2011 WCAG meeting are posted to
http://www.w3.org/2011/01/13-wai-wcag-minutes.html and copied below.


  - DRAFT -


  Web Content Accessibility Guidelines Working Group Teleconference


    13 Jan 2011

Agenda <http://lists.w3.org/Archives/Public/w3c-wai-gl/2011JanMar/0002.html>

See also: IRC log <http://www.w3.org/2011/01/13-wai-wcag-irc>


    Attendees

Present
    Michael_Cooper, Bruce_Bailey, Wolf_Schmidt, Loretta, Adam_Solomon,
    +1.727.391.aaaa, Marc_Johlic, Tim_Boland
Regrets
    Gregg_Vanderheiden, James_Nurthen, Mary_Utt, Andrew_Kirkpatrick,
    David_MacDonald
Chair
    Loretta_Guarino_Reid
Scribe
    marcjohlic


    Contents

    * Topics <http://www.w3.org/2011/01/13-wai-wcag-minutes.html#agenda>
         1. Advisory Silverlight Technique for SC 1.1.1, 3.3.2:
            Providing User Instructions With
            AutomationProperties.HelpText in Silverlight
            <http://www.w3.org/2011/01/13-wai-wcag-minutes.html#item01>
         2. Sufficient Silverlight Technique for SC 3.1.2: Declaring
            Discrete Silverlight Objects to Specify Language Parts in
            the HTML DOM
            <http://www.w3.org/2011/01/13-wai-wcag-minutes.html#item02>
         3. Advisory Silverlight Technique for SC 3.1.2: Understanding
            Language/Culture Properties as Used by Silverlight
            Applications and Assistive Technologies
            <http://www.w3.org/2011/01/13-wai-wcag-minutes.html#item03>
         4. Sufficient Silverlight Technique for SC 4.1.2: Understanding
            the Accessibility Roles of Silverlight Text Elements
            <http://www.w3.org/2011/01/13-wai-wcag-minutes.html#item04>
         5. Sufficient Silverlight Technique for SC 1.4.5: Using
            Silverlight Font Properties to Control Text Presentation,
            and Avoid Images of Text
            <http://www.w3.org/2011/01/13-wai-wcag-minutes.html#item05>
         6. Extend to SC 1.3.2 : Silverlight Technique "Using the
            Silverlight Default Tab Sequence and Altering Tab Sequences
            With Properties"
            <http://www.w3.org/2011/01/13-wai-wcag-minutes.html#item06>
         7. Silverlight Technology Notes
            <http://www.w3.org/2011/01/13-wai-wcag-minutes.html#item07>
    * Summary of Action Items
      <http://www.w3.org/2011/01/13-wai-wcag-minutes.html#ActionSummary>

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

<trackbot> Date: 13 January 2011

<adam> this is adam i have a problem with mic

<MichaelC> Scribe List <http://www.w3.org/WAI/GL/wiki/Scribe_List>

<scribe> scribe: marcjohlic


      Advisory Silverlight Technique for SC 1.1.1, 3.3.2: Providing User
      Instructions With AutomationProperties.HelpText in Silverlight

*RESOLUTION: Accepted as an advisory technique*


      Sufficient Silverlight Technique for SC 3.1.2: Declaring Discrete
      Silverlight Objects to Specify Language Parts in the HTML DOM

*RESOLUTION: Accepted as propsed*


      Advisory Silverlight Technique for SC 3.1.2: Understanding
      Language/Culture Properties as Used by Silverlight Applications
      and Assistive Technologies

*RESOLUTION: Accepted as an advisory technique*


      Sufficient Silverlight Technique for SC 4.1.2: Understanding the
      Accessibility Roles of Silverlight Text Elements

<adam> is it semantically correct to have simple text marked up as a
control?

<adam> rock and hard place

<adam> perhaps we could leave out discussion of textblock, or at least
minimize its mention as much as possible to make it more of a note

<adam> or perhaps mentioning the word "controls" in the title to avoid
specific mention of all the controls

<Loretta> zakim who is making noise?

<adam> "Example 2: All three text containers " - should we leave out?

<adam> i still am uncomfortable with the title of the eample 2 section

<Loretta> Adam, can you suggest a better title?

<adam> never mind - i am ok with it.

<adam> My only concern is that someone will go straight to example 2

<adam> and think it is a legitimate element to be used

<adam> thats fine

*RESOLUTION: Accepted as amended*


      Sufficient Silverlight Technique for SC 1.4.5: Using Silverlight
      Font Properties to Control Text Presentation, and Avoid Images of Text

<adam> ill look it over for a minute

<adam> wait

<Loretta> ok, adam!

<adam> i think it could be left in...

<adam> if we enhance the discussion in the description...

<adam> the reason i think so is because this is adefinite pitfall

<adam> which is common

<adam> one sec

<adam> great

*RESOLUTION: Accepted as amended*


      Extend to SC 1.3.2 : Silverlight Technique "Using the Silverlight
      Default Tab Sequence and Altering Tab Sequences With Properties"

<adam> the problem of non focusable elements is very important

<adam> not off the bat - need a little research

<adam> ok

<adam> traditionally tab sequence relates to focusable controls, so I
agree with Wolf that the issue of non focusable controls is not so
relevant to this technique

<scribe> *ACTION:* ITEM to Loretta & Wolfe to investigate Silverlight
failure of including non-focusable content. [recorded in
http://www.w3.org/2011/01/13-wai-wcag-minutes.html#action01]

<trackbot> Sorry, couldn't find user - ITEM

<scribe> *ACTION:* Loretta investigate Silverlight failure of including
non-focusable content. [recorded in
http://www.w3.org/2011/01/13-wai-wcag-minutes.html#action02]

<trackbot> Created ACTION-116 - Investigate Silverlight failure of
including non-focusable content. [on Loretta Guarino Reid - due 2011-01-20].

<scribe> *ACTION:* Wolfe investigate Silverlight failure of including
non-focusable content. [recorded in
http://www.w3.org/2011/01/13-wai-wcag-minutes.html#action03]

<trackbot> Sorry, couldn't find user - Wolfe

<scribe> *ACTION:* Wolf investigate Silverlight failure of including
non-focusable content. [recorded in
http://www.w3.org/2011/01/13-wai-wcag-minutes.html#action04]

<trackbot> Created ACTION-117 - Investigate Silverlight failure of
including non-focusable content. [on Wolf Schmidt - due 2011-01-20].

*RESOLUTION: Accepted as amended*


      Silverlight Technology Notes

<adam> i'm signing out - good night!

*RESOLUTION: Accepted as amended*

TENTATIVE GOAL: Update the Editor's Draft by end of Feb 2011

<MichaelC> trackbot, end meeting


    Summary of Action Items

*[NEW]* *ACTION:* ITEM to Loretta & Wolfe to investigate Silverlight
failure of including non-focusable content. [recorded in
http://www.w3.org/2011/01/13-wai-wcag-minutes.html#action01]
*[NEW]* *ACTION:* Loretta investigate Silverlight failure of including
non-focusable content. [recorded in
http://www.w3.org/2011/01/13-wai-wcag-minutes.html#action02]
*[NEW]* *ACTION:* Wolf investigate Silverlight failure of including
non-focusable content. [recorded in
http://www.w3.org/2011/01/13-wai-wcag-minutes.html#action04]
*[NEW]* *ACTION:* Wolfe investigate Silverlight failure of including
non-focusable content. [recorded in
http://www.w3.org/2011/01/13-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.135 (CVS log <http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2011/01/13 22:52:11 $


-- 

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 Friday, 14 January 2011 13:22:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 14 January 2011 13:22:57 GMT