W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2000

AGENDA: W3C WAI User Agent Telecon 2 March 2000

From: Jon Gunderson <jongund@ux1.cso.uiuc.edu>
Date: Wed, 01 Mar 2000 15:52:47 -0600
Message-Id: <4.1.20000301154949.00a5d3a0@staff.uiuc.edu>
To: w3c-wai-ua@w3.org
WAI UA Telecon for March 2nd, 2000 

Chair: Jon Gunderson 
Date: Thursday, March 2nd
Time: 2:00 pm to 3:30 pm Eastern Standard Time, USA
Call-in: Longfellow Bridge (+1) (617) 252-1038

Agenda

Review Open Action Items (see below)

Announcements 

none

Discussion 

The following are the current issues and a proposed resolution

----------------------
Issue CR#196: It is unclear to developers how they know they conform to
Checkpoint 6.2: Conform to W3C specifications when they
are appropriate 

http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#196

Proposed Resolution: 

   1.Change wording "Use and conform to W3C specifications when they are
available and appropriate for a task." 
   2.Add note: Implementing one accessible format 
   3.Add techniques: From ATAG "Specifications that become W3C
Recommendations after an authoring tool's development cycles permit
     input are not considered "available" in time. " 

----------------------
Issue CR#197: Not clear with the scope of user preferences is in Checkpoint
10.7 

http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#197

Proposed Resolution: 

   1.Narrow scope to style and input configuration 
   2.Add technique: Accessible browser project portable configuration file 

----------------------
Issue CR#198: How much information needs to be provided to satisfy
Checkpoint 8.4 

http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#198

Proposed Resolution: 

   1.Make current list of items is minimum requirement, plus any that we
may have missed 

----------------------
Issue CR#199: Poor wording of checkpoint 10.8, it is not clear what the
requirement is to improve accessibility 

http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#199

Proposed Resolution: 

   1.Ensure that the most frequently used functions are the most easily
activated in the default configuration. 
   2.Add technique: Show operating system conventions 

----------------------
CR#200: Checkpoint 5.5 on timely exchanges, developers not unclear on how
they know they have satisfied this checkpoint

http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#200

Resolution Options: 

   1.Merge requirement in with other applicable checkpoints
     http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0359.html 
   2.Ian's pending proposal 

----------------------
CR#201: 5.5 "Ensure that programmatic exchanges proceed in a timely manner"
should be a priority 1 

http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#201

Resolution Options: 

   1.Merge requirement in with other applicable checkpoints
     http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0359.html 
   2.Ian's pending proposal 

----------------------
CR#202: User agent configuration to render NOFRAMES content 

http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#202

Proposed Resolution: 

   1.HTML 4.0 Specification issues related to NOFRAMES rendering
     http://www.w3.org/TR/html4/present/frames.html#h-16.4.1 

----------------------
CR#204: Add collated text to Checkpoint 2.6 and 4.8 or create a new
checkpoint at lower priority 

http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#204

Proposed Resolution: 

   1.Add collated text to checkpoints
     http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0343.html 

----------------------
CR#205: Timing issues related to AT missing or not being synchronized to
document changes 

http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#205

Resolution Options: 

   1.Merge requirement in with other applicable checkpoints
     http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0359.html 
   2.Ian's pending proposal 

----------------------
CR#206: Precise specification of what parts of DOM are required 

http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#206

Resolution Options: 

   1.Add W3C DOM level 2 Event Module at Priority 2
     http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0359.html 
   2.Do not include rteference to DOM Event Model 

===========================
Open Action Items

   1.IJ: Propose checkpoint to address event notification timing issue 

   2.IJ: Split checkpoint 5.1 (28 January Draft) into read and UI write as
stated in minutes 

   3.IJ: Add a cross-reference from 2.1 to 5.1 and say in 5.1 that this is
a special case of 2.1 

   4.IJ: Add techniques to checkpoint 7.2 for synchronous multi-media
presentation (space and time) 

   5.IJ: Ensure that techniques for checkpoint 1.5 talk about using status
bar to display message 

   6.IJ: Incorporate proposal for checkpoint 1.5 from minutes 

   7.IJ: Add rationale to Checkpoint 1.5: if you're deaf blind you might
need this (Braille display). 

   8.DB: Ask IE Team about publication of review of IE 5 and Pri 1 checkpoints 

   9.DB: See if microsoft can produce HTML version of their developer
guidelines 

  10.JA: Rewrite techniques for 3.3 (see minutes) 

  11.MK: For 4.8 check if any media players do this? 

  12.MK: Find out techniques for sending text search requests to servers of
streamed text. 

  13.MR: Review techniques for topic 3.1 (Multi-media) 

  14.MR: Review techniques for Guideline 4 (Multi-media) 

  15.RS: Take timely and synchronization issues to WAI PF. Get input from
MSAA developers as well. Craft email to PF WG with Ian 

Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Chair, W3C WAI User Agent Working Group
Division of Rehabilitation - Education Services
College of Applied Life Studies
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
WWW: http://www.w3.org/wai/ua
Received on Wednesday, 1 March 2000 16:51:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:49:52 GMT