WAI_UA

http://www.w3.org/WAI/UA/2008/draft_uawg_charter_26jun08.html

Charter Renewal

JB: Review of changes to the Charter Milestones

KF: This seems more reasonable and achievable

JA: Ok

JS: More achievable

JB: Can I add the Errata document?

KF: Agreed

JA: Agreed

JS: Agreed
... Give an example of what goes in the Errata document?

JB: It is the corrections document.
... These are standard placeholder pages for corrections.
... The participation page has also changed. I would like to see the participation at 8.
... Also changed the F2F number from 3-4 to 2.
... to reflect the trend toward fewer F2F meetings.

+1

discussion on participation and potential participants

we agreed to increase the participation to 8 and commit to bringing on new members and keeping existing ones.

<AllanJ> http://lists.w3.org/Archives/Public/w3c-wai-ua/2008OctDec/0016.html

Last Item in 4.1

JA: We had discussion, but never reached a final resolution.

* 4.1.11 Intergroup Navigation: Allow the user to navigate from group

to group of focusable items (e.g., toolbars, dialogs, panels, etc.)

JB: why not combine it with 4.1.7?

JA: It is a different level 4.1.7 is AA and 4.1.11 is AAA.

KF: Once you make something accessible from the keyboard, it is the same amount of work whatever you do. It could be merged.

JA: I think it could be merged.

KF: If there are so many controls that they have to be visually grouped, then you have to be able to move directly to the group. You can't tab through 50 controls.

JS: Agreed

<AllanJ> ACTION: AllanJ to combine 4.1.7 and 4.1.11 sequential and among group navigation [recorded in http://www.w3.org/2008/10/16-ua-minutes.html#action01]

<trackbot> Sorry, couldn't find user - AllanJ

<AllanJ> ACTION: JA to combine 4.1.7 and 4.1.11 sequential and among group navigation [recorded in http://www.w3.org/2008/10/16-ua-minutes.html#action02]

<trackbot> Created ACTION-30 - Combine 4.1.7 and 4.1.11 sequential and among group navigation [on Jim Allan - due 2008-10-23].

review remainder of keyboard issues to flag wordsmithing issues from technical issues.

Guideline 4.3 Allow time-independent interaction

4.3.1 Timing Adjustable: Where time limits for user input are recognized and controllable by the user agent, an option is provided to extend the time limit.

+1

KF: +1

<AllanJ> +1

Guideline 4.4 Help users avoid flashing that could cause seizures

4.4.1 Below Threshold: The user interface "chrome" never violates the general flash or red flash thresholds.

JS: Can't we refer them to WCAG?

KF: The definition should be in this document/

<AllanJ> define - general flash and red flash thresholds

JB: We need to remove "chrome"

<AllanJ> issue: 4.4.1 define - general flash and red flash thresholds

<trackbot> Created ISSUE-1 - 4.4.1 define - general flash and red flash thresholds ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/1/edit .

<AllanJ> issue: remove 'chrome' from all checkpoints...entire document

<trackbot> Created ISSUE-2 - Remove 'chrome' from all checkpoints...entire document ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/2/edit .

4.4.1 Below Threshold: The user interface never violates the general flash or red flash thresholds. [copy definitions here from WCAG]

JS: The levels are in harmony with WCAG

JB: A great deal of research has been done to define these thresholds. It may be appropriate to make a note that refers people to the definitions and tools.
... We need to give people more than a hint of what to do.

KF: A link with more detail in a definition is ok. The techniques should link to tools. (Trace tools?)

Definition in WCAG: http://www.w3.org/TR/2008/CR-WCAG20-20080430/#general-thresholddef

<AllanJ> issue: 4.4.1 and 4.4.2 - do we just link to definition that include all info from wcag, or add short note in explanation with link to definitions and techniques

<trackbot> Created ISSUE-3 - 4.4.1 and 4.4.2 - do we just link to definition that include all info from wcag, or add short note in explanation with link to definitions and techniques ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/3/edit .

KFord had to leave. Judy, Jeanne and Jim remain on the call, so the balance of the meeting will be used for planning purposes.

<scribe> ACTION: JS to do an editorial fix of the numbering in the Guideline text of 4.5 (says 3.6) [recorded in http://www.w3.org/2008/10/16-ua-minutes.html#action03]

<trackbot> Created ACTION-31 - Do an editorial fix of the numbering in the Guideline text of 4.5 (says 3.6) [on Jeanne Spellman - due 2008-10-23].

JB: 4.5.3 should be Level AA.

<AllanJ> issue: move 4.5.3 to Level AA

<trackbot> Created ISSUE-4 - Move 4.5.3 to Level AA ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/4/edit .

JS: questioned quotes around "wizard" in 4.5.4 and the "(at least)".

JB: There is no semantic change if the "(at least)" is deleted.

<AllanJ> issue: 4.5.4 remove quotes around wizard

<trackbot> Created ISSUE-5 - 4.5.4 remove quotes around wizard ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/5/edit .

<AllanJ> issue: 4.5.4 remove (at least) --- no change in meaning

<trackbot> Created ISSUE-6 - 4.5.4 remove (at least) --- no change in meaning ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/6/edit .

Guideline 4.6 Provide text search

4.6.1 Search Rendered: The user can perform a search within rendered (e.g., not hidden with a style) content for text and text alternatives for a sequence of characters from the document character set.

JB: 4.6.1 needs to be given as an action item for someone to work on rewording.

<scribe> ACTION: JS to create a proposal for rewording 4.6.1 [recorded in http://www.w3.org/2008/10/16-ua-minutes.html#action04]

<trackbot> Created ACTION-32 - Create a proposal for rewording 4.6.1 [on Jeanne Spellman - due 2008-10-23].

JA: The back history is that it requires searching within the text and the text alternatives.

4.6.2 Bi-Directional: The user has the option of searching forward or backward (in document order) from any selected or focused location in content.

JB: We should not need parenthetical comments to explain it. I recommend we assign it to be scrubbed a little.

<scribe> ACTION: JA to create a proposal for rewording of 4.6.2 [recorded in http://www.w3.org/2008/10/16-ua-minutes.html#action05]

<trackbot> Created ACTION-33 - Create a proposal for rewording of 4.6.2 [on Jim Allan - due 2008-10-23].

SC 4.6.3 Match found

# 4.6.3 Match Found: When there is a match, both of the following are true:

* (a) move: the viewport moves so that the matched text content is at least partially within it, and@@9.8 in UAAG10@@

* (b) search again: the user can search for the next instance of the text from the location of the match.@@9.8 in UAAG10@@

JA: There is no major issue and we will review it with the rest of the document.

4.6.4 No Match

JS: Needs more word smithing

<AllanJ> issue: 4.6.4 reword

<trackbot> Created ISSUE-7 - 4.6.4 reword ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/7/edit .

4.6.5 Case Insensitive: There is a case-insensitive search option

JS: This is common practice. It should be a level A.

JB: This is an issue that can be picked up in the overall document review.