Nick Schonning

The browser will autoclose a lot of broken HTML if you're using the "Inspect" part of the brower tools, it shows you it's corrected dome. You'd need to look at...

Probably not straightforward, or something I could likely contribute to, but the current ini-style config reminded me of the way EditorConfig has the ini-style selectors for overrides https://editorconfig.org/#example-file https://editorconfig.org/#file-format-details. A...

@mcking65 that was what I was trying to describe, maybe a sample would make it better to understand. The sample from the current aria-practives .vnurc: ```ini # This is a...

Yeah, I prefer the in-place VNU scanning, because I can click on the "URL"/path directly to go to the line in VS code 😉

> An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images. This cleanup will probably take a lot...

And with a problem matcher running on the non-complied code, it can comment inline on the issues by registering a problem matcher like https://github.com/w3c/aria-practices/blob/master/.github/workflows/vnu-jar-problem-matcher.json

`Non-space characters found without seeing a doctype first. Expected “”.` is actually working, just double checked an my suppression was missing the end of the statement. Other 2 aren't though

Just tried with `Element “head” .* “title”.` and it suppressed, but I didn't see any funny characters in https://github.com/validator/validator/blob/master/src/nu/validator/messages/MessageEmitterAdapter.java#L365

OK, so `Element “head” is missing .*“title”.` seems to be the minimal wildcard to allow it to pass, anything beyond and it seems to stop filtering again

If you do go down the route of a bigger error suppression refactor, I'd vote for error (and warning) codes/names a-la pylint/eslint/markdownlint. I think there is already an issue somewhere...