From 650c1b9646d6f31ec5908b190b8c94a2f823b12d Mon Sep 17 00:00:00 2001
From: Rohan Kumar <seirdy@seirdy.one>
Date: Mon, 1 Aug 2022 20:51:56 -0700
Subject: [PATCH] Update tools I use

---
 content/about/uses.md       | 25 +++++++++++++++++++------
 content/meta/site-design.md |  4 +++-
 2 files changed, 22 insertions(+), 7 deletions(-)

diff --git a/content/about/uses.md b/content/about/uses.md
index 21af58a..efe10ed 100644
--- a/content/about/uses.md
+++ b/content/about/uses.md
@@ -8,7 +8,8 @@ date: "2022-06-16T17:16:18-07:00"
 ---
 Here's the software I use. I've recently started to reduce my use of <abbr title="Textual User Interfaces">TUIs</abbr> in favor of <abbr title="Command Line Interfaces">CLIs</abbr> for a variety of reasons. When possible, I try to use lightweight programs that can run on any machine, from a single-board computer to a giant desktop. I don't ever want to feel like I need to upgrade my hardware to do the same tasks as before: hardware upgrades should only be justified by my use-cases significantly changing, existing hardware being broken beyond repair, or upstream abandonment of security patches.[^1]
 
-## Hardware
+Hardware
+--------
 
 My main computer is a 2013 HP Elitebook 840 G1. It has an Intel i5-4300U CPU, with simultaneous multithreading disabled.
 
@@ -201,19 +202,31 @@ I run these tools locally, on every applicable file. A full run takes under <tim
 [IBM Equal Access accessibility-checker](https://github.com/IBMa/equal-access/blob/master/accessibility-checker/README.md)
 : I use this just like axe-core: as a CLI utility to check every page on my sitemap for basic accessibility violations. I disable "potential-violations" checks because those have false-positives.
 
-jq:
-: I use jq to ensure that all my JSON is valid. This includes my Web App Manifest file and Webfinger JSON.
+jq
+: I use jq to ensure that all my JSON is valid. This includes my Web App Manifest file and Webfinger JSON. I also use jq to filter out false positives from the Nu HTML Checker.
+
+[Feed Validator](https://github.com/w3c/feedvalidator)
+: I validate my Atom feeds using this tool. Like always, I filter out false positives and report them upstream.
+
+[htmltest](https://github.com/wjdp/htmltest) OR [html-proofer](https://github.com/gjtorikian/html-proofer)
+: Two very similar tools. html-proofer is slow but supports more features; I run the faster htmltest more often. They check for broken links, markup errors, and valid icons.
+
+[webhint](https://webhint.io)
+: When all the aforementioned tests pass, my staging site deploys and webhint runs on every page in its sitemap. I skip its axe-based tests, since those are already covered by axe-core.
+
+  Webhint checks HTTP headers, validates the Web App Manifest, ensures caching and compression work, checks for compatibility issues, validates compliance with a performance budget, and looks for common HTML/CSS mistakes.
 
 Tools I have yet to add to this section:
 
-* Something to validate my Web App Manifest and Webfinger JSON against a schema
-* Validation for my Atom feeds
-* Broken internal link checkers
+* Something to validate my Webfinger JSON against a schema
+* A tool to validate microdata and RDFa. structured-data-linter or Schemarama could work.
+* A tool to validate microformats.
 
 ### Server-side stuff
 
 All my server daemons are statically-linked binaries, which makes sandboxing easier.
 
+
 Nginx
 : Specifically, [nginx-quic.](https://quic.nginx.org/) with the [headers_more](https://github.com/openresty/headers-more-nginx-module) and [ngx_brotli](https://github.com/google/ngx_brotli) modules. Statically linked against zlib-ng, BoringSSL, and musl libc; patched for dynamic TLS records, basic OCSP support, and HPACK compression.
 
diff --git a/content/meta/site-design.md b/content/meta/site-design.md
index bd31512..587e192 100644
--- a/content/meta/site-design.md
+++ b/content/meta/site-design.md
@@ -42,10 +42,11 @@ I also go further than WCAG in many aspects:
 
 - I ensure at least one such 56-by-56&nbsp;px non-interactive region exists on the page, for users with hand tremors or or anyone who wants to tap the screen without clicking something.
 
-- With the exception of in-text borders, I only set custom colors in response to the `prefers-color-scheme: dark` media query. These custom colors pass APCA contrast ratios, all being close to the ideal lightness contrast of 90. They are also autism- and overstimulation-friendly colors: yellow links are significantly de-saturated to reduce harshness.
+- With the exception of in-text borders, I only set custom colors in response to the `prefers-color-scheme: dark` media query. These custom colors pass APCA contrast ratios, all being close to the ideal lightness contrast of 90. They are also autism- and overstimulation-friendly colors: the yellow links are significantly de-saturated to reduce harshness.
 
 - I ensure that the page works on extremely narrow viewports without triggering two-dimensional scaling. It should work at widths well below 200 CSS pixels.
 
+
 ### Assessment and evaluation
 
 I test each WCAG success criterion myself using the mainstream browser engines (Blink, Gecko, WebKit). I test using multiple screen readers: Orca (primary, with Firefox and Epiphany), NVDA (with Firefox and Chromium), Windows Narrator (with Microsoft Edge), Apple VoiceOver (with desktop and mobile Safari), and Android TalkBack (with Chromium).
@@ -60,6 +61,7 @@ Finally, I supplement manual testing with the following automated tools:
 - [WAVE Web Accessibility Evaluation Tool](https://wave.webaim.org/)
 - [ARC Toolkit](https://www.tpgi.com/arc-platform/arc-toolkit/)
 - [webhint](https://webhint.io/)
+- [lighthouse](https://developer.chrome.com/docs/lighthouse/overview/)
 
 WAVE reports no errors; AXE is unable to determine certain contrast errors, but it otherwise reports no errors; IBM Equal Access reports no errors but some items that need review.