People love the flashy parts of accessibility tooling, but some of the most useful checks are the ones that sound ordinary: headings, metadata, language, alt text, and broken links. Those things are not side quests. They shape whether the page is understandable, navigable, and actually maintained properly.
In A11Y Cat these checks are not buried in one giant results pile. The headings flow, link checks, and metadata checks have their own logic and output, because they answer different questions. The headings tab, for example, is about document structure, order, skipped levels, empty headings, ARIA heading use, and whether the outline tells a coherent story.
The metadata side is similarly practical. It looks at things like title quality, H1 alignment, canonical mismatches, social preview basics, missing document signals, and other clues that tell you whether the page is just technically present or actually published with care.
That part of the build came from doing real front-end work. These are exactly the details teams forget until they become a mess.
Documentation trail
README.mdCOMMAND_REFERENCE.mdTECHNICAL_GUIDE.md
