See also: IRC log
<trackbot> Date: 28 June 2013
<scribe> scribe: Mary_Jo_Mueller
<scribe> scribenick: MaryJo
Can't find any record of Andi's comments with Peter and Gregg's, probably not saved so she'll have to submit them on the document review.
Capitalization issue for 'Web' vs. 'web' will be left to Michael.
Peter will provide an edit tracked document to Michael at the end of the meeting.
It will have all of the edits except for global changes which will be provided as instructions to Michael after the meeting.
https://www.w3.org/2002/09/wbs/55145/20130618/results#xSCs
Discussion on suggested edit to 2.1.2 to add 'component' to the note to say 'or other standard COMPONENT exit methods,'
<korn> http://www.w3.org/WAI/GL/wcag2ict/#keyboard-operation-trapping
That edit was not agreed upon, so will not get added to the document.
Discussion on how to mark up the 'Intent' headings. We agreed that the 'Intent from' text be included in the link text so it will also get the link visual treatment.
Change text to say 'Intent for' and add 'also provided below' to it
<korn> Global suggestion "INTENT" becoming "Intent" -> instead plan is to make them all hyperlinks from "</a>Intent from Understanding {sc} WCAG 2.0</a>(also provided below)"
The word 'directly' will not be removed from the statements 'Applied directly as written.'
For principles and guidelines, the word 'directly' will be added to that statement for consistency.
<korn> http://www.w3.org/WAI/GL/wcag2ict/#minimize-error-identified
Discussion on 3.3.1 where software must make error text programmatically determinable. The web has a generalized way to make text appear on the screen through an event caused by adding text to the DOM.
For software, you have to use an API in order expose the event of displaying the error text to ATs so they would speak it.
<Loic> text: sequence of characters that can be programmatically determined, where the sequence is expressing something in human language
The issue is that no event will get issued unless an API call is used to expose the text insertion.
4.1.2 requires that and change to a UI component has to be programmatically determinable. This error text cannot be set by a user, so it can't apply to this error text.
1.3.1 could be used to apply to this, but programmers may not read it this way.
Would be best to have this situation documented in the understanding document and Gregg and Peter will take this forwared to the WCAG working group.
WCAG could also add an WAI-ARIA example.
<korn> The sections that follow are organized according to the principles, guidelines, and success criteria from WCAG 2.0. The text of the item from WCAG 2.0 is copied as quoted text. Following that, the “intent” from Understanding WCAG 2.0 is copied as quoted text. Finally, the guidance of this document is provided. In visual presentations this is set out in a box with a blue bar to the left, to highlight that this is the content specific to this document.
<korn> Following that, the “intent” from Understanding WCAG 2.0 is copied as quoted text - WE MAKE NO SUBSTITUTIONS OR EDITS TO THIS TEXT.
We need to make clear in this paragraph that we are not providing the word substitutions for the Intent which is copied as quoted text from WCAG 2.0.
Gregg would like to add that with the heading of each intent section before we include it.
There is a suggested change for 'assistive technology' to 'assistive technologies' to be consistent, but it changes some verbiage in normative SC.
In the places where the substitution occurs, we had actually changed to 'technology' and this is really meant to change that back - we intend to make the pluralization consistent with WCAG 2.0
RESOLUTION: Accept comments by guidelines and success criteria as amended in the meeting.
Comments on definitions in the Appendix A: https://www.w3.org/2002/09/wbs/55145/20130618/results#xDefs
Peter meant ICT[s], without a capital 's'.
In the styling of the note for 'accessibility supported', it is in a yellow background but that is not used elsewhere in the document.
<korn> http://www.w3.org/WAI/GL/wcag2ict/#programmaticallydetermineddef
In success criterion edits when we have WCAG2ICT-specific notes, it is placed outside of the white substitution box. In the glossary terms, like in 'programmatically determined', it should be done the same for consistency.
<korn> http://www.w3.org/WAI/GL/wcag2ict/#ensure-compat-parses
In glossary, we also need to remove the part 'and adding a note ...' in the paragraph talking about the substitutions we made in the glossary terms. This is to be consistent with the treatment in the SC's.
<korn> http://www.w3.org/WAI/GL/wcag2ict/#structuredef
Instead, whenever we have added notes, we won't refer to them in the statement above and they will be outside of the white box.
accessibility supported - since that note replaces WCAG's 5 notes, it belongs inside the white box.
change of context - note belongs outside the white box.
Also for programmatically determined, programmatically set, and structure - note belongs outside the white box.
'set of web pages' - was missing the header and quote due to incorrect HTML in the document.
<korn> http://www.w3.org/WAI/GL/wcag2ict/#conformancedef
Definition of 'contrast ratio' includes the third person 'we'
<korn> Because relative luminance is defined such that it cannot directly apply to hardware, please note the text in the introduction which reads
Crossing out is only used when words are removed where we don't make substitutions.
Text should say 'with these substitutions and removals....'
RESOLUTION: Accept editorial cleanup for the Comments on Definitions section as amended.
Content of the appendices: https://www.w3.org/2002/09/wbs/55145/20130618/results#xAppend
Credits - members of the task force in first section, and people in wcag working group that participated in the approval of the contents in the second section.
Task force all agreed on Peter's edits and Mary Jo's additional edit.
Bulleted lists will have semicolons at the end of each bullet's text and precede the bulleted list with a colon - will just leave this to the editors to agree upon.
The documents that we cite should be in references. The understanding document that we cite should be the one that has our updated notes.
RESOLUTION: Accept the 'Content of the appendices' as amended.
<korn> https://www.w3.org/2002/09/wbs/55145/20130618/results#xstatus
Description of the WCAG2ICT document: https://www.w3.org/2002/09/wbs/55145/20130618/results#xstatus
RESOLUTION: Accept the description of the WCAG2ICT document as proposed.
De-emphasizing the intent material: https://www.w3.org/2002/09/wbs/55145/20130618/results#xq16
There needs to be one clear main version of the document. We can have an alternate view of the document that allows collapsing.
We need to make sure that the snapshot of the document used as the alternate version is kept up-to-date with the main one.
It is unusual to put links to an alternate version inside of the main version of the document.
<David> +1
<greggvanderheiden> to go to publication with an expanded flat version in TR space, and a collapsed version in GL space with public question for final being A) flat only b) collapsable and collapsed only c) collapsable and expaneded only , and d) what we have now.
<greggvanderheiden> to go to publication with an Full flat version in TR space, and a collapsable collapsed version in GL space with public question for final being A) flat only b) collapsable and collapsed only c) collapsable and expanded only , and d) what we have done for this draft
<korn> +1
<greggvanderheiden> to go to publication with an Full flat version in TR space, and a collapsable collapsed version in GL space with public question for final being A) flat only b) collapsable and collapsed only c) collapsable and expanded only , and d) what we have done for this draft
RESOLUTION: Accept proposal for publication of a Full flat version in TR space, and a collapsable collapsed version in GL space with public question for final being A) flat only b) collapsable and collapsed only c) collapsable and expanded only, and d) what we have done for this draft
<greggvanderheiden> Empowered the members of the task force who are at the WCAG meeting to act for the task force in closing any final WCAG working group questions so that the working group can approve the document for publication
<korn> +1 in present tense
<janina_> +1
<greggvanderheiden> Empower the members of the task force who are at the WCAG meeting to act for the task force in closing any final WCAG working group questions so that the working group can approve the document for publication
RESOLUTION: Agree to empower the members of the task force who are at the WCAG meeting to act for the task force in closing any final WCAG working group questions so that the working group can approve the document for publication.
commenting period: https://www.w3.org/2002/09/wbs/55145/20130618/results#xComment
Europe - many countries have vacation in July, but others have vacation in August, so a longer time period would be best.
We can accept comments after the end of the commenting period, so having a 30 day commenting period is not necessarily a problem.
We can process any early comments received before the comment period ends as soon as they are received.
We would publish either on July 12 or 16th. End of comment period would be: 30 days is the 15th of August, and 45 days is the 30th of August.
M376 is meeting on September 10 to go over comments and will have an issue using our document if we're not a working group Note by then.
There will be a second meeting on September 23 for M376 comment processing, so that gives us 2 more weeks to become a Note.
<korn> +1 to extending
RESOLUTION: Accept 5 week review period.
RESOLUTION: Close Judy's action item.
<greggvanderheiden> Replace "applies... 'as is'..." which appears in a few places with "applies ... 'as written'..."
<greggvanderheiden> https://sites.google.com/site/wcag2ict/to-do-before-3rd-final-public-draft
RESOLUTION: Replace 'applies...' 'as is'..." which appears in a few places with "applies ... 'as written'..." are considered editorial comments.
RESOLUTION: Allow editors to make other editorial changes that would not cause concern to the members of the task force.
We will not be meeting regularly again unless the chairs call one.
First meeting would be July 26 at the earliest, but probably won't happen until August.
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/'component/'component' to the note to say 'or other standard COMPONENT exit methods,'/ Succeeded: s/add a/add an/ Succeeded: s/of the contents./of the contents in the second section./ Succeeded: s/should/will/ FAILED: s/needs to be an action to take forward to the WCAG working group/Gregg and Peter will take this forwared to the WCAG working group./ Succeeded: s/needs to be an action to take forwared to the WCAG working group/Gregg and Peter will take this forwared to the WCAG working group/ Succeeded: s/30 days is the/End of comment period would be: 30 days is the/ Found Scribe: Mary_Jo_Mueller Found ScribeNick: MaryJo Default Present: Gregg_Vanderheiden, David_MacDonald, Mary_Jo_Mueller, [Microsoft], Peter_Korn, Michael_Cooper, Loic, Bruce_Bailey, Kiran_Kaja, Judy, janina_, Cooper Present: Gregg_Vanderheiden David_MacDonald Mary_Jo_Mueller [Microsoft] Peter_Korn Michael_Cooper Loic Bruce_Bailey Kiran_Kaja Judy janina_ Cooper Regrets: Mike_Pluke Andi_Snow-Weaver Found Date: 28 Jun 2013 Guessing minutes URL: http://www.w3.org/2013/06/28-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]