RE: Re : Influence of valid code on screen readers

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.

Mat I understand your point of view but they could exist assistive
technologies or browser (especially in the mobile phone) that they could
have many problems whith an invalid code (also only an erroneus character
encoding) because our errors management is not much powerful. This would
provoke one situation of real inaccessibility.


Luca Mascaro
IWA/HWG Member
W3C HTML and WCAG WG Member

Received on Saturday, 18 June 2005 07:40:59 UTC