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: Sun, 09 Sep 2012 22:07:55 +0000
Message-Id: <E1TApfX-00044F-B9@jessica.w3.org>
To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18385

Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bhawkeslewis@googlemail.com

--- Comment #9 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2012-09-09 22:07:55 UTC ---
(In reply to comment #0)
> Programmatically associate a control with a glossary term (brief description)
> in a different uri. For example, a developer creates a page called
> www.foo.gov/glossary.html and then ties a piece of text, say, 'glossary#1' to a
> control in www.foo.gov/pagexyz.html. This could be helpful in numerous
> situations:
> 1. Where the describedby text need not be visible on the same page.
> 2. When an image needs a description.
> 3. Link needs additional description.
> 4. Form control needs additional explanation.

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.

> 5. When a superscript needs to be associated.

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>

-- 
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 Sunday, 9 September 2012 22:07:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 9 September 2012 22:07:56 GMT