Re: Drop longdesc, get aria-describedat?

On Fri, Mar 9, 2012 at 6:33 AM, John Foliot <> wrote:
> In the tools that support @longdesc, they do deliver on all 3 requirements,
> whereas today the Accessibility APIs have no mechanism in place to deliver
> the second and third functions: the AAPI can express that a thing is a thing
> (discoverability, via role and state), but the key other requirement of
> user-choice is a scripted-like function that the APIs currently cannot
> handle, because there is NOTHING in the Accessibility APIs that deliver
> these functions

Not entirely true. See for example:

> Additionally, "hiding" the longer text description using an ARIA mechanism
> *does* break the requirement for HTML rich content, as content not rendered
> on screen *is* processed by the APIs as string text today.

Also not entirely true, as I've pointed out to you before some of the
APIs support specifying accessible relations:

Benjamin Hawkes-Lewis

Received on Friday, 9 March 2012 07:11:45 UTC