W3C

- DRAFT -

Web Content Accessibility Guidelines Working Group Teleconference

20 Sep 2012

Agenda

See also: IRC log

Attendees

Present
Gregg_Vanderheiden, Bruce_Bailey, David_MacDonald, James_Nurthen, Cooper, Katie_Haritos-Shea, Marc_Johlic, Loretta_Guarino_Reid
Regrets
Kathy_Wahlbin
Chair
Loretta_Guarino_Reid
Scribe
jamesn

Contents


<trackbot> Date: 20 September 2012

<scribe> scribe: jamesn

<David> http://tinyurl.com/9b52rkr

Survey results - https://www.w3.org/2002/09/wbs/35422/20120920misc/results

<Loretta> http://www.w3.org/WAI/WCAG20/quickref/

<greggvanderheiden> Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. The techniques listed only satisfy the Success Criterion if all of the WCAG 2.0 conformance requirements have been met.

<greggvanderheiden> Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. However, it is not necessary to use these particular techniques.

<greggvanderheiden> Any techniques used only satisfy the Success Criterion if all of the WCAG 2.0 conformance requirements have been met.

<greggvanderheiden> Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. However, it is not necessary to use these particular techniques. Any techniques used only satisfy the Success Criterion if all of the WCAG 2.0 conformance requirements have been met.

<Loretta> The "sufficient techniques" listed below are considered sufficient to meet the success criteria; however, it is not necessary to use these particular techniques.

<greggvanderheiden> Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. However, it is not necessary to use these particular techniques.

<a href="#about-techs">Note: It is not necessary to use these techniques"</a>

<greggvanderheiden> Note: Other techniques may also be sufficient if they meet the success criterion.

<Loretta> <a href="#about-techs">Note: Other techniques may also be sufficient if they meet the success criterion.</a>

<Loretta> https://www.w3.org/2006/02/lc-comments-tracker/35422/NOTE-UNDERSTANDING-WCAG20-20120103/2630

RESOLUTION: Accept LC-2630 as amended at https://www.w3.org/2006/02/lc-comments-tracker/35422/NOTE-UNDERSTANDING-WCAG20-20120103/2630

<MichaelC> http://www.w3.org/TR/WCAG20-TECHS/H69

<greggvanderheiden> The User Agent Notes for H69 discuss the native support for navigating by headings that is provided in Opera, and notes that for other browsers, plugins may be needed. With all of our success criterion the assumption is that people needing special user agents (including AT or special plug-ins) to get the access they want, will get and be using that type user agent (eg screen reader, or plug-in that allows keyboard navigation of

<greggvanderheiden> properly marked up content, etc) .

<greggvanderheiden> This technique assumes that people needing special user agents (including AT or special plug-ins) to get the access they want, will get and be using that type user agent (eg screen reader, or plug-in that allows keyboard navigation of properly marked up content, etc) .

<greggvanderheiden> NOTE: All of our techniques assumes that people needing special user agents (including AT or special plug-ins) to get the access they want, will get and be using that type user agent (eg screen reader, or plug-in that allows keyboard navigation of properly marked up content, etc) .

<greggvanderheiden> NOTE: All of our techniques assume that people needing special user agents (including AT or special plug-ins) to get the access they want, will get and be using that type user agent (eg screen reader, or plug-in that allows keyboard navigation of properly marked up content, etc)

<Loretta> http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation.html

RESOLUTION: Accept LC-2624 as amended
... Accept LC-2685 as amended
... Accept LC-2684 as proposed

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2012/09/20 21:22:19 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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: jamesn
Inferring ScribeNick: jamesn

WARNING: No "Topic:" lines found.

Default Present: Gregg_Vanderheiden, Bruce_Bailey, David_MacDonald, James_Nurthen, Cooper, Katie_Haritos-Shea, Marc_Johlic, Loretta_Guarino_Reid
Present: Gregg_Vanderheiden Bruce_Bailey David_MacDonald James_Nurthen Cooper Katie_Haritos-Shea Marc_Johlic Loretta_Guarino_Reid
Regrets: Kathy_Wahlbin
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2012JulSep/0092.html
Found Date: 20 Sep 2012
Guessing minutes URL: http://www.w3.org/2012/09/20-wai-wcag-minutes.html
People with action items: 

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


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]