- From: Jon Gunderson <jongund@staff.uiuc.edu>
- Date: Fri, 05 Mar 1999 14:42:42 -0600
- To: w3c-wai-ua@w3.org
Date: Fri, 05 Mar 1999 14:39:42 -0600 To: Charles McCathieNevile <charles@w3.org> From: Jon Gunderson <jongund@staff.uiuc.edu> Subject: Re: PROPOSAL: Information that needs to be exhanged between Descktop Graphical User Agents and Dependent Assistive Technology DOM currently does not provide all the information that assistive technology developers say they need to make browser technology more accessible. Some of the major limitations of the current DOM are: 1. Lack of support for simulating both UI and scriting control events 2. Lack of information about rendering position of an element 3. Lack of information about UI controls, menus and dialog box information We want to as precisely as we can identify the information that needs to be exhanged between a user agent and assistive technology. In this way it can be used to guide both DOM development and accessibility APIs. May the user with a disability win!! Jon At 02:07 PM 3/5/99 -0500, you wrote: >>If we are already going to require DOM, then we can shorten this list >>considerably: >> >>User interface Controls >>elements of the DOM >> >>Charles McCN >> >>On Wed, 3 Mar 1999, Jon Gunderson wrote: >> >> Information that needs to be provided by the Desktop Graphical user Agent >> through interoperable interface >> >> User Interface Informaton >> 1. Menus >> 2. Dialog boxes >> 3. Toolbars >> 4. Keyboard bindings >> 5. Changes in focus >> >> Content Rendering >> Block level elements >> 1. Element type >> 2. Rendering order in the document >> 3. Rendering graphical position and size on visual display >> 4. Text content >> 5. Accessibility attributes >> IMG: Alt, title, longdesc >> APPLET: ALT >> LABEL: FOR >> DIV: CLASS >> LINKS and FORM controls: ACCESSKEY >> 6. Font and font style characterisitcs >> 7. General element attibutes >> 8. Which document (frame) the element is associated with >> >> In-line level elements >> 1. Element type >> 2. Rendering position and size on visual display >> 3. Element attributes >> >> TABLES >> 1. Row and column position in table >> 2. Individual cell contents >> 3. Table element type (TD or TH) >> 4. Table cell attributes >> 5. Explicit header cell references >> >> FRAMES >> 1. List of documents in frameset >> 2. Move focus to another document in frameaset >> 3. Frame which has the current focus >> >> FORM CONTROLS >> 1. Control type >> 2. Control state >> 3. Control text >> 4. Control label information >> >> SCRIPTING EVENTS >> 1. Indentification of elements with explicit event handlers >> 2. Event handler type >> 2. Simulation of event handler activation >> >> >> >> >> 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 >> http://www.als.uiuc.edu/InfoTechAccess >> >> >>--Charles McCathieNevile mailto:charles@w3.org >>phone: +1 617 258 0992 http://purl.oclc.org/net/charles >>W3C Web Accessibility Initiative http://www.w3.org/WAI >>MIT/LCS - 545 Technology sq., Cambridge MA, 02139, USA >> 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 http://www.als.uiuc.edu/InfoTechAccess
Received on Friday, 5 March 1999 15:44:39 UTC