W3C

- DRAFT -

WCAG2ICT Task Force Teleconference

22 Mar 2013

Agenda

See also: IRC log

Attendees

Present
Mary_Jo_Mueller, David_MacDonald, Michael_Cooper, Mike_Pluke, Judy, Gregg_Vanderheiden, Kiran_Kaja, Peter_Korn, Bruce_Bailey
Regrets
Loic_Martinez_Normand, Andi_Snow_Weaver, Alex_Li
Chair
Mike_Pluke
Scribe
Mary_Jo_Mueller

Contents


<trackbot> Date: 22 March 2013

<Judy> trackbot, start meeting

<trackbot> Meeting: WCAG2ICT Task Force Teleconference

<trackbot> Date: 22 March 2013

<scribe> scribe: Mary_Jo_Mueller

<scribe> scribenick: MaryJo

Discuss the 'Closed Functionality - compare/contrast with M376' survey

https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/comparison-to-m376#TOC-Comparison-for-closed-list

https://www.w3.org/2002/09/wbs/55145/20130321/results

We want to make sure that we consense on any changes to our wording, not on any advice for M376.

The M376 team and access board are finding our observations and rationale valuable.

We will do cleanup of the individual notes in the tables so there isn't any information in there that shouldn't be in the final output.

The statements about what M376 'should do' will have to be cleaned out, as it appears to be pro-active efforts at reconciliation of active regulatory processes that is outside the scope of our task force.

The wiki is a work in progress, and the third column is useful for the discussions on what we need to do in the WCAG2ICT document.

The column before the last column with the suggestions, it was always the understanding this column will be deleted once our discussions are complete.

Actually 2 columns would be removed from the documentation and software tables: 1) where the initial observations and then 2) the survey compilation of comments.

When we're done, we'll have 5 columns left in each table.

WCAG2ICT should not be telling the regulatory groups what to do, nor creating the perception that they may be doing so. Even if we do this temporarily, it is a concern. This is beyond the scope of this task force.

There was an issue with timing of our work and the M376 work, and if there are things the group consenses on we can make a statement about our consensus.

Proposal that we remove anything in bold yellow at the end of our meeting today.

Proposal made to remove working notes for items we have closed and directions toward what M376 should do.

<korn> I propose I will make the following edits to the compare doc:

<korn> 1. change final column title to be "TF resolution, with dates"

<korn> 2. remove all boldface "suggestion" text from "Comparison" column

<korn> 3. Remove highlighted in yellow introductory text

<greggvanderheiden> To remove non-consensus language and any comments on what M376 should do.

Columns 1, 2, 3, 4 and the last column will be all that remains when we're done.

<greggvanderheiden> To remove any comments on what M376 should do and remove non-consensus language as we complete the items. Comments from individuals will be signed.

RESOLUTION: Task force agreed to remove any comments on what M376 should do and remove non-consensus language as we complete the items. Comments from individuals will be signed.

<phone> Closed Products survey SC 1.1.1 - the resolution that we document should be in the same format as the others.

<korn> WCAG2ICT text includes brief description noting the problematic issue with this SC for Closed Functionality. M376 notes a 5.x.y.z provision addressing the closed requirement raised by this SC.

<korn> No change. 

<korn> Rationale: WCAG2ICT does not have these additional provisions.

<korn> -22Mar13.

<phone> SC 1.2.1 - The original WCAG 2.0 SC (and our WCAG2ICT notes for the SC) isn't split, but M376 needed to split to cover 2 scenarios.

<korn> ===============================

<korn> WCAG2ICT text includes brief description noting the problematic issue with this SC for Closed Functionality. M376 notes a 5.x.y.z provision addressing the closed requirement raised by this SC.  M376 splits 1.2.1 into two parts

<korn> No change. 

<korn> Rationale: WCAG2ICT does not have these additional provisions.

<korn> -22Mar13.

WCAG2ICT doesn't include specific provisions for closed functionality.

<korn> ====== new rationale: Rationale: WCAG2ICT does not have specific provisions for closed functionality. =======

<korn> ========================

<korn> WCAG2ICT text includes brief description noting the problematic issue with this SC for Closed Functionality. M376 notes a 5.x.y.z provision addressing the closed requirement raised by this SC.  M376 splits 1.2.1 into two parts

<korn> No change. 

<korn> Rationale: WCAG2ICT does not have specific provisions for closed functionality. 

<korn> -22Mar13.

<korn> =====================

1.2.1 a and b would have the above comment.

SC 1.2.3 - this has some 'should' language that needs to be removed.

<korn> ==============

<korn> WCAG2ICT text includes brief description noting the problematic issue with this SC for Closed Functionality. M376 notes a 5.x.y.z provision addressing the closed requirement raised by this SC. Further, M376 makes more clear what is needed.

<korn> RESOLUTION: modify WCAG2ICT text for closed to read: "one of the options available to authors for success criterion 1.2.3 is that of providing a media alternative that is text - which necessarily relies on a connected assistive technology to be presented"

<korn> Rationale: WCAG2ICT text cannot introduce or reference additional provisions. WCAG2ICT text can be made more clear and helpful.

<korn> -22Mar13.

<korn> WCAG2ICT text includes brief description noting the problematic issue with this SC for Closed Functionality. M376 notes a 5.x.y.z provision  addressing the closed requirement raised by this SC. Further, M376 makes more clear what is needed.

<korn> RESOLUTION: modify WCAG2ICT text for closed to read: "one of the options available to authors for success criterion 1.2.3 is that of providing a media alternative that is text - which necessarily relies on a connected assistive technology to be presented"

<korn> Rationale: WCAG2ICT does not have specific provisions for closed functionality.  WCAG2ICT text can be made more clear and helpful.

<korn> -22Mar13.

SC 1.2.8

This version of the WCAG2ICT document doesn't address Level AAA SC's.

We had never previously made a resolution as a group that we would not address Level AAA SC's in our document.

However, there is no indication that anyone will be picking up Level AAA.

It would be good to get a resolution from the task force by putting it in a survey and then we can communicate it forward to the WCAG working group.

<Mike_P> M376 doesn't include this on the list. This is a AAA SC. RESOLUTION: drop this SC from the list Rationale: This version of WCAG2ICT doesn't address any AAA SC. -22Mar13.

<korn> ================

<korn> M376 doesn't include this on the list. This is a AAA SC.

<korn> RESOLUTION: drop this SC from the list.

<korn> Rationale: This version of WCAG2ICT doesn't address any AAA SC.

<korn> -22Mar13.

SC 1.3.1 and 1.3.2

The survey comments are both straighforward.

That we are in agreement that the formatting changes are needed.

<korn> ===================

<korn> WCAG2ICT text includes brief description noting the problematic issue with this SC for Closed Functionality. M376 notes a 5.x.y.z provision addressing the closed requirement raised by this SC.  WCAG2ICT includes logic referencing programmatic determinability.

<korn> No change. 

<korn> Rationale: WCAG2ICT does not have specific provisions for closed functionality. Programmatic determinability language helpful to developers.

<korn> -22Mar13. 

SC 1.4.2 - This SC is covered in M376 by 3 provisions rather than using this SC.

<korn> =================

<korn> WCAG2ICT doesn't place this on the closed list.

<korn> No change. 

<korn> Rationale: audio control is important also for self-voicing apps.

<korn> -22Mar13.

SC 1.4.4 - a lot like 1.3.2, but is not a programmatic determinability reference

We can say in the rationale that the WCAG2ICT text is helpful.

<korn> ====================

<korn> WCAG2ICT text includes brief description noting the problematic issue with this SC for Closed Functionality. M376 notes a 5.x.y.z provision addressing the closed requirement raised by this SC.  WCAG2ICT describes potential text rendering limitations in closed.

<korn> No change. 

<korn> Rationale: WCAG2ICT does not have specific provisions for closed functionality. WCAG2ICT text is helpful.

<korn> -22Mar13.  

We'll start with SC 1.4.5 at the next meeting.

We also need to finish the final 4 SC and conformance.

This survey can be kept open until the next meeting.

The next meeting will be on Friday 5 April.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.137 (CVS log)
$Date: 2013/03/22 18:56:35 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.137  of Date: 2012/09/20 20:19:01  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/as it is part of the regulatory process/as it appears to be pro-active efforts at reconciliation of active regulatory processes/
Succeeded: s/cannot be creating guidance for what the regulatory groups should do/should not be telling the regulatory groups what to do, nor creating the perception that they may be doing so/
Succeeded: s/introdoctory/introductory/
Succeeded: s/closed products functionality/closed functionality/
Found Scribe: Mary_Jo_Mueller
Found ScribeNick: MaryJo
Default Present: Mary_Jo_Mueller, David_MacDonald, Michael_Cooper, Mike_Pluke, Judy, Gregg_Vanderheiden, Kiran_Kaja, Peter_Korn, Bruce_Bailey
Present: Mary_Jo_Mueller David_MacDonald Michael_Cooper Mike_Pluke Judy Gregg_Vanderheiden Kiran_Kaja Peter_Korn Bruce_Bailey
Regrets: Loic_Martinez_Normand Andi_Snow_Weaver Alex_Li
Agenda: http://lists.w3.org/Archives/Public/public-wcag2ict-tf/2013Mar/0013.html
Found Date: 22 Mar 2013
Guessing minutes URL: http://www.w3.org/2013/03/22-wcag2ict-minutes.html
People with action items: 

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


[End of scribe.perl diagnostic output]