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

Page validation (was RE: Testing web page accessibility by phone)

From: John Foliot - bytown internet <foliot@bytowninternet.com>
Date: Wed, 29 May 2002 08:39:25 -0400
To: "Robert B. Yonaitis" <ryonaitis@hisoftware.com>, <w3c-wai-ig@w3.org>, "David Poehlman" <poehlman1@comcast.net>
Message-ID: <GKEFJJEKDDIMBHJOGLENEEGDCHAA.foliot@bytowninternet.com>

This thread has introduced the topic of validation

> -----Original Message-----
> From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org]On
> Behalf Of David Poehlman
> Sent: May 29, 2002 8:03 AM
> To: Jerry Weichbrodt; w3c-wai-ig@w3.org
> Subject: Re: Testing web page accessibility by phone
> interesting point Jerry!
> This harkens back to my point of "vallidation" with which I was putting
> forward the crazy notion that doing it right to begin with makes a huge
> difference.

From http://www.hisoftware.com/access/whatwedow.html

[Checkpoint]  3.2 Create documents that validate to published formal
[Method]      Programmatic
[Explanation] Identify if a page does not use the !DOCTYPE tag and fail or
warn as configured.  This is a visual/programmatic  checkpoint that can be
verified and reported on with the HiSoftware Interview Wizard.

But what happens if the document has a doctype declaration, but the page
does not validate to it?  Is that page deamed accessible or not accessible?
While the US Section 508 does not make this a manditory requirement, in
Canada their accessibilty requirements for Federal Web Sites (part of the
Common Look and Feel standards) requires compliancy to the WCAG Priority 1
and 2 levels to pass muster (AA).

I ask this as a serious question - how important is it to developers out
there to ensure that your pages validate?  Or has Section 508 become the
defacto benchmark and who cares, it has skip nav links and alt tags and it
looks good in IE?


> -----Original Message-----
> From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org]On
> Behalf Of Robert B. Yonaitis
> Sent: May 29, 2002 7:34 AM
> To: 'phoenixl'; poehlman1@comcast.net; w3c-wai-ig@w3.org
> Subject: RE: Testing web page accessibility by phone

> By Design you can determine if the page is putting forward the
> information accessible to all clients in standard or alternative
> methods. (I Believe this is what David is talking about) Much of the
> questions are related to individuals and using a focus group or team
> approach to QA/Development for Accessibility or usability is
> recommended. Note: HiSoftware does that and does it well.
> Additionally we have comprehensive 508 and W3C and WCAG validation:
> 508 coverage http://www.hisoftware.com/access/whatwedo.html
> WCAG 1.0 coverage http://www.hisoftware.com/access/whatwedow.html

> -----Original Message-----
> From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On
> Behalf Of phoenixl
> Sent: Tuesday, May 28, 2002 8:14 PM
> To: phoenixl@sonic.net; poehlman1@comcast.net; w3c-wai-ig@w3.org
> Subject: Re: Testing web page accessibility by phone
> Hi,
> The issue of "getting it right" is an interesting one, but it is not
> clear exactly what it means since various people and organizations have
> different interpretations.
Received on Wednesday, 29 May 2002 08:40:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:19 UTC