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: Mon, 10 Sep 2012 14:12:57 +0000
Message-Id: <E1TB4jR-0007sC-Q3@jessica.w3.org>
To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18385

--- Comment #10 from Devarshi Pant <devarshipant@gmail.com> 2012-09-10 14:12:57 UTC ---
(In reply to comment #9)
> In all these cases, if the description works as plain text, you can just hide
> the referenced describing element using @hidden. You can reference an iframe if you want to reuse the text elsewhere.

How would sighted keyboard users (even non-disabled users) access this
information if we use @hidden? Also, based on the response from Laura, longdesc
could be a viable alternative here -- it is accessible to everyone.

> What's wrong with an ordinary link here?
> <th abbr="2013 estimate">2013 estimate<a href=note-5
> rel=help><sup>5</sup</a></th>

Nothing is wrong with your suggestion, but table navigation with screen reader
is burdensome when keyboard focus shifts because the target (footnote) is
outside the table. For large tables that reference footnotes from within <td>
or even <th>, managing focus for most user groups can be diffcult. Here
longdesc, when used, can be helpful.

-- 
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 Monday, 10 September 2012 14:13:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 10 September 2012 14:13:07 GMT