W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 1999

AGENDA: W3C WAI User Agent Telecon 9 June 1999

From: Jon Gunderson <jongund@staff.uiuc.edu>
Date: Tue, 08 Jun 1999 10:27:01 -0500
Message-Id: <199906081526.KAA05430@staff2.cso.uiuc.edu>
To: w3c-wai-ua@w3.org
Please RSVP to the chair (jongund@uiuc.edu) if you are going to attend or not.
Thanks for your cooperation,

WAI UA Telecon for June 9th, 1999

Chair: Jon Gunderson
Date: Wednesday, June 9th
Time: 12:00 noon to 1:30 pm Eastern Standard Time
Call-in: W3C Tobin Bridge (+1) 617-252-7000


Review of open action items
Editors: Incorporate resolutions into next draft of document.
IJ: Write DJW about requirements T&S/WAI. Wrote thrice, no reply. Will
follow up.

IJ: Editorial action items
CMN: Write techniques for 7.2.2 and 7.2.6 CMN deferred until publication of
Note by Rich and Mark.

JG: Techniques for 7.2.2.

MN: Post references to mechanisms that can be used for applications to
exchange information for various operating systems: UNIX/X-Windows,
Microsoft windows, Apple Macintosh and Java

IJ: Implement proposal to simplify the guidelines, separate techniques from
checkpoints, make checkpoints more global, move technichy checkpoints to
technique document.

IJ: Include specific navigation checkpoints for the following elements:
forms, form controls, tables, in next draft

Include checkpoint: Scripting events should be part of navigating to active
content checkpoint
Include checkpoint: Allow user to configure elements that are part of
active contents
Include checkpoint: Allow user to simulate event activator that an element
could respond to
Include checkpoint: Orient user to events an element can respond to
Include checkpoint: Allow user to navigate to elements that can respond to
Include checkpoint:: Add checkpoint: turn on/off access key at priority 2

Review of open issues from the last 2 months

PROPOSED Saving form state: Saving filled in forms (Al)
Proposed resolution: Discussion with group

PROPOSED: Need to support "until user agent" clauses from WCAG.
Proposed resolution: add checkpoints to issued list

PROPOSED: Combine 6.1.9 and 6.1.11. Provide info in techniques doc.
http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0284.html Also,
drop "fee link" part of example.
Resolution proposal: Document status information, see results in next draft

PROPOSED Checkpoint: Allow the user to search for content.
Resolution Proposal: Already covered in 31 March draft

PROPOSED Checkpoint: for natural language
Resolution proposal: Checkpoint related to natural language Pirority 1 in
Web Content and should have same level of attention in user agent
guidelines for compatibility

PROPOSED priority change to 5.2.9 -> 1.
http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0285.html (Allow
the user specify that audio descriptions of video be rendered at the same
time as the video.)
5.2.8 [Priority 1] Allow the user to specify that captions or descriptions
for video be rendered at the same time as the video.
5.2.9 [Priority 2] Allow the user to specify that audio descriptions of
video be rendered at the same time as the video.
Resolution proposal: Merge 5.2.8 and 5.2.9 in 31 march draft

PROPOSED rewrite of 6.3.2 and 6.3.3 (CMN)
6.3.2 [Priority 2] Alert the user when scripts or applets are executed.
6.3.3 [Priority 3] Provide information about document changes resulting
from the execution of a script.
Resolution proposal: Include checkpoint related to notification of document

PROPOSED additional functionaility: Do you want to provide some audio
feedback as to audio length, either before it plays, or when paused, etc. ?
Resolution proposal: Next document there will be better information on
summary document. Do we need a checkpoint or more desciption in a technique
about summary information?

PROPOSED additional functionaility: For searches, do you need to define
"which" attributes can be used, given this is a priority #1 item ? (Also,
proposed change to Pri 2).
Resolution proposal: Lets review after next working draft

PROPOSED Priority Change: 5.3.4 Allow the user to move the focus to a link
based on its integer (tabbing-order) position, to Priority 2 since info
accessible without it.
Resolution proposal: Lets review after next working draft

PROPOSED select form control functionaility: Proposed advice in techniques
about keyboard access to menus.
Resolution proposed: Authoring issue

PROPOSED: Reorder guidelines according to importance of guideline. (Ian
Resolution proposal: Wait until guidelines more stable

PROPOSED: Need to give user final control over accesskey settings. UAGL
shouldn't specify UA error behavior.
Resolution proposal: User control over keyboard bindings related to 4.3.1
what do about access keys and final control similar to styles

PROPOSED deletion: 4.1.1: Ensure that the software may be installed in a
device-independent manner using any supported input and output devices.
Resolution proposal: Discussion at meeting
Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
University of Illinois at Urbana/Champaign
1207 S. Oak Street
Champaign, IL 61820

Voice: 217-244-5870
Fax: 217-333-0248
E-mail: jongund@uiuc.edu
WWW:	http://www.staff.uiuc.edu/~jongund
Received on Tuesday, 8 June 1999 11:26:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:22 UTC