- From: <schwer@us.ibm.com>
- Date: Mon, 6 Mar 2000 09:49:37 -0600
- To: Jon Gunderson <jongund@ux1.cso.uiuc.edu>
- cc: Ian Jacobs <ij@w3.org>, w3c-wai-ua@w3.org
I like your addition. Rich Rich Schwerdtfeger Lead Architect, IBM Special Needs Systems EMail/web: schwer@us.ibm.com http://www.austin.ibm.com/sns/rich.htm "Two roads diverged in a wood, and I - I took the one less traveled by, and that has made all the difference.", Frost Jon Gunderson <jongund@ux1.cso.uiuc.edu> on 03/06/2000 08:45:05 AM To: Richard Schwerdtfeger/Austin/IBM@IBMUS, Ian Jacobs <ij@w3.org> cc: w3c-wai-ua@w3.org Subject: Re: Suggested note to Checkpoint 5.5 on timeliness Ian and Rich, I like Rich's addition. I think it could be expanded to say "DOM implementation and other supported accessibility related interfaces". Jon > ><PROPOSEDRICH> >This checkpoint is designed to reduce delays that an assistive >technology user might experience due to communication overhead when >accessing >parts of your application such as your DOM. >Timely exchange is import for preventing loss of information, >a risk when changes in content occur faster than the >exchange with the assistive technology. One effective technique >for providing timely access is to allow assistive technologies to run >in the same process space as the user agent, thus eliminating >inter-application communication delays. ></PROPOSEDRICH> > >Rich Schwerdtfeger >Lead Architect, IBM Special Needs Systems >EMail/web: schwer@us.ibm.com http://www.austin.ibm.com/sns/rich.htm > >"Two roads diverged in a wood, and I - >I took the one less traveled by, and that has made all the difference.", >Frost > > >Ian Jacobs <ij@w3.org> on 03/03/2000 09:57:00 AM > >To: Jon Gunderson <jongund@ux1.cso.uiuc.edu> >cc: w3c-wai-ua@w3.org >Subject: Re: Suggested note to Checkpoint 5.5 on timeliness > > > > >Jon Gunderson wrote: >> >> Note to checkpoint 5.5: This checkpoint is designed to promote the use of >> APIs which provide efficient exchange of information between user agents >> and assistive technologies. Notably in multi-tasking operating systems >> this requires the ability to access the DOM and other Accessibility APIs >in >> process. In process communication eliminates the time delays which occur >> with out-of-process communication between applications. The time delays >> can result in slower response to user actions or potentially the user >> missing important information. > >I object. This says "requires", which I don't think we agreed to. >I though we agreed that in-process communication should be >highlighted as a technique. I propose the following edit: > ><PROPOSED> >This checkpoint is designed to reduce delays that an assistive >technology user might experience due to communication overhead. >Timely exchange is import for preventing loss of information, >a risk when changes in content occur faster than the >exchange with the assistive technology. One effective technique >for providing timely access is to allow assistive technologies to run >in the same process space as the user agent, thus eliminating >inter-application communication delays. ></PROPOSED> > > - Ian >-- >Ian Jacobs (jacobs@w3.org) http://www.w3.org/People/Jacobs >Tel/Fax: +1 212 684-1814 or 212 532-4767 >Cell: +1 917 450-8783 > > > 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 Monday, 6 March 2000 10:58:42 UTC