I have always liked heading structure because it gives a page away almost immediately. You can tell when a page has been thought through and you can tell when it has been assembled without much discipline.
That is why the headings side of A11Y Cat is more than a tiny utility. It pulls together native headings and ARIA headings, shows order, flags empty items, skipped levels, suspicious jumps, and other structural problems, and keeps weaker cases separate from fully deterministic defects.
What I like about that is that it matches how I actually review work. I do not just want a warning that headings exist. I want the outline, the pattern, and the bits that feel wrong the second I look at them.
There is a lot of accessibility work that is really document-quality work in disguise. This feature reminded me of that.
Documentation trail
README.mdCOMMAND_REFERENCE.mdTECHNICAL_GUIDE.md
