W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2005

RE: [techs] d-link Test 9

From: Roberto Scano (IWA/HWG) <rscano@iwa-italy.org>
Date: Sun, 23 Jan 2005 09:25:21 +0100
To: <gv@trace.wisc.edu>, <chris.ridpath@utoronto.ca>, <w3c-wai-gl@w3.org>
Message-Id: <200501230322156.SM05388@Inbox>

I disagree to use a technique for d link.
The reason is that specific attribute, longdesc, is available since html 4.x.
The longdesc reading is eventually an UA issue: UA must follow reccomaation, and not other reccomandations must close the programming holes of UA.
Jaws, for example, only NOW (2005) has start to support specific data table attributes.


----- Messaggio originale -----
    Da: "Gregg Vanderheiden"<gv@trace.wisc.edu>
    Inviato: 23/01/05 7.07.34
    A: "'Chris Ridpath'"<chris.ridpath@utoronto.ca>, "'WAI WCAG List'"<w3c-wai-gl@w3.org>
    Oggetto: RE: [techs] d-link Test 9
    
    
    If we stick with the Baseline approach we have been discussing, I believe
    D-Link would be a BRIDGE technique with LONGDESC being required.  
     
     
    Gregg
    
     -- ------------------------------ 
    Gregg C Vanderheiden Ph.D. 
    Professor - Ind. Engr. & BioMed Engr.
    Director - Trace R & D Center 
    University of Wisconsin-Madison 
    
    
    -----Original Message-----
    From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
    Of Chris Ridpath
    Sent: Friday, January 21, 2005 9:22 AM
    To: WAI WCAG List
    Subject: [techs] d-link Test 9
    
    
    In our recent straw poll, the group accepted the test for d-link:
    
    test 9 - All IMG elements that have a LONGDESC attribute also have an
    associated 'd-link'.
    http://www.w3.org/WAI/GL/WCAG20/tests/test9.html
    
    However there were several people that voted for killing it and most people
    voted that it be "optional". I thought we should have some discussion on the
    list as a result of the close decision.
    
    The "d-link" was a temporary measure to support image long descriptions
    until there was user agent support for the LONGDESC attribute. We know that
    d-link will eventually be not required so the question is - when?
    
    Is there yet enough user agent support for LONGDESC that we should not
    require d-link? How do we judge when there is enough support for LONGDESC
    that we can dump d-link. Is there something we can do to increase the
    support of LONGDESC so d-link can be quickly removed?
    
    Note that d-link is currently a level 1 requirement because it maps to
    guideline 1.1, Level 1, Success Criteria 2. I believe that it should be a
    level 2 or level 3 requirement.
    
    Comments appreciated.
    
    Cheers,
    Chris
    
    
    
    
    
    

[Messaggio troncato. Toccare Modifica->Segna per il download per recuperare la restante parte.]
Received on Sunday, 23 January 2005 08:25:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:35 GMT