W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2012

[Bug 18385] Programmatic association of a page element to a 'description' text in a different uri

From: <bugzilla@jessica.w3.org>
Date: Tue, 11 Sep 2012 14:08:21 +0000
Message-Id: <E1TBR8X-0002fB-Ih@jessica.w3.org>
To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18385

--- Comment #12 from Devarshi Pant <devarshipant@gmail.com> 2012-09-11 14:08:21 UTC ---
> If you want a visible description, make it visible and point at it with
> aria-describedby.
> (Requiring sighted keyboard users to use a secondary action on a control just
> to get additional explanation seems like terrible UI by the way.)

Your point is taken, but I disagree, there is no terrible UI when content is
accessible. If aria-describedby points to visible text, how does a sighted user
or a magnifier user track focus to the visible description. It will depend on
how aria-describedby is implemented here, like any other technique.

> I don't get how @longdesc would help here given the target of @longdesc would
> be outside the table too.

Well, using longddesc, the keyboard focus will land on the link that was
selected once the target dialog is closed, thus preserving focus. Technically,
I do not see any issue there, unless implementers have UI issues.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 11 September 2012 14:08:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 September 2012 14:08:27 GMT