See also: IRC log
<trackbot> Date: 13 November 2012
<shadi> hi andi
<shadi> i won't be able to participate by phone today
<shadi> ping me if i can help with anything via irc
<scribe> scribe: Andi_Snow-Weaver
RESOLUTION: Accept new title "Guidance on Applying WCAG 2.0 to Non-web Information and Communications Technologies"
https://www.w3.org/2002/09/wbs/55145/OCT112012/results#xq12
<Zakim> Bruce_Bailey, you wanted to say we need to careful about what being on the list means
<Mike_P> M376 approach: https://docs.google.com/viewer?a=v&pid=sites&srcid=ZGVmYXVsdGRvbWFpbnx3Y2FnMmljdHxneDoxMzgxYmI2YzU4MmU5NzU5
if there are images of text, it's important that the text either be of a sufficient size or that there be some way to enlarge it
but we don't believe we can prescribe that actual text has to be used rather than images of text in closed functionality
RESOLUTION: Add 1.4.5 to the list for closed functionality with appropriate rationale
in multitasking environments, the purpose of the title is to remind the user what task he/she is doing - doesn't seem to be necessary in single task environments
<greggvanderheiden> '
this is about a document title or software title - not anything inside the document or software
where software is an integral part of a closed product that has only one funtion (calculator, IP phone), there is no need for a title
if we add to the list, need a one line explanation/rationale much as we have for the others
reminder of some of the words we have around this list ....
"Where AT cannot be used, other output and input solutions are needed to achieve the intent of these success criteria."
and "Note: While these guidelines are not suitable for closed functionality as written, they will inform and aid development of built-in accessible alternatives needed with closed functionality."
titles are not needed for any single task function environment, whether it is closed to AT or not
example of where there is a single task function - Linux based phone with a USB port - could put AT on a USB drive
RESOLUTION: Add 2.4.2 to the list for closed functionality with appropriate rationale
we need rationale with this one that makes it clear the information needs to be presented but it doesn't have to be "text" according to the WCAG 2.0 definition of text
proposal for the rationale for this one: while it's important that errors that can be detected are described in words, for closed functionality, the error doesn't have to be in text, as defined in WCAG
RESOLUTION: Add 3.3.1 to the list for closed functionality with appropriate rationale
<greggvanderheiden> https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/remaining-3-scs
it's tricky to say there are no examples of "set of software" unless we define it
<Zakim> Bruce_Bailey, you wanted to double check that we cannot say “webpage in a set of webpages” should be interpreted as “software”?
<greggvanderheiden> https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/remaining-3-scs
WCAG co-chairs agree that we can't interpret "web page within a set of web pages" as "software"
intent of these SC is that they apply to a set of things - we can apply within software as long as we can define what the "things" are in the set
we were unable to come up with a definition of things inside software that would make up the set
we attempted to define the "things" by defining "interaction context"
web applications are generally a single URL - if we apply this inside a non-web software product, the rules would be different for non-web and web software
for next draft, may have to say we've not yet reached consensus on guidance for SW for these three SC
<greggvanderheiden> https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/remaining-3-scs
<greggvanderheiden> The remaining three success criteria apply in situations when "a set of web pages", or "multiple web pages" share some characteristic or behavior. For these, the task force found that (with substitutions) the success criteria apply to non-web documents fairly straightforwardly. The task force has not yet been able to work out how these three success criteria dealing with "sets of web pages" or "multiplel " web page would apply to
<greggvanderheiden> software.
<korn> "The task force does not yet have guidance for how to apply these to software."
<korn> The task force does not yet have guidance for how to apply these three remainign success criteria to software.
<greggvanderheiden> "The task force does not yet have guidance for how to apply these three SC to software."
<greggvanderheiden> The task force does not yet have guidance for how to apply these three SC in a software context
<greggvanderheiden> The task force does not yet have guidance for how to apply these three SC in a software context
<greggvanderheiden> [10:49am]
<greggvanderheiden> The Task Force found that the majority of success criteria from WCAG 2.0 can apply to non-Web documents and software with no or only minimal changes. Specifically, of the thirty-eight Level A and AA success criteria, twenty-six did not include any web related terms and apply directly as written and as described in the "Intent" sections from the updated “Understanding WCAG 2.0”. Half of these twenty-six applied without any additional
<greggvanderheiden> notes. Half applied as written but additional notes were also provided for assist in applying them to either or both non-web documents and software.
<greggvanderheiden> Of the remaining twelve success criteria, the Task Force found that nine of them they apply as written when replacing certain web specific terms or phrases like "Web page(s)" with non-web terms or phrases like “non-web document(s) and software" or “for non-Web documents and software that use markup languages, in such a way that…etc.” Additional notes were also provided to assist in the application of these.
<greggvanderheiden> The remaining three success criteria apply in situations when "a set of web pages", or "multiple web pages" share some characteristic or behavior. For these, the task force found that (with substitutions) the success criteria apply to non-web documents fairly straightforwardly. The task force does not yet have guidance for how to apply these three success criteria in a software context
<BBailey> +1
<David> +1
+1
<korn1> +1
<Mike_P> +1
RESOLUTION: Accept "PROPOSAL for final paragraphs in INTRO FROM WCAG2ICT 2012-11-13meeting" at https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/remaining-3-scs
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/Back to/topic: Back to/ Succeeded: s/RESOLUTION: Add 1.4.2 to the list for closed functionality with appropriate rationale/RESOLUTION: Add 2.4.2 to the list for closed functionality with appropriate rationale/ Succeeded: s/RESOLUTION: Add 1.4.5 to the list for closed functionality/RESOLUTION: Add 1.4.5 to the list for closed functionality with appropriate rationale/ Succeeded: s/RESOLUTION: Add 3.3.1 to the list with appropriate rationale/RESOLUTION: Add 3.3.1 to the list for closed functionality with appropriate rationale/ No ScribeNick specified. Guessing ScribeNick: Andi Found Scribe: Andi_Snow-Weaver WARNING: No "Present: ... " found! Possibly Present: Alex_Li Andi_Snow_Weaver BBailey Bruce_Bailey David David_MacDonald Gregg_Vanderheiden IPcaller Janina_Sajka Judy Kiran_Kaja MaryJo MichaelC_ Microsoft Mike_P Mike_Pluke Oracle P1 P12 P20 P21 P24 P36 P6 Peter_Korn alex_ greggvanderheiden https janina korn korn1 shadi trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Regrets: Allen_Hoffman Loic_Martinez_Normand Found Date: 13 Nov 2012 Guessing minutes URL: http://www.w3.org/2012/11/13-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]