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

[Bug 10455] Mint a describedby attribute for the img element

From: <bugzilla@jessica.w3.org>
Date: Thu, 02 Sep 2010 22:03:34 +0000
To: public-html-a11y@w3.org
Message-Id: <E1OrHsc-00056A-74@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10455





--- Comment #76 from Gregory J. Rosmaita <oedipus@hicom.net>  2010-09-02 22:03:33 ---
(in response to comment #70)

benjamin -- i agree with your recipe for providing meaningful verbose
description generation:

QUOTE
  - Create a separate HTML page containing your long description.  Identify
your "img" element with a unique "id" attribute (e.g. "my-image")

  - Put an empty "span" element beside it to hold machine-readable information
about how to locate the long description.

  - Set the "resource" attribute of the "span" to the URL of the long

  - description.  Set the "about" attribute of the "span" to reference the

  - "img" element (not the image source) by fragment URL by putting a hash sign
before the "id" value (e.g. "#my-image").

  - Set the "rel" attribute of the span to "longdesc" to indicate the resource
is a long description for the subject of the "about" attribute (i.e. the "img"
element). 
UNQUOTE

in fact, i would encourage you to submit your step-by-step list for providing
verbose descriptors to the Authoring Tool Accessibility Working Group
(http://www.w3.org/WAI/AU/ for consideration and possible addition to
http://www.w3.org/TR/2010/WD-IMPLEMENTING-ATAG20-20100708/#principle_b2
"Implementing Principle B.2: Authors must be supported in the production of
accessible content") 

NOTE: the Authoring Tool Accessibility Guidelines version 2.0's last call
review period ends today, 2 september 2010 -- the last call draft is available
at http://www.w3.org/TR/2010/WD-ATAG20-20100708/ whilst comments should be sent
to: public-atag2-comments@w3.org

personally, i am an ardent advocate of RDFa, its use and deployment, but as a
user dependent upon assistive technology, i am more concerned at this point in
the webolutionary proccess that AT developers more consistently and completely
support ARIA before i would expect or demand that they be able to parse RDFa...

of course, in the best of all possible worlds, assistive technologies would be
implementing support for both ARIA and RDFa, for RDFa notation could be
leveraged by an assistive technology to make a user's interaction with content
marked-up with RDFa a far richer and meaningful by providing explicit
annotations that could be used for selecting, sorting, navigating, and a far
fuller discovery of the annotated content; especially when the material being
annotated comprises educational materials, historical documents, or legal or
medical records

-- 
Configure bugmail: http://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 Thursday, 2 September 2010 22:03:37 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:13 UTC