Chair: Jon Gunderson
Date: Wednesday, January 19th
Time: 12:00 pm to 1:30 pm Eastern Standard Time, USA
Call-in: Longfellow Bridge (+1) (617) 252-1038
Chair: Jon Gunderson
Scribe: Ian Jacobs
Gregory J. Rosmaita
1.IJ: Update document with resolutions for issue LC#162
2.IJ: Update document with resolutions for issue LC#166
3.IJ: Update document with resolutions for issue LC#175
4.IJ: Update document with resolutions for Issue LC#176
5.IJ: Repropose checkpoint 1.5
6.IJ: Add info related to searching for non-rendered information (or
searches using voice output user agents) to appendix
Need to verify.
7.IJ: Adopt changes in wording for Checkpoint 1.1
8.JG: Find a host/date for next FTF meeting
9.JG: Take issue of mobile devices/guidelines in next WAI CG meeting.
10.CMN: Follow up on this with some learning disability people on graphical
11.DA: Follow up with Alan Cantor on what is the critical component(s) for
graphical configuration (done by email during meeting)
12.DB: Send proposal for single key access wording for checkpoint 10.3
13.DB: Ask IE Team about publication of review of IE 5 and Pri 1
14.DB: Find out how developers find out which appropriate triggers to use
in Windows for using built-in accessibility features (i.e. sound sentry, show
15.DP: Propose new Checkpoint 1.5 for access to system messages
16.GR: Send to the list techniques for how to use and control focus to not
have new windows cause problems for usability. In particular, how this will
work with ATs.
Pending. Will ask RS at PF face-to-face.
17.GR: Send screen shot of JFW link list to the list
18.GR: Remind DP of this action to proposed new text for checkpoint 1.5
19.MK: Find out techniques for sending text search requests to servers of
20.MR: Review techniques for topic 3.1 (Multi-media)
21.MR: Review techniques for Guideline 4 (Multi-media)
22.MR: Run a multimedia player through the guidelines for January.
23.MQ: Ask Mark about meaning of comment raised in Issue #167
24.MQ: Ask Mark Hakkinen about telephone browsers and the guidelines.
25.WC: Take form submission to GL WG to discuss issues related to
Regular UA telecon scheduled 20 January 2000 at 2:00 pm to 3:30 pm Eastern
Standard Time, USA
IJ: Once we get the issues resolved (tomorrow), the WG needs to say
"We want to go to CR".
- Aim for 24th for CR.
- Aim to resolve all issues (and document objections) by tomorrow.
- Update materials for Friday.
Action DB: Schedule time with IE team for next tuesday when CMN will be in Seattle to review the CR if ready.
KB: What if all developers say "We don't expect to satisfy these 5 or they shouldn't be on the list?"
IJ: Valuable information that should be considered by the WG.
JG: We have an invitation from RFBD (Princeton, NJ). PWWorks may be "co-host".
No objections to general location (east coast).
- new short names
- some new text in there awaiting WG approval.
HB: I think "concurrent" is better than "simultaneous".
Action IJ: Make change for 2.1 note.
IJ: Note the change - no longer required only on systems with multiple users.
HB: Reword to be "through a profile".
Action IJ: Make change with clarification.
KB: Required by "whom"?
IJ: The markup language definition, not WCAG.
Action IJ: Make change wtih clarification.
Refer to DB's proposal:
DB: Sticky keys on means that you accomplish something with single keys in sequence.
JB: I think we want to highlight that you want really single key, direct access (e.g., "F4" and that's it). I think people want to highlight the ability to do this, but not make it an absolute requirement.
DB: I don't think you'll get developers to add single-key when sticky keys and sequences exist.
DP: I think the objective is to perform a single action with a single key.
KB: In IE, you can get to most of the functions, but can be very inefficient for some users. The goal (according to Bryan Campbell) is to let users configure a small number of single key bindings for important actions. Sequences ok for the rest.
DB: I think that this is less important than other accessibility features. I can, with sticky keys today, do some things faster than some users with a mouse.
JG: Refer to Alan Cantor's email about keyboard efficiency as well.
Consensus: We don't expect all functionalities to be bound to single keys at the same time.
IJ: Also, I think there are some contexts where you are inherently doing N things (e.g., the print control panel). I only mean "things that only require one step".
DP: Save input configurations in the user's profile.
JG: Note that this is possible in Word. We're asking for the functionality in user agents.
GR: Note that Opera is a user agent that recognizes different modes, so that in form edit mode, single key strokes aren't available to the user.
IJ: noted - there may be modes in which some single keys are not available (e.g., "p" should not be available in editing mode).
- Split 10.4 into two. Make single-key a special case of old 10.4.
Action Ian: Propose split to list. Priority 2 for new checkpoint.
Incorporate these pieces:
- Not all at once
- Some keys not available at certain times.
- Intended for one-step operations.
Refer to proposal from DP:
DP: Goal of not having my input be sent to the wrong window.
GR: I would like to talk to RS face-to-face about some of the focus issues.
JG: I have problems with "all output device APIs". Which ones? The printer?
JG: I think the goal is that messages are rendered through system controls.
IJ: I think the actual requirement is device-independent access to information. System controls are the best way to do this since ATs can monitor them.
IJ: I think 1.5 may be covered by 5.2, 9.1, and 5.6. However, 1.5 is P1.
JG: Problem of support for beeps: is morse code necessary?
DP: Refer to 9 December minutes as well.
- Modify 9.1 to include controls
- Add checkpoint to G4 to includes messages. In techniques talk about different priorities of messages.
- Modify 1.5 about mode-independence of messages. (Don't just use sound or animations).
Action IJ: Propose changes to the list.