W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2005

Re: Well-formed (was: Re: F2F Proposed Resolutions Draft Updates)

From: Ineke van der Maat <inekemaa@xs4all.nl>
Date: Fri, 17 Jun 2005 22:45:41 +0200
Message-ID: <020601c5737d$869e6180$0201a8c0@inekem>
To: <w3c-wai-ig@w3.org>

Hello,

i am very confused about the discussion about valid or well-formed code.

Using xhtml 1.1 served as application/xhtml + xml, I am sometimes 
confrontated  in Firefox with the error message : can not parse  the page 
because line XX character XX is not well formed, when I look sometimes the 
page for a test before validating. And Opera has a different strategy: it 
shows the page till the line where the code is not well formed, shows an 
error message and continues to show the  complete code of the page!  The 
only possibility to prevent this, is indeed validating the page after every 
change.

The same incorrect code served as text/html will be parsed by  IE, Firefox 
and Opera.
 It is a very little worth to validate a page.

I don't dare to think of  that a version of IE will show not-valid xhtml 2.0 
correctly in future... but perhaps the WCAG can help to prevent this by 
requiring valid code  at level 1.

When it is true that incorrect/ not valid code is handled differently by UAs 
( stated in "Beginning XHTML", Wrox Press by eg. Dave Ragget), how can we be 
sure hat content of invalid pages in a website  have always the same order / 
look as related valid pages, independent on UA and platform? Is not this an 
accessibilty issue for people who are learning disabled?


Greetings
Ineke van der Maat
Received on Friday, 17 June 2005 20:45:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:21 GMT