6.10 Timely exchanges through APIs

> ACTION: PP to Write up a few examples of situations where an API 
exchange is too slow

Situations in which an API exchange is too slow include, but are not 
limited to, the following:

1. The user agent updates the content in the active view but does not 
indicate the change through the API in a timely manner such that an AT can 
update its cached content before the next user query or command. As a 
result, the user ends up working with stale content.
2. The user agent processes user input but does not indicate confirmation 
through the API in a timely manner such that the user knows the input was 
received. As a result, the user is apt to think the input was lost and 
repeat the action.

Example techniques

1. On Linux, use AT-SPI document events to indicate global changes to a 
document and object events to indicate changes to portions of the content.

Peter Parente
IBM Linux Accessibility Project
pparent@us.ibm.com
Tie: 526-2346
UNC: 919-962-1780
IBM: 919-486-2346



Jan Richards <jan.richards@utoronto.ca> 
Sent by: w3c-wai-ua-request@w3.org
09/14/2006 03:17 PM

To
WAI-UA list <w3c-wai-ua@w3.org>
cc

Subject
re: User Agent Teleconference for 13 September 2006







Here are the notes from today's call:

http://www.w3.org/2006/09/14-ua-minutes.html

Action items:

ACTION: CL to Write a bit about speech engines and braille devices 
needing lang and locale info.

ACTION: JA to Follow up on 2 issues with 6.9 - events and content 
insertion

ACTION: PP to Write up a few examples of situations where an API 
exchange is too slow

ACTION: JA to update review chart and send to list