WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Nu HTML Checker

for

From: glen walker
Date: Aug 9, 2021 2:22PM

A bookmarklet or other filtering tool for the NU results would be nice but
I'm not sure I'd trust the results. As Steve said, it might not fully
filter, and I'd be worried it filtered too much. But I understand there's
a lot of "noise" in the parsing results. Technically, 4.1.1 only lists
four types of parsing errors, but some of the other parsing errors can
point out accessibility issues. For example, parsing can find IDs that
don't exist such as an aria-labelledby pointing to an ID that is misspelled
or incorrectly pointing to the NAME attribute. Those aren't technical WCAG
4.1.1 errors but they are accessibility issues that would hopefully be
caught when you're looking for 4.1.2 issues. A 4.1.1 filtering bookmarklet
might filter those results out since they're not one of the four mentioned
in the SC but I wouldn't want those filtered out.

I find that a manual inspection of the results works best (for me). I use
the "message filtering" option of the NU results which helps to group items
together and makes it much easier to go through.

But I'm digressing from the original question about NG attributes and agree
with Steve that they can be ignored.