RE: Re-post: Influence of valid code on screen readers

And, i add, remember also that tools cannot themeself check for the Valid code: with js is possible to do DOM injection for add elements/attributes (like some tricks that add target="_blank" to all links with a defined classname in a xhtml 1.0 strict document) and w3c markup validator approve the page code but the code is not valid (it is like aexternal file inclusion).

----- Messaggio originale -----
    Da: "Sailesh Panchang"<spanchang02@yahoo.com>
    Inviato: 14/06/05 15.44.01
    A: "w3c-wai-gl@w3.org"<w3c-wai-gl@w3.org>
    Oggetto: Re-post: Influence of valid code on screen readers
    
    
    This raises an important question for tools that evaluate accessibility. 
    Should only  pages which do not fail validation check be evaluated for accessibility?
    But then few pages  will qualify for automated accessibility evaluation because Bruce notes:
    "... is rare to encounter valid html, and such is not an explicit requirement. <for Sec 508>"
    I remember a recent instance wherein a complex table  was  apparently marked up "correctly" with headers and id and  yet the screen  reader / self voicing browser   was not able to read it as expected. 
    As it turned out, the id values were not unique in the document and the page failed the W3C Validator.
    Therefore I feel it is important that accessibility evaluation should be performed 
    only on documents that are correctly marked up and pass validation.
    Thanks,
    Sailesh Panchang
    Senior Accessibility Engineer
    Deque Systems
    Reston VA
    www.deque.com
    E-mail spanchang02@yahoo.com
    
    
    		
    ---------------------------------
    Discover Yahoo!
     Find restaurants, movies, travel & more fun for the weekend. Check it out!    

[Messaggio troncato. Toccare Modifica->Segna per il download per recuperare la restante parte.]

Received on Tuesday, 14 June 2005 13:50:27 UTC