Re: Validation in WCAG 2

The Oracle Accessibility Checker, version 3.0 (which is only available 
internally to Oracle until 2005) plans to incorporate valid HTML/XHTML 
checks.

-Kerstin

david poehlman wrote:

>My take,
>
>Tools should not allow for creation of either inaccesable or invalid markup.
>
>My question:
>What if any at require valid markup or are planned to?
>
>Johnnie Apple Seed
>----- Original Message ----- 
>From: "Jesper Tverskov" <jesper.tverskov@mail.tele.dk>
>To: <w3c-wai-ig@w3.org>
>Sent: Wednesday, August 18, 2004 4:56 AM
>Subject: Validation in WCAG 2
>
>
>
>In the proposal for WCAG-2 validation of markup and CSS is now "level
>one success Criteria for Guideline 4.1". In WCAG-1 the issue was listed
>in Checkpoint 3.2 as Priority 2.
>
>Most of us will welcome that there is now more emphasis on the need for
>technologies to validate.
>
>But there are also some problems in the validation-issue. It is easy to
>make the transitional versions of HTML and XHTML validate but not that
>easy if you opt for "strict" or XHTML 1.1.
>
>Making validation a "level one success Criteria" could make is even more
>difficult to get web content authors to shift to the better "strict"
>versions of HTML and XHTML.
>
>Maybe validation should be level one for the transitional versions and
>level two for the strict versions? I would like to hear the opinion of
>other members of this list.
>
>Best regards,
>
>Jesper Tverskov
>www.smackthemouse.com
>
>
>
>
>
>
>  
>

Received on Wednesday, 18 August 2004 17:43:17 UTC