F2F Agenda (Tentative)

• UAGL WG Home Page
• Austin meeting page
• Issues list
• 6 December Guidelines

Proposed process for resolving issues

Since we received a number of issues during last call, the Chair proposes the following process for resolving them during the meeting:

Each issue will be given 10 minutes for discussion and resolution. If the issue has not been resolved after 10 minutes, the group by consensus allocate an additional 5 minutes for discussion if they feel the additional time will lead to resolution. If the issue is still not resolved, it will remain on the table until the Friday afternoon time block reserved for resolving remaining open issues. Working group members interested in the issue will be solicitied to develop proposals to help resolve the issues on Friday afternoon.

Thursday, 9 December

8:00 Transportation leaves from Hotel to IBM

8:15 - 8:30 Continental Breakfast

8:30 - 8:40 Preliminaries

• Introductions
• Review of agenda

8:40 - 9:40 Introduction and Definitions

• LC#117: How are exception cases determined and by whom?
• LC#119: Proposed narrowing of scope in definition of "applicability" (ALSO: Put back in conformance section? -IJ)
• LC#128: Extend definition of focus to include GUI control focus
• LC#137: Use of terms for disabilities, impairment
• LC#144: Editorial changes to some Guideline titles suggested
• LC#173: Proposed revision of "native" to account for OS features

9:40 - 10:20 Guideline 1. Support input and output device-independence

• LC#141: Need to qualify checkpoint 1.4 in same was as 1.1 is qualified re: "every"
• LC#142: Checkpoint 1.5 (output device-independence) needs clarification.
• LC#152: Proposed checkpoint: "Do not constrain the accessible output by constraints of the existing presentation"
• LC#172: Some clarification required in 1.1

10:20 -10:30 Break

10:30 - 11:20 Guideline 2. Ensure user access to all content

• LC#138: "Synchronized equivalent" v. "Continuous Equivalent"/ Proposed split of 2.5
• LC#140: Clarification on 2.3 required: how do you satisfy it if you don't support a language?
• LC#143: Proposed deletion of 2.6 since special case of 2.2
• LC#168: Checkpoint 2.7: Add object name in addition to type.
• LC#174: Natural language identification issues.

11:20 - 12:00 Guideline 3. Allow the user to turn off rendering or behavior that may reduce accessibility

• LC#145: Why is 3.7 Pri 1 and 3.10 Pri 3? (Re: blinking and flashing)
• LC#167: Proposed checkpoint to allow users to turn on/off multilingual support.
• LC#169: What UI is required for turning on/off features that may impede accessibility?

12:00 - 1:00 Lunch

1:00 - 2:10 Guideline 4. Ensure user control over styles

• LC#115: Checkpoint to maintain relative font sizes?
• LC#118: User Interface for text size (font size) control
• LC#132: Checkpoint 4.17 (Note): User should not be able to turn off default styles
• LC#135: Add incremental forward/rewind for audio, video, speech?
• LC#151: Proposed checkpoint: change audio rate without changing pitch

2:10 - 3:00 Guideline 5. Observe operating system conventions and standard interfaces

• LC#114: How do requirements for APIs overlap (DOM? Platform standards? Provided by Tool)
• LC#120: The UAGL should pay more attention to UI accessibility
• LC#121: Consider reordering/grouping the checkpoints/Guidelines (e.g., accessible content/accessible UI)
• LC#122: Proposed checkpoint related to input focus on controls
• LC#123: Proposed checkpoint to use standard UI components for the interface.

3:00 - 3:20 Break

3:20 - 4:30 Guideline 5. Observe operating system conventions and standard interfaces

• LC#124: Should the Guidelines reference MSAA and JAAPI?
• LC#113: Deletion of Guideline 2: Support the Keyboard
• LC#116: Non-editorial issues raised by Eric Hansen
• LC#147: Need to review priority and wording of 5.8
• LC#150: Do APIs apply when the software is accessible on its own?
• LC#154: Proposed requirement that UAs give access to style sheet classes
• LC#165: Add information about system level flags to 5.2

4:30 - 5:00 Guideline 6. Implement open specifications and their accessibility features

• LC#111: Proposal to make Checkpoint 6.1 have a relative priority
• LC#157: Correct reference to XSL in checkpoint 6.2 since only a Working Draft.

Dinner at local restaurant

Friday, 10 December

8:00 Transportation leaves from Hotel to IBM

8:15 - 8:30 Continental Breakfast

8:30 - 8:40 Guideline 7. Provide navigation mechanisms

• LC#160: Delete checkpoints 7.3 and 8.2 (related to tables) since too vague

8:40-9:10 Guideline 8. Help orient the user

• LC#160: Delete checkpoints 7.3 and 8.2 (related to tables) since too vague
• LC#163: Proposed new checkpoint on "Favorites" functionality

9:00 - 9:10 Guideline 9. Notify the user of content and viewport changes

• LC#148: Checkpoint 9.6: Does RETURN count as explicit submit?

9:10 - 10:10 Guideline 10. Allow the user to configure the user agent

• LC#112: Split checkpoint 10.1 into two separate checkpoints for author and user agent input functionalities and mark as an issue during last call
• LC#129: Need to clarify 10.3 ("Allow the user to change and control the inputconfiguration. Users should be able to activate a functionality with a single-stroke (e.g., single-key, single voicecommand, etc.).)
• LC#130: Proposed rewording of 10.5: Avoid default > > input configurations that conflict with operating system navigation, control, and access conventions.
• LC#131: Proposed change in wording of 10.8
• LC#134: Proposed modification of 10.3: "The controls mustbe user-selectable."
• LC#149: 10.6: Wording (delete "and software") and Priority.

10:10 - 10:20 Break

10:20 - 10:30 Guideline 11. Provide accessible product documentation and help

• None, review guideline for any possible interactions with other changes

10:30 - 12:00 Other Issues

• LC#113: Deletion of Guideline 2: Support the Keyboard
• LC#116: Non-editorial issues raised by Eric Hansen
• LC#120: The UAGL should pay more attention to UI accessibility
• LC#121: Consider reordering/grouping the checkpoints/Guidelines (e.g., accessible content/accessible UI)
• LC#136: Proposal for checklist delivery (part of conformance)
• LC#153: Hold off on conformance until functional requirements between browsers/ATs more defined?
• LC#170: How can UAs "stay" accessible when there is a mass of inaccessible content?

12:00 - 1:00 Lunch

1:00 - 2:30 Priority Changes Only

• LC#133: Priority of 10.1 compared to 10.3
• LC#146: Review priorities of 4.16, 5.2, 8.3, 8.5, 10.3, 10.6
• LC#155: Propose change of priorities for checkpoints 5.3 (r/w access) and 10.3 (single key)
• LC#156: Propose change in priority of 5.6 (P1 -> P2)
• LC#158: Propose priority change (1 to 2) for checkpoint 4.1 (control of font family)
• LC#159: Propose raise priority of 4.13 to Priority 1
• LC#161: Raise priority of 8.8 to P2 (highlighting and identifying selection/focus)
• LC#162: Raise priority of 8.9 (consistency in configs) to P2.
• LC#166: Review priority of 10.5 (default configs that interfere with OS conventions)
• LC#175: Proposed raise (to P1) of checkpoint 4.18
• LC#176: Proposed change in priority (P3 to P2) for checkpoint 8.7 (link information

2:30 - 2:45 Break

2:45 - 4:45 Discussion of unresolved actions items

4:45 - 5:00 Review of action items from meeting and discussion of guideline scheduling for proposed recommendation