ISSUE-690: Implementor concerns for UA requirements in #aria-describedat

UA reqs for describedat

Implementor concerns for UA requirements in #aria-describedat

ARIA 1.1
Raised by:
James Craig
Opened on:
Raising issue based on list discussion continued here:

Several implementors have expressed concern that mainstream UI requirements for "describedat" are problematic. They should be addressed more like tabindex (defer to a host language feature), or removed from the spec.

The text in question is:

User agents SHOULD provide a device-independent mechanism to allow a user to navigate the user agent to content referenced by the aria-describedat attribute. User agents SHOULD also provide a device-independent mechanism to return the user's focus from the descriptive content view to the original content view. For example, a user agent may provide access to the document or document fragment referenced by the aria-describedat attribute in a contextual menu associated with the object.
Related Actions Items:
No related actions
Related emails:
No related emails

Related notes:

While we could defer to host language features like longdesc, one of the other requests was from SVG working group members who wanted it for the Diagram effort.

We have to address this issue and we should also bring George Kirscher back in to discuss this. Perhaps after the January 8, 2014 meeting.

Richard Schwerdtfeger, 2 Jan 2015, 18:00:16

Closed. no aria-describedat in ARIA 1.1

Richard Schwerdtfeger, 7 Apr 2016, 17:23:04

Display change log ATOM feed

James Nurthen <>, Valerie Young <>, Chairs, Daniel Montalvo <>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 690.html,v 1.1 2023/05/22 16:31:58 carcone Exp $