See also: IRC log
These resolutions to be confirmed with the rest of the WCAG WG on the 23 June 2005 telecon. Note that a separate document "WCAG 2.0 Punchlist" contains the open questions related to each Guideline.
(where "single-key bindings" is used to mean "keyboard shortcuts")
[with clarification in techniques that you don't need to check for *all* possible errors.]
greg describes "punch list" and that the goal of today is to create a list of what needs to be checked off before we can go to last call - what is the list of issues we need to address before we can go to last call.
our next public draft will be as near to what we expect to publish as a last call *plus* a punch list.
go through document top to bottom. want to capture all of the issues that someone here has or that someone else (not here) has. don't want to debate if they are issues or not - collect them.
by end of day have a list of issues (our "punch list") and tomorrow we'll work on proposals to address as many of those as we can.
<ben> updated internal draft: http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20050613/
tomorrow: subgroups come back with a list of 1. accessibility issues that the SC/GL addresses 2. what are the assumptions being made 3. proposed wording (if any) to resolve the issues
to this point we've cleaned up most of what we agree on, next we have to address the points where we have debate (i.e., survey results of 5-5 or 9-4)
3 work products coming out of these 2 days: 1. the list of unresolved issues for SC and GL 2. where possible produce proposals that resolve the issues, do that (to go to the group for review next week) 3. where unable to reach resolution, have the basis for editorial notes for the next WD
an editor's note becomes a succinct statement of the issue (or basis for proposal for solution) around a SC that can tell the community what is unresolved and why and to get input about how to resolve.
resolution: close all of the general issues (in the survey) except the one on plain language (1175).
<Yvette> Current WD: http://www.w3.org/WAI/GL/WCAG20/
1.1 survey: http://www.w3.org/2002/09/wbs/35422/textequiv20050607/results
http://www.w3.org/2002/09/wbs/35422/closed
guideline 1.1 discussion at the 09 June 2005 telecon - http://www.w3.org/2005/06/09-wai-wcag-minutes.html#item05
resolution: no issues with the guideline text
(that we're aware of)
... switch the order of SC1 and SC2 (order becomes: convey info followed by
functional)
scribe note - capturing questions for discussion in separate html document. only capturing resolutions, actions, here.
resolution: L1 SC3 - For non-text content that
is intended to create a specific sensory experience text alternatives at
least identify the non-text content with a descriptive label. With a
definition of "specific sensory experience."
... L1 SC4 - Non-text content that is not functional, is not used to convey
information, and does not create a specific sensory experience is implemented
such that it can be ignored by assistive technology. With definitions of
functional, convey information, specfiic sensory experience.
... L1 SC6 For live audio-only or live video-only content, text alternatives
at least identify the purpose of the content with a descriptive label. Note:
Refer to Guideline 1.2 for guidance on content that combines live audio and
video. [With defns of live audio-only and live video-only content OR (include
examples below AND directly associate the examples with the SC).]
... L3 SC1 - For prerecorded multimedia content, a combined transcript of
captions and audio descriptions of video is available.
Resolution: keep guideline text as "Provide
synchronized alternatives for multimedia." without adding word 'content'
... L1 SC1 Prerecorded multimedia has captions
<ben> note that above resolution was invalidated with additional discussion (multiple issues for future discussion on this)
<wendy> old form of 1.2 - http://www.w3.org/TR/2004/WD-WCAG20-20040730/#media-equiv - rebroadcast was an "exception" and many comments about it being exception and to move to its own criterion.
Resolution: Delete 1.2 L1 SC3
rationale: it is a subset of the other requirements at L1. Any exceptions are already covered by the existing ednote that will be discussed.
<wendy> proposed wording for guideline text: Ensure that the perception of structure and function of the web content do not depend on the presentation
no resolution yet, will discuss tomorrow
Resolution: Not add proposed L2 SC1 "Only markup languages and technologies that enable separation of structure, presentation, and behaviour are used."
Resolution: keep 1.4 as is
<wendy> resolution: Adopt guideline 1.4 as it is in the current draft. http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20050613/#visual-audio-contrast
<wendy> results of survey: http://www.w3.org/2002/09/wbs/35422/keyboardop20050607/results
discussion on GL 2.1
<wendy> functional Performs or is able to perform an action in response to user input. If multiple actions are possible, then refer to definition of applet and scripting.
<wendy> forget that definition
Resolution: adopt text for GL 2.1 as "Make all functionality operable via a keyboard interface"
<wendy> Proposed wording for a L1 criterion for guideline 2.1: The states and values of contents that can be changed via the user interface can also be changed programmatically. (coming from the guideline 4.2 work)
<wendy> http://lists.w3.org/Archives/Public/w3c-wai-gl/2005AprJun/0364.html
resolution: delete GL 2.1 L2 SC1
reason is because this is covered by L1 SC1. This is actually a possible tech (depending upon technology) for satisfying L1 SC1.
<wendy> counter proposal for wording for L3SCx: Keyboard shortcuts are provided for frequently-used functionality.
resolution: not accept the new L3 SC proposal (Provide single-key bindings to frequently-used functionality.)
<wendy> (where "single-key bindings" is used to mean "keyboard shortcuts")
resolution: cover keyboard shortcuts in
advisory material
... not accept the new L3 SC proposal (All of the functionality of the
content is operable through voice commands.)
<wendy> minutes from 26 may 2005 telecon: http://www.w3.org/2005/05/26-wai-wcag-minutes.html#item05
<wendy> 2.2 survey results - http://www.w3.org/2002/09/wbs/35422/time-limits0525/results
resolution: delete ednote under L3 SC1 - will go in guide doc if it goes anywhere
<ben> (ednote referenced free tool from Trace)
quote of the day: "There are not international standards for this, there are standards which are used internationally." -GV
<wendy> ACTION: gv rewrite 2.3 and associated defintions [recorded in http://www.w3.org/2005/06/13-wai-wcag-irc]
<wendy> survey results - http://www.w3.org/2002/09/wbs/35422/navigation-mechanisms20050531/results
<scribe> ACTION: Yvette, Michael, John define "navigational features" for http://www.w3.org/WAI/GL/WCAG20/#navfeaturesdef [recorded in http://www.w3.org/2005/06/13-wai-wcag-irc]
resolution: delete note and ednote to L1 SC1 re
overlap with 1.3
... remove ednote for L2 SC2; becomes a general techniques issue
<wendy> from last week's discussion: concern about proposals. not ready to adopt. need more discussion. Proposed wording Level 2 SC 4: For each programmatic reference to another delivery unit, a title or description of that delivery unit can be programatically determined. and Should we move current level 3 SC3 to Level 2 SC 3: Delivery units have descriptive titles?
resolution: adopt moving L3 SC2 to L2 (becomes SC 3) - with issue of what we intend for "delivery units" still open
<wendy> we've adopted wording for the guideline and that there are no level 1 criteria.
<wendy> Resolution: G2.5 L2 SC3 - For forms that cause legal or financial transactions to occur, that modify or delete data in remote data storage systems, or that submit test responses, at least one of the following is true:
<wendy> a. Actions are reversible.
<wendy> b. Actions are checked for errors before going on to the next step in the process.
<wendy> c. The user is able to review and confirm or correct information before submitting it.
<wendy> [with clarification in techniques that you don't need to check for *all* possible errors.]
<wendy> Resolution: remove guideline 2.1 Level 3 SC 2: If there are more than 75 choices, selection lists must not be the only means of providing the input choice. Another input method, such as a text entry field, text typing... [because it is a usability problem for everyone and usually, if it's that long of a list can navigate it alphabetically and press a letter key to get to it or near it quickly.]
<Andi> http://lists.w3.org/Archives/Public/w3c-wai-gl/2005AprJun/0363.html
<Andi> 1. When user input is limited to a set of 10 or fewer known choices that
<Andi> can
<Andi> be provided without jeopardizing security or purpose, choices can be
<Andi> selected from a list instead of, or in addition to, typing.
<wendy> above is proposal for l3 sc 1
<wendy> current text: Where text entry is required for which there is a known set of less than 75 valid choices and they can be provided without jeopardizing security or purpose, users are allowed to select from a list of options as well as to type the data directly.
<wendy> Resolution: (replaces previous resolution that was misrecorded) don't accept the proposed text (previously proposed for 2.5 and then proposed to move to 2.1): If there are more than 75 choices, selection lists must not be the only means of providing the input choice. Another input method, such as a text entry field, text typing... [because it is a usability problem for everyone and usually,...
<wendy> ...if it's that long of a list can navigate it alphabetically and press a letter key to get to it or near it quickly.]
<wendy> resolution: adopt Proposed wording for 2.5 Level 3 SC3: Additional context relevant assistance is available for text input. [this replaces the existing 2 level 3 criteria which move to techniques]
3.2 Proposal Survey Results http://www.w3.org/2002/09/wbs/35422/consistent-behavior0525/results
<wendy> http://lists.w3.org/Archives/Public/w3c-wai-gl/2005AprJun/0717.html
resolution: Accepted accepted for GL 3.2 Level 1 SC 1 - "Any extreme change of context is implemented in a manner that can be programmatically determined." with the proviso that we re-write the definition of "extreme change of context"
<wendy> resolution: delete from the benfits of guideline 3.2 "Using captions to note changes in speaker is beneficial for individuals who are deaf or hard of hearing and who may be unable to discern changes in speaker for audio-only presentations."
resolution: Proposal accepted for GL 3.2 level 2 SC: Components that are repeated on a set of delivery units occur in the same sequence each time they are repeated.
<wendy> michael counter proposal for L2SC2 - Any component that can receive focus does not automatically activate when focus is received.
<wendy> for this one or last one?
"for at least one presentation format" removed because it is addressed in conformance.
Discussion: should this be Level 3? Resolution wording fixes this.
resolution: Proposal accepted for GL 3.2 Level 2 SC 2 - When any component receives focus it does not cause an extreme change in context.
<wendy> current wording/proposed - Changing the setting of any input field should not automatically cause an extreme change in context
<wendy> that for l2sc3
resolution: Proposal accepted for GL 3.2 Level 2 SC 3 - Changing the setting of any input field does not automatically cause an extreme change in context.
<wendy> Interactive content that appears in multiple delivery units within the same context is associated with similar functionality wherever it appears.
<wendy> above is a counter proposal to, 'Interactive content that appears in multiple delivered units is associated with similar functionality wherever it appears.'
resolution: Proposal accepted for GL 3.2 Level
2 SC 4 - Functional components that are repeated on a set of delivery units
provide similar functionality wherever they appear.
... Delete GL 3.2 Level 2 SC 6 (The destination of each link is identified
through words or phrases that either occur in the link or can be
programmatically determined.) and combine the comcepts with the proposal for
GL 2.4 Level 2 SC 4.
... Proposal accepted to delete GL 3.2 Level 3 SC 2 (Components that appear
visually on multiple pages, such as navigation bars, search forms, and
sections within the main content, are displayed in the same location relative
to other content on every page or screen where they appear.) and include it
appropriately in techniques.
... Delete GL 3.2 Level 3 SC 3 (When components such as navigation menus and
search forms appear on multiple pages, users can choose to have those
elements presented in a different visual position or reading-order.)
... Move GL 3.2 Level 3 SC 5 (When content is arranged in a sequence that
affects its meaning, that sequence can be determined programmatically.) to
1.3 because using correct semantics fixes this problem. Is there another
success criteria that addresses this?
... delete two editorial notes for GL 3.2 Level 3 SC