Re: Re : Influence of valid code on screen readers

Sorry Matt but when wysiwyg producers, also for web standards group support, are moving to product editors that permit generation of conform code, at now we said: guys, you can prepare your tag soup everyday!
It's years that we are asking for support web standards, i've asked in different AC meetings and Tim Berners-Lee said: ask to the member to respect w3c reccomandation!
So as developer and ac rep of IWA/HWG i'm asking again to think and evalutate the resl impact of wcag 2.0 that will become a reference for 2006-2007 (xhtml 2.0 era...)

----- Messaggio originale -----
    Da: "Matt May"<mcmay@w3.org>
    Inviato: 17/06/05 22.28.16
    A: "Roberto Castaldo"<r.castaldo@iol.it>
    Cc: "w3c-wai-gl@w3.org"<w3c-wai-gl@w3.org>
    Oggetto: Re: Re : Influence of valid code on screen readers
    
    
    Roberto Castaldo wrote:
    
    >Matt:
    >We're not in a position to say what is and is not "allowed". The WCAG WG is
    >not the Web police.
    >
    >Roberto C:
    >I think we are in such position: the whole web community interested in web
    >accessibility is strongly waiting for WCAG 2.0, and requests some guidelines
    >that are very near the concept of "web accessibility police"; but we always
    >say that Web should not be not accessible, so WCAG 2.0 will have a deep
    >impact on the whole Web.
    >  
    >
    
    Unless we put a requirement on them that they don't consider logical, or 
    that they consider too much work. In which case, we will have a standard 
    that appeals to Web standards people, and is ignored by everyone else.
    
    >Roberto C:
    >I think that we should avoid to give tag soup any kind of dignity, as it
    >simply is the absence of rules in developing web pages. From Wikipedia: "Tag
    >soup is HTML code, written without regard for the rules of HTML structure
    >and semantic meaning"; that should be enough for any W3C recommendation to
    >not allow this superficial way of approaching web development.
    >  
    >
    
    I'm not defending tag soup. That practice needs to be fixed. I'll spend 
    the next several years of my career pounding that fact into designers' 
    heads. But we should only go so far as to instruct authors to use 
    semantic markup and accessibility-related metadata appropriately at all 
    times. Validity doesn't ensure that, since people can still be using 
    <font> instead of <h1>, etc., and it requires doing a lot more work 
    that's unrelated to accessibility.
    
    Validity is a fragile thing. An unclosed <td> or an unterminated &nbsp 
    buried in a CMS database somewhere doesn't mean an entire site is 
    functionally inaccessible. But it does mean that at least one rendering 
    of it is invalid. Getting people to spend their time making it valid 
    instead of increasing its accessibility is not the solution. I would 
    rather focus authors' energies on techniques that directly increase the 
    accessibility of HTML markup than on a binary indicator that does not.
    
    -
    m
    
    
    

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

Received on Friday, 17 June 2005 21:24:28 UTC