[Bug 10017] New: longdesc and @aria-describedby (ARIA)

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10017

           Summary: longdesc and @aria-describedby (ARIA)
           Product: HTML WG
           Version: unspecified
          Platform: Macintosh
        OS/Version: Mac System 9.x
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: xn--mlform-iua@xn--mlform-iua.no
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org


How does longdesc and @aria-describedby work together?

What should happen when/if both are used on the same <img>? Solving this
problem will tell authors whether it is useful to use both, or always just a
waste of time/space,  sometimes useful etc.

Example:

<img 
   aria-describedby=samepage-fragment  
  longdesc=#samepage-fragment 
  src=foo alt="Foo. Bar.">

What if aria-describedby contains a IDREF _list_? Should that impact how one
uses @longdesc? 

Example:

<img 
   aria-describedby=samepage-fragment-1  samepage-fragment-2
samepage-fragment-3
  longdesc=#samepage-fragment-1
  src=foo alt="Foo. Bar.">

Are there cases when it is useful to _both_ point to long description on the
same page (via aria-describedby) _and_ to a long description on another page?
Or should this cause a warning, for some reason?

Example:

<img 
   aria-describedby=samepage-fragment  
  longdesc=other-page 
  src=foo alt="Foo. Bar.">

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 25 June 2010 22:34:49 UTC