Blog
What we are building, what the rules actually say, and the things we refuse to claim. Written for the person who has to do the work, not for a search engine.
LegalThe first contact is rarely a lawsuit. It is a letter that names a handful of failures on named pages, and the useful question it raises is not whether you are compliant but what you can show.
Read the post
ProductReporting a number we cannot stand behind would be worse than reporting nothing at all.
Read the post
StandardsNobody outside the field knows what 1.4.3 means. “Text too light to read” is the same finding, in a sentence you can act on.
Read the post
EngineeringWhere a fix lands changes what it is worth. On WordPress the corrected markup leaves your server; elsewhere it is applied from rules you approved.
Read the post
EvidenceDated scans, approved fixes and verified re-checks are the part that answers a question months later.
Read the post
StandardsAutomated testing cannot tell you whether alt text is accurate or an error message is genuinely helpful. That is why the 16 checks are listed separately.
Read the post
Getting startedConnect, scan, read the list. Most owners have never seen their own failures written down.
Read the post
LegalA list sorted by severity is an inventory. A list sorted by what actually draws complaints is a plan.
Read the post
EngineeringA tool that rewrites your layout is a tool that will eventually break it. The constraint is the safety feature.
Read the postFive pages, every problem ranked by risk, in plain English — before a lawsuit-hunting scan finds them first.