W3C

- DRAFT -

WCAG2ICT Task Force Teleconference

24 May 2013

See also: IRC log

Attendees

Present
Mary_Jo_Mueller, Loic, Peter_Korn, David_MacDonald, Andi_Snow-Weaver, Gregg_Vanderheiden, Mike_Pluke, Alex_Li, Bruce_Bailey
Regrets
Kiran_Kaja
Chair
Mike_Pluke
Scribe
Mary_Jo_Mueller

Contents


<trackbot> Date: 24 May 2013

<scribe> scribe: Mary_Jo_Mueller

<scribe> scribenick:MaryJo

<David> https://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html

<David> https://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html

Structuring of our document to include collapsible parts

The link that David provided (below) was discussed. This document has expandable sections.

Editors will have to look at this to make sure it is an acceptable solution.

<David> https://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html

Glossary Terms - Part 5, items 3 (programmatically determined) and 4 (programmatically set)

<Mike_P> https://www.w3.org/2002/09/wbs/55145/glossary5/results

In other definitions, we had proposed replacing 'user agents' with 'accessibility features and services of software'. It was suggested that we do the same in the definition of 'programmatically determined'.

<andisnow> +1 to Peter's suggestion

This links strongly to our other survey and we need to remain consistent in the word replacement.

<korn> https://www.w3.org/2002/09/wbs/55145/glossary7/results

Final 5 Glossary Terms

<andisnow> https://www.w3.org/2002/09/wbs/55145/glossary7/results

RESOLUTION: Accept 'blinking' as proposed.

Discussion on 'process': https://www.w3.org/2002/09/wbs/55145/glossary7/results#xq2

The proposed example was problematic for several people, because it is focused on the development environment and we are not getting into ATAG.

This term is used in the SC on multiple ways which applies to a set of software.

<andisnow> +1 to Gregg's comment

<Loic> +1 to that. We need an example about sets of software

The example is not really about authoring, but using a set of software to complete a process.

Batch software is a set of software used to complete a process, but there is no UI involved in that.

<greggvanderheiden> two programs where the first is an authentication program that must precede the second program

<korn> Example: Printing a document converted into a different format involves several programs, and the final program that generates the converted output can only be accessed at the end of the process.

<greggvanderheiden> Printing a document converted into a different format involves several utility programs that must be separate for licensing reasons, and the final program that generates the converted output can only be accessed at the end of the process.

<andisnow> "sets of software" are "extremely rare" - therefore, processes that involve multiple programs with in a set of software are extremely, extremely rare

<greggvanderheiden> Example: There is a digital certification utility that is a separate program but it neither makes sense to use by itself (what are your certifying) nor can it be part of a software product. There it is bundled as part of many sets but only accessible as part of process involving the other software and the utility

<korn> set of software programs: (as used in WCAG2ICT)

<korn> group of software programs that are distributed together and that can be launched and be used independently from each other, but that are interlinked each with every other one such that users can navigate from one program to another via a consistent method that appears in each member of the set

<korn> set of documents (non-web) (as used in WCAG2ICT)group of documents that are published together, and where the items all refer to each other by name or link.Note 1:   Republishing or bundling previously published documents as a collection does not constitute a set of documents.Note 2:  If a set is broken apart, the individual parts are no longer part of a set, and would be evaluated as any other individual document is evaluated.

<greggvanderheiden> NOTE: By the definition of "set of software" used in [WCAG2ICT] a group of software that comprises a process would already be excluded from the definition of "set of software

<greggvanderheiden> so the exception is not needed

<korn> Note 5: The definitions of "set of documents" and "set of software" require every item in the set to be independently reachable, and so nothing in the set can be a "step in a process".

<Alex_> it can be a step, just not a linear one that cannot be reached in other ways

<andisnow> +1 to Alex

<korn> The purpose of the exception - that items in a process are exempt from meeting Multiple Ways - is achieved by the defintion of set.

<korn> Note 5: The definitions of "set of documents" and "set of software" require every item in the set to be independently reachable, and so nothing in the set can be a "step in a process".  The purpose of the exception - that items in a process are exempt from meeting this success criterion- is achieved by the definition of set.

<korn> process

<korn> This term is only used in success criterion 2.4.5 Multiple Ways.  The definitions of "set of documents" and "set of software" require every item in the set to be independently reachable, and so nothing in the set can be a "step in a process". 

<korn> process

<korn> This term is only used in success criterion 2.4.5 Multiple Ways.  The definitions of "set of documents" and "set of software" require every item in the set to be independently reachable, and so nothing in the set can be a "step in a process".  The purpose of the the term's use in 2.4.5 Multiple Ways - that items in a process are exempt from meeting that success criterion- is achieved by the definition of set.

<andisnow> "so nothing in the set can be a "step in a process that can't be reached any other way"."

<korn> ... so nothing in the set can be a "step in a process" as defined by WCAG 2.0...

<korn> Note 5: The definitions of "set of documents" and "set of software" in WCAG2ICT require every item in the set to be independently reachable, and so nothing in such a set can be a "step in a process" that can't be reached any other way.  The purpose of the exception - that items in a process are exempt from meeting this success criterion- is achieved by the definition of set.

Note 5 is a proposed addition to the Multiple Ways SC

<korn> Note 5: The definitions of "set of documents" and "set of software" in WCAG2ICT require every item in the set to be independently reachable, and so nothing in such a set can be a "step in a process" that can't be reached any other way.  The purpose of the exception - that items in a process are exempt from meeting this success criterion- is achieved by the definition of set.

<korn> process

<korn> This term is only used in success criterion 2.4.5 Multiple Ways.  The definitions of "set of documents" and "set of software" in WCAG2ICT require every item in the set to be independently reachable, and so nothing in such a set can be a "step in a process" that can't be reached any other way.  The purpose of the the term's use in 2.4.5 Multiple Ways - that items in a process are exempt from meeting that success criterion- is achieved by the definition[CUT]

RESOLUTION: Accept Note 5 for SC 2.4.5 Multiple Ways and the text for the definition of 'process' as updated in the meeting.

<Loic> https://www.w3.org/2002/09/wbs/55145/glossary7/results#xq3

Supplemental content: https://www.w3.org/2002/09/wbs/55145/glossary7/results#xq3

There is a new section being added to the document listing terms we will not be working on.

RESOLUTION: Accept adding 'supplemental content' to the list of terms we are not defining in our document.

technology (Web content) : https://www.w3.org/2002/09/wbs/55145/glossary7/results#xq4

This term only appears in 'accessibility supported'.

<korn> "technology (as used for creation of content)" could perhaps work

The word 'technology' occurs in many places in WCAG 2.0, but is not linked into the glossary. In those places, this term definition doesn't really work well.

In the few places where 'Web content technology' is used and linked then the proposed definition makes sense.

<korn> Guidance on applying this definition to non-web documents and softwareThis definition applies as written, replacing "browsers and other user agents" with "user agents or other software",  replacing "user agents" with "user agents or other software", replacing "Web content technology" with "technology", replacing "widely-distributed plug-in" with "widely-distributed plug-in or other software extension", and replacing all five of the Notes with a single[CUT]

<korn> "NOTE:The concepts behind the five Notes and in Understanding Accessibility Supported are applicable to Web technologies. The same or similar factors are applicable for non-Web technologies"With these substitutions and addition, it would read: ...

The substitution 'non-web documents or software' should also be in the parenthetical of the term 'technology', and then analyze if it works everywhere or not.

You wouldn't replace every instance of 'technology' with this definition.

<korn> See https://sites.google.com/site/wcag2ict/glossary-edits-post-2nd-public-draft (which assumes we gain RESOLUTION on it)

RESOLUTION: Accept the proposal for 'technology (Web content)' as written.

<korn> https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/accessibility-supported-glossary

RESOLUTION: Accept update to 'accessibility supported' as documented in the above linked page.

<korn> https://sites.google.com/site/wcag2ict/edits-for-michael-post-2nd-public-draft

user interface component: https://www.w3.org/2002/09/wbs/55145/glossary7/results#xq5

<Mike_P> A software program has 2 controls: a text field for entering a file name and a drop down list box for choosing a folder. Each is a user interface component with a name that is settable by the software.

RESOLUTION: Accept proposal for 'user interface component' as written with the edit to the Example updated in the meeting, posted above.

<korn> https://www.w3.org/2002/09/wbs/55145/a11srvcs/results

<korn> https://sites.google.com/site/wcag2ict/edits-for-michael-post-2nd-public-draft/new-glossary-term-accessibility-services-of-software-and-assistive-technology

RESOLUTION: Accept proposal 2 for accessibility services of software as written.

<andisnow> Maximize compatibility with current and future assistive technology and accessibility services of software

RESOLUTION: Accept substitution proposed for Guidline 4.1 and Principle 4 as updated in the meeting posted above.

<greggvanderheiden> https://www.w3.org/2002/09/wbs/55145/glossary5/results#xq2

Returning to 'programmatically determined': https://www.w3.org/2002/09/wbs/55145/glossary5/results#xq2

<korn> Principal 4 Robust: Content must be robust enough that it can be interpreted reliably by a wide variety of [assistive technology, ACCESSIBILITY FEATURES, and <key term link>accessibility services of software</key term link>].

<korn> In WCAG 2.0, the Principles are provided for framing and understanding the success criteria under them but are not required for conformance to WCAG. Principle 4 applies as written replacing "user agents, including assistive technologies" with "assistive technology, accessibility features and accessibility services of software".

<korn> Principal 4 Robust: Content must be robust enough that it can be interpreted reliably by a wide variety of [assistive technology, accessibility features and <key term link>accessibility services of software</key term link>].

<korn> programmatically determineddetermined by software from author-supplied data provided in a way that different [<key term link>accessibility services of software</key term link>] including assistive technologies [and accessibility features of software], can extract and present this information to users in different modalities

<korn> The definition of "programmatically determined" applies to non-web ICT as is, replacing "user agents" with "accessibility services of software" and adding "accessibility features of software".

<korn> https://sites.google.com/site/wcag2ict/glossary-edits-post-2nd-public-draft

RESOLUTION: Accept 'programmatically determined' and 'programmatically set' as updated in the meeting, as shown in the above linked page.

<korn> https://sites.google.com/site/wcag2ict/edits-for-michael-post-2nd-public-draft

<korn> https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/remaining-3-scs

<greggvanderheiden> https://join.me/807-915-348

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log)
$Date: 2013/05/24 17:58:12 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/software that is comprises/software that comprises/
Succeeded: s/cannot be reach/cannot be reached/
Succeeded: s/can you repost the link to the collapsable doc?//
Succeeded: s/The link that David provided above was discussed/The link that David provided (below) was discussed/
Found Scribe: Mary_Jo_Mueller
Found ScribeNick: MaryJo
Default Present: Peter_Korn, +1.512.423.aaaa, David_MacDonald, Andi_Snow-Weaver, Gregg_Vanderheiden, Mike_P, [Microsoft], Bruce_Bailey
Present: Mary_Jo_Mueller Loic Peter_Korn David_MacDonald Andi_Snow-Weaver Gregg_Vanderheiden Mike_Pluke Alex_Li Bruce_Bailey
Regrets: Kiran_Kaja
Found Date: 24 May 2013
Guessing minutes URL: http://www.w3.org/2013/05/24-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]