ISSUE-108: The implementors guide should ensure a unique ID for each accessible object in the accessibility API

Unique Accessibility API ID

The implementors guide should ensure a unique ID for each accessible object in the accessibility API

State:
CLOSED
Product:
ARIA HTML 5 Implementation Guide
Raised by:
Richard Schwerdtfeger
Opened on:
2009-02-09
Description:
The assistive technology needs to refer to a unique object ID such as when objects are added or removed to present the appropriate information to the user. For example, in a live region where objects are removed the AT needs to be able to get the object from the ID that is being removed to announce what was deleted.

This is the task of the user agent and not the author.
Related Actions Items:
No related actions
Related emails:
No related emails

Related notes:

See 9 Feb UAI TF meeting minutes: http://www.w3.org/2010/02/09-aapi-minutes.html

David to get clarification from Rich on why this is needed.

Andi Snow-Weaver, 9 Feb 2010, 17:20:33

Closing as obsolete.

Joanmarie Diggs, 11 Apr 2018, 15:14:01

Display change log ATOM feed


Joanmarie Diggs <jdiggs@igalia.com>, James Nurthen <nurthen@adobe.com>, Chairs, Michael Cooper <cooper@w3.org>, Ruoxi Ran <ran@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $