From 1823cb57b7ac592159bde64a25cb06e3606bb735 Mon Sep 17 00:00:00 2001 From: Rohan Kumar Date: Fri, 3 May 2024 15:07:13 -0400 Subject: [PATCH] Update my usage of the Nu HTML Checker Emphasize how I use the latest commit of the CSS validatro --- content/about/uses.md | 2 +- content/meta/badges.md | 1 - content/meta/site-design.md | 6 +++--- content/meta/wcag-conformance.md | 2 +- linter-configs/vnu_filter.jq | 1 + 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/about/uses.md b/content/about/uses.md index ebd688c..4181bb4 100644 --- a/content/about/uses.md +++ b/content/about/uses.md @@ -244,7 +244,7 @@ I run these tools locally, on every applicable file. A full run takes under }} {{}} {{}} -{{}} {{}} {{}} {{}} diff --git a/content/meta/site-design.md b/content/meta/site-design.md index a3dca2a..d19efd9 100644 --- a/content/meta/site-design.md +++ b/content/meta/site-design.md @@ -35,7 +35,7 @@ I conform to all WCAG AAA success criteria (SC) _excep SC 3.1.6 Pronunciation : I do not currently offer any pronunciation information. -I have only tested WCAG compliance in mainstream browser engines (Blink, Gecko, WebKit). For full details on how I meet every WCAG success criterion, read [Details on WCAG 2.2 conformance]({{}}). +I have only tested WCAG compliance in mainstream browser engines (Blink, Gecko, WebKit). For full details on how I meet every WCAG success criterion, read [Details on WCAG 2.2 conformance]({{}}). The WCAG presents a starting point, not a stopping point. Here are some non-WCAG accessibility criteria I consider: @@ -71,7 +71,7 @@ The following automated tools supplement manual testing: WAVE reports no errors. AXE sometimes fails to measure contrast, but otherwise reports no errors. IBM Equal Access reports no errors, and finds some items which need manual review. -I run axe-core, the IBM Equal Access Accessibility Checker, the Nu HTML Checker (local build, latest commit), and webhint on every page in my sitemap. After filtering out false-positives (and reporting them upstream), I receive no errors. I repeat this run with every change to my Hugo templates and stylesheets. +I run axe-core, the IBM Equal Access Accessibility Checker, the Nu HTML Checker (local build, latest commit of the validator and its CSS-Validator submodule), and webhint on every page in my sitemap. After filtering out false-positives (and reporting them upstream), I receive no errors. I repeat this run with every change to my Hugo templates and stylesheets. To work around [issue 1008 in IBM Equal Access Checker](https://github.com/IBMa/equal-access/issues/1008), I remove all instances of `content-visibility` from my site's CSS before running `achecker` from the command line. Update: the issue has been resolved @@ -81,7 +81,7 @@ I run axe-core, the IBM Equal Access Accessibility Checker, the Nu HTML Checker This website uses well structured, semantic, [polygot XHTML5](https://www.w3.org/TR/html-polyglot/) (including [WAI-ARIA](https://www.w3.org/WAI/standards-guidelines/aria/) and [DPUB-ARIA](https://www.w3.org/TR/dpub-aria-1.1/) extensions where appropriate), enhanced with CSS for styling. -This website conforms to Web standards. Each build runs `xmllint` to catch syntax errors. Every few commits, I run a local build of [the Nu HTML Checker](https://github.com/validator/validator) and [html proofer](https://github.com/gjtorikian/html-proofer) across all 200-something pages in my sitemap, and see no errors. I do [filter out false Nu positives](https://git.sr.ht/~seirdy/seirdy.one/tree/master/item/linter-configs/vnu_filter.jq), and I [report and fix false-positives](https://github.com/w3c/css-validator/issues?q=author%3ASeirdy) when possible. +This website conforms to Web standards. Each build runs `xmllint` to catch syntax errors. Every few commits, I run a local build of [the Nu HTML Checker](https://github.com/validator/validator) and [html proofer](https://github.com/gjtorikian/html-proofer) across all 200-something pages in my sitemap, and see no errors. I do [filter out false Nu positives](https://git.sr.ht/~seirdy/seirdy.one/tree/master/item/linter-configs/vnu_filter.jq), and I [report and fix false-positives](https://github.com/w3c/css-validator/issues?q=author%3ASeirdy) when possible. See [my docs for building and validating this site]({{}}) for more information. ### Cross-browser compatibility diff --git a/content/meta/wcag-conformance.md b/content/meta/wcag-conformance.md index 5707c2e..cb5c08f 100644 --- a/content/meta/wcag-conformance.md +++ b/content/meta/wcag-conformance.md @@ -292,7 +292,7 @@ Principle 4: Robust [SC 4.1.1: Parsing](https://w3c.github.io/wcag/understanding/parsing.html) -: I validate all the required properties using the Nu HTML Checker and `xmllint`. All pages are well-formed polygot (X)HTML5. Every deploy contains a step that runs `xmllint` to ensure that all content is well-formed. +: I validate all the required properties using the Nu HTML Checker and `xmllint`. All pages are well-formed polygot (X)HTML5. Every deploy contains a step that runs `xmllint` to ensure that all content is well-formed. Note that this requirement has been dropped from WCAG 2.2. [SC 4.1.2: Name, Role, Value](https://w3c.github.io/wcag/understanding/name-role-value.html) : I use standard HTML controls, enhanced by fully-compliant WAI-ARIA 1.2 and DPUB-ARIA 1.1. I regularly run the Nu HTML Checker, axe-core, and IBM Equal Access Checker on every page of my site to validate this. diff --git a/linter-configs/vnu_filter.jq b/linter-configs/vnu_filter.jq index a3dbee2..8d7aaa0 100644 --- a/linter-configs/vnu_filter.jq +++ b/linter-configs/vnu_filter.jq @@ -1,6 +1,7 @@ # I regularly validate every page with the Nu HTML Checker. # It has false positives; I report them upstream and silence them here. # I use jq/jaq to remove them from the JSON output. +# Use the latest commit of Nu and its css-validator submodule for best results. .messages |= map( . | select( .type == "info" and (