W3C

- DRAFT -

Web Content Accessibility Guidelines Working Group Teleconference

13 Jan 2011

Agenda

See also: IRC log

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


<trackbot> Date: 13 January 2011

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

<MichaelC> 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 version 1.135 (CVS log)
$Date: 2011/01/13 22:52:11 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: marcjohlic
Inferring ScribeNick: marcjohlic
Default Present: Michael_Cooper, Bruce_Bailey, Wolf_Schmidt, Loretta, Adam_Solomon, +1.727.391.aaaa, Marc_Johlic, Tim_Boland
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
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2011JanMar/0002.html
Found Date: 13 Jan 2011
Guessing minutes URL: http://www.w3.org/2011/01/13-wai-wcag-minutes.html
People with action items: item loretta wolf wolfe

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]