- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Tue, 15 Sep 2009 15:10:03 -0500
- To: Jim Jewett <jimjjewett@gmail.com>
- Cc: HTML WG Public List <public-html@w3.org>, public-pfwg-comments@w3.org, public-pfwg-comments-request@w3.org
- Message-ID: <OF4CC587A3.648B6BF0-ON86257632.006E684E-86257632.006EC8B7@us.ibm.com>
Jim, I am not quite sure what you are askign but the ARIA working group resolved have this be a collection of one or more IDs. longdesc was a disaster. The id should refer to the text that describes the object. aria-describedby can take multiple ids and they should be processed in order or you can have a container, say a div that contains all the text. Rich Rich Schwerdtfeger Distinguished Engineer, SWG Accessibility Architect/Strategist Jim Jewett <jimjjewett@gmail .com> To Sent by: HTML WG Public List public-pfwg-comme <public-html@w3.org>, nts-request@w3.or public-pfwg-comments@w3.org g cc Subject 09/15/2009 02:32 aria-describedby vs longdesc [was: PM Re: Opera 10.10 recently added longdesc support] Laura L. Carlson wrote: > (NOTE: it is understood that aria-describedby cannot point off page directly.) Ouch. Is it too late to allow URLs in place of IDREFs? (IDREFs could of course still be done as #fragments.) Or, at the very least, could the link suggestion be explicitly added -- that aria itself would say that if the target ID is a link, then the description is in the target of the link, rather than its contents? (HTML5 could probably do this by itself if it needs to ... but this seems like something that ought to be fixed at the source level -- in this case, the aria spec.) -jJ
Attachments
- image/gif attachment: graycol.gif
- image/gif attachment: pic19302.gif
- image/gif attachment: ecblank.gif
Received on Tuesday, 15 September 2009 20:10:56 UTC