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

[Bug 10853] New: HTML5 lacks a verbose description mechanism

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Sep 2010 13:52:45 +0000
To: public-html@w3.org
Message-ID: <bug-10853-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10853

           Summary: HTML5 lacks a verbose description mechanism
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: oedipus@hicom.net
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Verbose (As Long As Necessary) Descriptor Requirements

Purpose

The purpose of a verbose descriptor is to describe an image. Such a 
description is essential for users who can not see, but who need 
access to information contained in a graphic. While verbose 
descriptors provide an important accommodation for the blind and 
visually impaired, a verbose descriptor can also be used by those 
with an extremely limited viewport or with cognitive difficulties as 
a guide to navigating and comprehending the described image. This 
means that the exposition of a verbose descriptor must not be an 
"either-or" proposition; rather, the user should be able to control 
the means of exposing the verbose descriptor, including the ability 
to simultaneously view the contents of the image and the contents of 
the verbose description.

Programmatically Determinable

Programmatically determinable [1] relates to the information in web 
content. If technologies that are accessibility supported are used 
properly, then assistive technologies and user agents can access 
the information in the content (i.e., programmatically determine 
the information in the content) and present it to the user. For 
instance longdesc as an attribute should be used as a hook by user 
agents and asssistive technologies in order to notify the user that 
a long description exists, so even if longdesc is applied to an 
image that also serves as a link, it is programmatically possible 
to separate the activation of the longdesc for exposure from the 
UA's universal link activation action (which is usually activated 
with the ENTER key, the SpaceBar, or by mouse click), so that the 
linked image retains the expected behavior in response to user 
interaction while a discrete mechanism is used to retrieve the 
long description.


Issue

Due to the chairs' ruling, on HTML5 ISSUE-30 [2], excluding 
@longdesc, but failing to provide an alternate mechanism to 
provide the functions that had been provided through the 
HTML 4 attribute longdesc [3] there is currently no means of 
providing a programmatically bound verbose (as long as 
necessary) description for an image. Those functions are:

   1. A direct, reusable programmatic determinable mechanism to a 
      long description of an image without a forced visual 
      encumbrance or default visual indicator.

   2. A method to reference a longer description of an image, without 
      including the content in the main flow of a page. 

Many images cannot be sufficiently described with other long description 
techniques. For instance, longdesc currently provides a solution for 
describing the content of images to the blind when it would be:

    * Visually apparent and redundant to a sighted person.
    * Unacceptable to the marketing department due to aesthetic 
      considerations. 

There is currently absolutely no other direct way of doing that without 
a longdesc.


Requirements

   1. A programmatic mechanism to reference a specific set of 
      structured content, internal (enhanced describedby model) 
      or external (HTML4 longdesc model) to the document 
      containing the described image.

   2. A way to inform users and authors that a description is 
      present/available.

   3. A device independent way to access the descriptive content.

   4. An explicit provision that accessing descriptive content, 
      whether internal or external to the document containing 
      the image, does NOT take the user away from the user's 
      position in the document containing the image where the 
      verbose descriptor was invoked;

   5. A way to provide user control over exposition of the 
      descriptor so that rendering of the image and its 
      description is not an either/or proposition. (A visual 
      indicator of the description should NOT be a forced 
      visual encumbrance on sighted users by default).

   6. A method to reference a longer description of an image, 
      without including the content in the main flow of a 
      page. 


Satisfying These Requirements for HTML5

OPTIONS:

   1. retain support for longdesc; allow for exposition of longdesc 
      via user agent preference, context menu, or toggle inline as 
      well as for simultaneous exposition of both the image and its 
      description (useful for those with very limited viewports or 
      users with cognitive issues, who may need a description to 
      guide and to assist in the user's understanding of the image 
      being described);

          * advantage: 2 major browsers already support longdesc 
            natively and are expected to continue to do so as part 
            of their support for HTML4x; 

   2. add support for aria-describedby and deprecate longdesc in HTML5;

         * drawback 1: aria-describedby is currently limited to text 
           that appears in the same document as the image being 
           described;

          * drawback 2: The content associated using aria-describedby 
            as currently implemented, is limited to unstructured text; 

   3. add support for external references and structured content to the 
      aria-describedby attribute in HTML5 and deprecate longdesc;

   4. Mint a describedby attribute for the img element (HTML5 Bug 
      10455) [4]

Research

    * [5] Longdesc Examples In the Wild
    * [6] Longdesc Guidelines, Laws, Policy, and Standards 

Related Resources

    * HTML 5 Issue: Image Equivalent Content (HTML WG Wiki page)
    * Chairs' decision on HTML WG Issue-30 (longdesc)
          o cover letter for Chairs' decision on HTML WG Issue 30 (longdesc)
          o HTML WG Issue-30 (longdesc) 

References:

[1]
http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-programmatically-determined-head

[2] http://www.w3.org/html/wg/tracker/issues/30

[3] http://www.w3.org/TR/REC-html40/struct/objects.html#adef-longdesc-IMG

[4] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10455

[5] http://www.d.umn.edu/~lcarlson/research/ld.html#wild

[6] http://www.d.umn.edu/~lcarlson/research/ld.html#glps

[7] http://www.w3.org/html/wg/wiki/LongdescRetention

[8]
http://lists.w3.org/Archives/Public/public-html/2010Aug/att-0112/issue-30-decision.html

[9] http://lists.w3.org/Archives/Public/public-html/2010Aug/0112.html

[10] http://lists.w3.org/Archives/Public/public-html/2010Aug/0112.html

[11] http://www.w3.org/html/wg/tracker/issues/30


(the logger of this bug thanks laura carlson and steven faulkner for their
contributions to the wiki page on which this bug report is based
http://www.w3.org/WAI/PF/HTML/wiki/Verbose_desc_reqs)

-- 
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, 30 September 2010 13:52:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:19 UTC