W3C home > Mailing lists > Public > www-validator@w3.org > March 2017

Re: Nu Html Checker

From: Michael[tm] Smith <mike@w3.org>
Date: Fri, 17 Mar 2017 15:53:15 +0900
To: Fuqiao Xue <xfq.free@gmail.com>
Cc: mikesabbia@yahoo.com, "www-validator@w3.org" <www-validator@w3.org>
Message-ID: <20170317065315.sgksfoy6xkcvauxk@sideshowbarker.net>
Fuqiao Xue <xfq.free@gmail.com>, 2017-03-17 08:18 +0800:
> Archived-At: <http://www.w3.org/mid/CAAF+z6FqFk1Q=jPS2TWLbtrtpT+vkPBMp3bbDzC6qhGMG=0i2A@mail.gmail.com>
> 
> On Thu, Mar 16, 2017 at 9:16 PM, Michael[tm] Smith <mike@w3.org> wrote:
> >
> > The HTML checker does not attempt to explicitly do any WCAG checks at all.
> > It only implements checks for requirements in the HTML spec.
> 
> I did not test it, but there's a bookmarklet about WCAG 2.0 checking
> in this page: https://checker.html5.org/about.html

True, I hadn’t meant to neglect the availability of that. Thanks for
pointing it out.

So, what that actually does is, after you use the HTML checker to check a
document and the checker shows you the results, the bookmarklet filters out
any errors or warnings about HTML conformance issues that don’t also happen
to correspond to whatever HTML requirements are restated in the WCAG spec.

That is, it just shows you any error or warnings that do correspond to
whatever HTML requirements are restated in the WCAG spec.

So to be clear, that bookmarklet is also not doing any WCAG-specific
checking—instead it’s just showing you any HTML conformance issues your
document has that also happen to be issues that the WCAG spec identifies as
accessibility issues.

  —Mike

-- 
Michael[tm] Smith https://sideshowbarker.net/

Received on Friday, 17 March 2017 06:53:44 UTC

This archive was generated by hypermail 2.3.1 : Friday, 17 March 2017 06:53:48 UTC