W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2013

Re: HTML Validation Tools

From: Karl Groves <karl@karlgroves.com>
Date: Wed, 17 Jul 2013 07:26:32 -0400
Message-ID: <CABScKPCxtgHboprDV1OpuAnXVFBgcjsw20CoKM7tx6PHo0Y_CQ@mail.gmail.com>
To: "Homme, James" <james.homme@highmark.com>
Cc: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
As Mitch noted, the W3C validator would work for you, as you can enter
source directly.
You're right to note that you should be testing the final rendered page,
not the document source file.  All major browsers have the ability to get
that information for you. One of the easiest ways is using Firebug on
Firefox and right-clicking on the <html> element node. Then, select "Copy
HTML". You can then paste that into the validator.

Even easier, use this addon for Firebug:

On Wed, Jul 17, 2013 at 7:02 AM, Homme, James <james.homme@highmark.com>wrote:

>  Hi,
> I interpret guideline 4.1.1 as requiring clean HTML. Does anyone know of a
> validation tool that we can use that does not link out to the Internet to
> do its checking? Related to this, I would think that the tool would need to
> examine the HTML after it gets rendered in the browser, because many pages
> are likely to have some of their HTML generated by scripts.
> Thanks.
> Jim
> ------------------------------
> This e-mail and any attachments to it are confidential and are intended
> solely for use of the individual or entity to whom they are addressed. If
> you have received this e-mail in error, please notify the sender
> immediately and then delete it. If you are not the intended recipient, you
> must not keep, use, disclose, copy or distribute this e-mail without the
> author's prior permission. The views expressed in this e-mail message do
> not necessarily represent the views of Highmark, its diversified business,
> or affiliates.


Karl Groves
Phone: +1 410.541.6829
Received on Wednesday, 17 July 2013 11:26:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:45 UTC