WAI UA Telecon for February 15th, 2001
 
 
	 Chair: Jon Gunderson
		 
 Date: Thursday, 15 Febraury 2001
		Time: 2:00-4:00 pm Eastern Standard Time, USA
		Call-in: Longfellow Bridge (+1) (617) 252-1038
 
 
	  
	  
	 Announcements 
 
	  
		- Register for User Agent face-to-face meeting in Boston on 1-2 March
		  2001
  
	 
 
	 Discussion
 
	  
		- Coordination of joint meetings with DOM and CSS
  
		- Issue
		  443: Checkpoint 1.4: Device indepdent access to pointer (mouse) specific
		  events. 
Source:
		  http://server.rehab.uiuc.edu/ua-issues/issues-linear-lc2.html#443
Status:
		  The document currently requires emulation of mouse-specific controls by virtue
		  of our requirement that the user must be able to do everything through the
		  mouse. 
Discussion: 
a) Do we want to require the UA to
		  repair device-specific bindings specified by the author? 
b) Do we have
		  evidence that the ability to simulate mouse events through the keyboard
		  benefits the user?  
		- Definition Issues: 
		  
 
			 - Issue 359: Definition: text content (incompatible with WCAG?)
				
  
			 - Issue 358: Definition: Equivalent 
  
			 - Issue 322: The definition of the word element 
  
			 - Issue 321: Equivalency relationships and the wording of
				checkpoint 2.3
  
			 - Issue 394: Checkpoint 2.1: Vague about what cannot be provided
				through a source view
  
		  
  
	 
 
 
	 Attendance
 
	 Chair: Jon Gunderson
 
	 Scribe: Ian Jacobs
 
	 Present: 
David Poehlman
Harvey Bingham
Mickey
		Quenzer
Gregory Rosmaita
Tim Lacy
 
	 Regrets:
Denis Anson
Eric Hansen
Jim Allan
	 
 
	  
	  
	  
		- IJ, EH, AG: Propose new definitions forterms in question
		  (equivalence, text element, etc.)
  
		- IJ: Coordinate usability testing of the guidelines (JRG volunteers to
		  be one of the testers).
Source:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0137.html 
		
		- IJ: Write an executive summary appendix.
Source:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0200.html 
		
		- JG: Implementation information for guideline 2
  
		- JG: Propose text for the techniques document about synthesized speech
		  implementation issues. Notably UA and AT wanting to use the same synthesizer
		  engine.
  
		- JG: Create issue list for things that need to be addressed in the
		  next version of the document
  
		- GL: Ask someone from Microsoft whether they will evaluate the
		  guidelines with a product. 
Deadline: 2/1/2001
Source:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0137.html 
		
		- GR: Review checkpoints in Guideline 10 for implementation information
		  
  
		- JA: Review checkpoints in Guideline 4 for implementation
		  information
  
	 
 
	  
	 
		- IJ: Send an email about CSS issues to take to the CSS WG. Confirm
		  that IJ will attend CSS meeting earlier in the week to discuss WAI
		  issues.
Source:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0227.html 
		- IJ: Write a proposal trying to define repair requirements for
		  pointing device specific event handlers we might include in the
		  guidelines.
Source:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0227.html 
		- TL: Report to WG on discussions at Microsoft about keyboard
		  emulation.
Source:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0227.html 
	 
 
	  
	 
		- IJ: Send email to list asking for input on scope of checkpoint 1.1
		  including emulation of device specific behaviors
Source:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0193.html
Done:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0203.html 
		- JG:
		  Talk
		  to Al Gilman at the next WAI CG meeting about a joint meeting with UA, PF, and
		  Voice WG (or participants) to discuss accessibility issues.
Source:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0083.html
Done 
		- JG: Ping AOL to see if they can attend
Source:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0193.html
Done 
		- JG: Ask WAI PF/WAI ER/WAI CG about their experience with repair of
		  device-specific event handlers and indicate that we are leaning towards
		  lowering the priority of repair here. 
Source:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0200.html
Done:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0203.html 
		
		-  JG: Send an outline of what should be in a executive summary.
		  
Source:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0200.html
Done:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0220.html 
		- EH: Send thoughts on what should be in a executive summary.
		  
Source:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0200.html
Done:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0221.html 
		- RS: Find out what HPR's intentions are re: repair of device-specific
		  event handlers.
Source:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0200.html
Done:
		  http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0226.html 
		- KB: Submit technique on providing information on current item and
		  number of items in search
Cancelled