WCAG WG F2F 16 June (day #4) -- 16 Jun 2005

guideline 1.3

updated 1.3 survey results: http://www.w3.org/2002/09/wbs/35422/content-struct-0616/results

resolution: adopt guideline 1.3 text Ensure that information, functionality, and structure can be separated from presentation.

rationale: structure is information but not all information is structure (we would like to highlight the importance of structure). since we use the word "functionality" elsewhere, would like to use one term consistently throughout the guidelines.

<scribe> scribe: wendy

resolution: adopt updated proposed tet G1.3 L1 SC3 Information that is conveyed by color is also conveyed when color is not available, or can be programmatically determined.

<Christophe> quote of the day: "I think we're having the world's most expensive document semantics tutorial."

resolution: adopt updated proposed wording for G1.3 L2 SC2 Information that is conveyed by variations in presentation of text is also conveyed when variations in presentation of text are not available, or can be programmatically determined. (which deletes the current L1 SC2 Emphasis can be programmatically determined.)

Guideline 2.2

results of survey: http://www.w3.org/2002/09/wbs/35422/time-limits0616/results

<scribe> ACTION: gregg provide a reference for the number "10 times" in G2.2 Level 1 SC1 - "the user is allowed to adjust the time-out over a wide range which is at least ten times the length of the default setting or;" [recorded in http://www.w3.org/2005/06/16-wai-wcag-minutes.html#action01]

resolution: keep current wording of guideline 2.2 L1 SC1 (reject proposal to delete option 2 - the user is allowed to adjust the time-out over a wide range which is at least ten times the length of the default setting or;)
... adopt updated proposed text for G2.2 Level 2 SC1: Content does not blink for more than 3 seconds, or a method is available to stop any blinking content in the delivery unit. (explain 3 seconds in the guide doc)
... adopt proposed wording for G2.2 L3 SC3 When an authenticated session has an inactivity timeout, the user can continue the activity without loss of data after re-authenticating.

oops - didn't resolve on the priority of that....coming back after lunch.

guideline 3.2

results of survey - http://www.w3.org/2002/09/wbs/35422/consistentbe-0616/results

resolution: change "extreme change of context" to "change of context" defined as: A change of user agent, viewport, user interface controls, or focus; or complete change of content.

make sure that we use "change of context" consistently.

<Christophe> GL 3.2 L2 SC2 and L2 SC3 say "extreme change in context" instead of "extreme change of context"

resolution: delete G3.2 L2SC5 "Explicit notice is given in advance of any extreme change of context."

rationale: there did not seem to be any way to do this that would not interfere with normal operation of the page or that didn't prohibit itself. for example, alerts - would have to give notice before an alert (an alert before an alert)

resolution: adopt Updated proposal for Level 2 SC1: Components that are repeated on multiple delivery units in a set of delivery units occur in the same order each time they are repeated.
... Components that have the same functionality in multiple delivery units within a set of delivery units are labeled consistently.
... adopt updated proposed wording for G3.2 L2SC4 Components that have the same functionality in multiple delivery units within a set of delivery units are labeled consistently.

(the first resolution is replaced by the 2nd - 1st was mistyped)

resolution: adopt proposed wording for G3.2 L3 SC2 Changes of context are initiated only by user action.
... change guideline 3.2 text to, "Make the placement and functionality of content predictable."

Conformance

http://www.w3.org/2002/09/wbs/35422/conf20050608/results

resolution: adopt Proposed wording for definitions of levels of conformance 1. WCAG 2.0 conformance at level A means that all level 1 success criteria in the guidelines are met assuming user agent support for only the technologies in the chosen baseline.

2. WCAG 2.0 conformance at level Double-A means that all level 1 and all level 2 success criteria in the guidelines met assuming user agent support for only the technologies in the chosen baseline.

3. WCAG 2.0 conformance at level Triple-A means that all level 1, level 2 and level 3 success criteria in the guidelines are met assuming user agent support for only the technologies in the chosen baseline.

<scribe> ACTION: yvette and john work on editorial fix the use of the term "assuming" in the definition of conformance levels. [recorded in http://www.w3.org/2005/06/16-wai-wcag-minutes.html#action02]

resolution: adopt proposed wording for definition of level 2

1.Achieve an enhanced level of accessibility through one or both of the following:

1. markup, scripting, or other technologies that interact with or enable access through user agents, including assistive technologies.

2. the design of the content and presentation.

1. Can reasonably be applied to all Web resources.

oops. second 1. is a 2.

resolution: adopt proposed wording for definition of level 2

1.Achieve an enhanced level of accessibility through one or both of the following:

a. markup, scripting, or other technologies that interact with or enable access through user agents, including assistive technologies.

b. the design of the content and presentation.

2. Can reasonably be applied to all Web resources.

resolution: adopt proposed wording for definition of level 3

1. Achieve additional accessibility enhancements for people with disabilities.

2. Are not applicable to all Web resources.

resolution: close issue 1330 - The reviewer says that if the delivery unit falls outside the guidelines, such as a PDF document, it can't be called either conformant or non-conformant. The latest draft contains a re-write of the Conformance Requirements section clarifies that the guidelines can be applied to non-W3C technologies.
... closee issue 1364 - The new text in the Conformance Requirements section clarifies that the guidelines are meant to be technology independent and that the use of specific technologies is dependent on the baseline which is defined outside the scope of these guidelines.

<scribe> ACTION: yvette, ben, and andi work to close issue 1324? [recorded in http://www.w3.org/2005/06/16-wai-wcag-minutes.html#action03]

drop action 3

1324 - stays open until we provide the information in the guide doc

andi - it's at - http://www.w3.org/WAI/GL/WCAG20/wcag20-punchlist.html

<Andi> http://www.w3.org/WAI/GL/WCAG20/wcag20-punchlist.html

resolution: adopt updated proposed wording for G1.1 L1 SC1 For all non-text content that is used to convey information, text alternatives identify the non-text content and convey the same information. For multimedia, provide a text alternative that identifies the multimedia. Note: Refer to Guideline 1.2 for requirements for synchronized alternatives for multimedia.

resolution (punch list): delete from the punch list with no change to the guideline - L3 SC2 - "If additional audio description is necessary" - how to make that testable.

the previous resolution applies to Guideline 1.1 L3 SC2. decided that it was part of the defn of extended audio description and didn't need to make it more testable.

resolution (punch list): remove the following item from the punch list and leave l3sc1 in at level 3 for now "L3 SC1 - Should we remove it?"

resolution (punch list): remove the following item from the punch list and leave l3sc3 as it is "L3 SC3 - Should we remove it? Should we make it advisory?"

resolution (punch list): don't change "provided" in sc 1 and 2 to "available" and remove the following item from the punch list - L1 SC1 + SC 2Available - does that mean explicitely associated or just reachable from the delivery unit?

resolution: adopt proposed wording for G4.1 L1SC1 SGML-based delivery units are well-formed. Note: This does not require that they are valid.
... adopt proposed wording for G4.1 L1SC2 Non-SGML-based delivery units are formatted according to their content type specification.

guideline 2.4

these resolutions were made yesterday (15 June 2005). pasting in today's log since not recorded yesterday because of loss of internet connection.

Resolution: adopt proposed definition of Navigational features: Something that allows the user to locate and/or move to a different piece of content than the one currently with focus. Examples of navigational features are links and components that are grouped so they can be bypassed. [note: Might be something in UAAG that can use]
... to adopt wording for G2.4 L1 SC1: Navigational features can be programmatically identified.
... adopt new g2.4 L2 SC: The destination of each programmatic reference to another delivery unit is identified through words or phrases that either occur in text or can be programmatically determined.
... adopt new G2.4 L3 SC: Information about the user's location within a set of delivery units is available.

Guideline 2.1

these resolutions were made yesterday (15 June 2005). pasting in today's log since not recorded yesterday because of loss of internet connection.

Resolution: adopt the following wording for G2.1 L3 SC1 All functionality of the content can be operated through a keyboard interface.

misc other resolutions

These resolutions have not yet been recorded in the minutes. Recording here for completeness.

resolution: adopt proposed definition of multimedia - For the purposes of these guidelines, multimedia refers to combined audio and video presentations. It also includes audio-only and video-only presentations that include interaction.

- DRAFT -

WCAG WG F2F 16 June (day #4)

16 Jun 2005

Attendees

Contents