W3C

- DRAFT -

WCAG2ICT Task Force Teleconference

25 Sep 2012

See also: IRC log

Attendees

Present
David_MacDonald, Andi_Snow_Weaver, Mary_Jo_Mueller, Mike_Pluke, Gregg, Kiran_Kaja, BBailey, Alex_Li, Peter_Korn, Judy
Regrets
Loïc_Martínez_Normand, Pierce_Crowell
Chair
Andi_Snow-Weaver
Scribe
Mary_Jo_Mueller

Contents


<trackbot> Date: 25 September 2012

<Andi> scribe: Mary_Jo_Mueller

<Andi> scribenick: MaryJo

Re-survey on definition of "content" https://www.w3.org/2002/09/wbs/55145/SEP252012/results

<korn> +1 to keeping it as is

We introduced the term non-embedded content because media such as movies and sound files are also non-embedded content.

The update to the definition of content were to ensure hardware is excluded for the definition of content.

We do make clear that documents are an example of non-imbedded content.

Some documents have no interaction, some have simple links and interaction, while others contain more complex interactive content (more software-like).

We may need to have some application notes on the requirements to identify more simplified requirements for simple documents.

Comment on Note 2: This note is not very clear.

Proposal made to remove the note.

<Zakim> BBailey, you wanted to point out that we got into this spot by saying “software and documents” and to add this has now morphed to “software and non-embedded content” and to

<greggvanderheiden> Note: Non-embedded content may be web or non-web content. Electronic documents and a movie file (or set of movie related files including captions file etc if they are a package) are examples of non-embedded content.

propose to change 'movie file or files if they are a package' to be more clear since 'files' also are movie files.

Proposal to update the sentence that has 'non-embedded content' in there twice to make it clearer.

RESOLUTION: Accept proposal #4 for the definition of content.

Public Comments Processing https://www.w3.org/2006/02/lc-comments-tracker/35422/WD-wcag2ict-20120727/

Andi updated the instructions for handling comments for how to show proposed updates to the document.

<Andi> https://sites.google.com/site/wcag2ict/review-process/instructions-for-proposing-and-answer-to-an-issue

In the short name of the comment we can group the similar comments by adding [<topic>].

When we survey the proposed updates to the comments, be sure that the changes are marked with @@.

The WCAG working group must approve all of the proposed changes, so we need to make sure our proposals are in good shape for that approval.

EU M376: Supposed to be formally approved the week of 27 October. The standard probably won't directly reference the WCAG2ICT, but the technical report will.

The most important thing is for us to stabilize is the terminology.

We need to publish before the EU M376 publish date.

Mike should provide a list of the most important terminology that the WCAG2ICT needs to make stable so these are put through the WCAG working group for approval first.

Important are: The definitions of the SC, some of the glossary terms, and potentially the last of our unconcensed SC.

Next year the M376 goes through a long approval process, so WCAG2ICT will probably be published before the entire process is done.

<Zakim> Judy, you wanted to say that's what I was trying to avoid...

We are trying to avoid triggering any changes in M376, but there is too much for us to complete to completely avoid changes.

One important part is closed functionality which the WCAG2ICT has not yet addressed.

The other area of concern is what we mean by conformance.

Priorities: Finish remaining SC, glossary of terms, addressing closed products, and what does conformance mean outside of Web.

The M376 has received many comments on which SC are/are not applicable to closed products, so this may help us.

<Andi> https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/closed-products-and-scs-using-programmatically-determinable

A lot of WCAG applies to closed products, but any SC that are in support of AT and programmatically determined information are the ones that probably won't apply.

<korn> 1.4.4 thankfully mentions AT in the negative, so that one would still apply to closed.

<korn> Same with 1.4.8

We can add a paragraph in the introduction to address closed products in general.

<Mike> +1

We'll have to figure out what to say for the individual SC that don't apply and propose a statement to add to them.

In our charter we are not supposed to say that WCAG doesn't apply, however closed products do something equivalent on their own so we don't want to say that they fail the SC.

We can't use the 'automatically meets' language either.

We could say by fact: Closed products don't have AT, so by definition this SC doesn't fit.

We'll need a proposal and can start with some language that was originally proposed to the U.S. Access Board.

<Andi> ACTION: Andi to draft intro paragraph for closed products and text for each SC that uses programmatically determined [recorded in http://www.w3.org/2012/09/25-wcag2ict-minutes.html#action01]

<trackbot> Created ACTION-63 - Draft intro paragraph for closed products and text for each SC that uses programmatically determined [on Andi Snow-Weaver - due 2012-10-02].

<Andi> action Gregg to start outline of intro text describing content terms - why we don't use simple terms like "electronic documents", etc.

<trackbot> Created ACTION-64 - Start outline of intro text describing content terms - why we don't use simple terms like "electronic documents", etc. [on Gregg Vanderheiden - due 2012-10-02].

<Andi> ACTION: Mike to gather incoming comments to M376 team wrt closed functionality in the WCAG2ICT domain [recorded in http://www.w3.org/2012/09/25-wcag2ict-minutes.html#action02]

<trackbot> Created ACTION-65 - Gather incoming comments to M376 team wrt closed functionality in the WCAG2ICT domain [on Mike Pluke - due 2012-10-02].

Action Items http://www.w3.org/WAI/GL/WCAG2ICT-TF/track/actions/open

<Andi> http://www.w3.org/WAI/GL/WCAG2ICT-TF/track/actions/61

<Andi> close action-61

<trackbot> ACTION-61 Propose notes for both 'user agent' and 'content' to clarify software usage; work with Gregg, Loic, and Mike closed

<Andi> close action-60

<trackbot> ACTION-60 Create web page to show where 'user agent' is used for analysis of how well it works closed

<Andi> close action-59

<trackbot> ACTION-59 Find some real-world examples of sets of documents for group to look at and revisit closed

<Andi> Alex's proposed note is here: http://lists.w3.org/Archives/Public/public-wcag2ict-tf/2012Sep/0044.html

The note that was proposed for visually customized cannot be added to the glossary because that is part of the WCAG normative content.

This term is only used in 1.4.5, but it wouldn't make sense to add this as a note to the SC.

If this needs to be pursued further, this could be opened as an issue on WCAG.

<Andi> close action-58

<trackbot> ACTION-58 Craft note for WCAG 2.0 to describe this term only applies to SC 1.4.5 closed

<Andi> close action-53

<trackbot> ACTION-53 Modify introductory information discussing what content means in the introduction - 'where the word "content" or "web content" appear, it should be interpreted as [text we agreed to at the August 17th meeting]' closed

On action 50, will try to complete this week along with including updates to the terms.

<Andi> close action-48

<trackbot> ACTION-48 Make a proposal for a note to be added to 3.1.1 guidance to clarify the meaning of the last phrase "in that locale/language" closed

<Andi> close action-46

<trackbot> ACTION-46 Discuss issue of identifying the human language of the input with M376 team and come back with a proposal if necessary closed

<greggvanderheiden> …..

For action 43, Christophe still has concerns. He wants to separate out when an application magnifies its own non-embedded content vs. its embedded content and how it responds to platform settings.

He thinks there needs to be language for the different situations.

The WCAG working group already approved language for notes on this.

This was a WCAG 2.0 working group survey comment on 1.4.4.

<Andi> close action-43

<trackbot> ACTION-43 Revisit Christophe's comments on 1.4.4 Resize Text from the WCAG 19 July survey closed

Summary of Action Items

[NEW] ACTION: Andi to draft intro paragraph for closed products and text for each SC that uses programmatically determined [recorded in http://www.w3.org/2012/09/25-wcag2ict-minutes.html#action01]
[NEW] ACTION: Mike to gather incoming comments to M376 team wrt closed functionality in the WCAG2ICT domain [recorded in http://www.w3.org/2012/09/25-wcag2ict-minutes.html#action02]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2012/09/25 18:09:42 $

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)

Succeeded: s/I am back piggy backed on judy//
Succeeded: s/dropped off-- can't get back on//
Succeeded: s/I think there is a 90 min timer on my phone//
Succeeded: s/was a survey comment on 1.4.4/was a WCAG 2.0 working group survey comment on 1.4.4/
Succeeded: s/rrsagent, make minutes.//
Succeeded: s/Bye//
Found Scribe: Mary_Jo_Mueller
Found ScribeNick: MaryJo

WARNING: Replacing list of attendees.
Old list: Bruce_Bailey
New list: David_MacDonald Andi_Snow_Weaver Mary_Jo_Mueller Mike_Pluke Gregg Kiran_Kaja BBailey Alex_Li Peter_Korn Judy

Default Present: David_MacDonald, Andi_Snow_Weaver, Mary_Jo_Mueller, Mike_Pluke, Gregg, Kiran_Kaja, BBailey, Alex_Li, Peter_Korn, Judy
Present: David_MacDonald Andi_Snow_Weaver Mary_Jo_Mueller Mike_Pluke Gregg Kiran_Kaja BBailey Alex_Li Peter_Korn Judy
Regrets: Loïc_Martínez_Normand Pierce_Crowell
Found Date: 25 Sep 2012
Guessing minutes URL: http://www.w3.org/2012/09/25-wcag2ict-minutes.html
People with action items: andi mike

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


[End of scribe.perl diagnostic output]