R: Starter comments on WCAG 2.0 draft

Matt, is you the same Matt May of here?
http://www.idealliance.org/papers/dx_xml03/papers/06-03-02/06-03-02.html#s5.
2

5.2. 2. Generate standard markup. 
Valid, standardized markup is crucial to accessibility. Given that a wide
range of assistive technologies use Web content, from screen readers and
magnifiers to Braille displays to customized browsers for users with
learning disabilities, all users benefit from an understanding of the
semantics provided by languages like HTML. Valid content additionally
facilitates cross-platform and cross-browser compatibility, since most
modern browsers agree on how to render valid content. 

Authoring tools must by default create content that validates to published
grammars. If the final output turns out to be invalid, for example if the
author's portion of the template is invalid, tools are encouraged to
evaluate and inform the author of the problem. 



-----Messaggio originale-----
Da: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] Per conto
di Matt May
Inviato: luned́ 25 luglio 2005 21.46
A: Roberto Scano (IWA/HWG)
Cc: jan.richards@utoronto.ca; w3c-wai-au@w3.org
Oggetto: Re: Starter comments on WCAG 2.0 draft



Roberto Scano (IWA/HWG) wrote:

>If an authoring tool generates xhtml and it's no valid, when served as 
>application/xhtml+xml some browsers end the page execution: this means no
accessibility for all.
>  
>
Which is why validity doesn't need to be in the WCAG spec to satisfy 
XHTML. In XHTML, being valid (or at least well-formed) is an 
architectural constraint: you can't fail to do it and still be usable in 
any form. It's as useless to require it in WCAG as it is to require in a 
building accessibility document that front doors aren't built 20 feet 
off the ground.

That said, it's well in scope for ATAG 2, since it's the only way we 
know that the final output will be rendered no matter how the server is 
configured.

-
m

Received on Tuesday, 26 July 2005 10:42:52 UTC