ISSUE-690: Implementor concerns for UA requirements in #aria-describedat
UA reqs for describedat
Implementor concerns for UA requirements in #aria-describedat
- State:
- CLOSED
- Product:
- ARIA 1.1
- Raised by:
- James Craig
- Opened on:
- 2014-12-11
- Description:
- Raising issue based on list discussion continued here:
http://lists.w3.org/Archives/Public/wai-xtech/2014Dec/0004.html
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.
Closed. no aria-describedat in ARIA 1.1
Richard Schwerdtfeger, 7 Apr 2016, 17:23:04Display change log
