Rules

Every rule of the accessibility audit, and every security header check, structured-data feature and checked JavaScript library, has a page here: what it checks, how it is tested and, where the detection corpus has one, a failing and a passing example. The pages are generated from the rule catalogue and the rule contracts, so they cannot drift from what the tool does.

Coverage

Automatic

An automated check that can report a confirmed violation.

Hint only

An automated check that by design reports review hints only: its findings are marked for manual review, never as confirmed violations.

Manual

A tool cannot decide this check. The audit only points a person at it; it is never counted as automatically verified.

The class is declared by the rule's contract (automation andreview_only), not by what the corpus happens to show. A security page can stand for several header checks that surface as one finding.

Addresses

A rule's page is rules/<rule_id>/ below this site, with the id unchanged:/ stays a path separator, so document/title-missing is atrules/document/title-missing/. The help_url of a finding in the JSON, SARIF and AI report points here, using the id the finding carries: security.headers.missing_header andbest_practices.vulnerable_libraries.jquery for the other families; structured-data findings (seo.schema.schema_rule_missing_<feature>_<property>) point at their feature's page, seo.schema.schema_rule_missing_<feature>. A WCAG criterion's W3C Understanding page is understanding_url.

All rules