WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Nu HTML Checker

for

From: Steve Green
Date: Aug 9, 2021 1:56AM

The short answer is yes, you can ignore those validation errors. The long answer is...

WCAG2.1 SC 4.1.1 only requires you to report certain types of validation error. You should use a bookmarklet to filter the results so you only see the relevant ones. But which bookmarklet should you use?

Some of my team use https://github.com/stevefaulkner/wcagparsing. However, I recently reported an issue whereby I believe it is not filtering out all the validation errors I think it should.

Personally, I use https://dotjay.github.io/wcag-parsing-filter/bookmarklet/. This is based on Steve Faulkner's bookmarklet, but it filters out the validation errors mentioned above.

That said, I raised a couple of queries with regard to the latter more than a year ago, whereby I believe some results are filtered out incorrectly and some are not filtered out when they should be. I have not yet had an answer. Those queries would also apply to Steve Faulkner's bookmarklet.

The bottom line is that there is not a definitively correct filtering algorithm (that I am aware of). Furthermore, all such bookmarklets are fragile because they work by detecting specific strings in the validator's output. If the developers of the validator change even one character in a string, the bookmarklets will stop working correctly to some degree. Worse still, they will fail silently.

Steve Green
Managing Director
Test Partners Ltd


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Michael H
Sent: 09 August 2021 05:01
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [WebAIM] Nu HTML Checker

Hello,

As part of an accessibility audit, I am tasked with correcting feedback from the Nu HTML Checker:

https://validator.w3.org/nu/

The site that I am checking is an Angular-powered single page application.

Almost all of the errors I'm getting look like:

*Error*: Attribute _ngcontent-hdu-c107 not allowed on element span <https://html.spec.whatwg.org/multipage/#the-span-element> at this point.

It's barking about Angular's automatic attribute generation naming conventions. *Is this something that is safe for me to ignore?*

Has anyone else here run into this issue? If so, how did you solve it?

Many thanks!