Static heading sequence skips a level
ShipReady found a later static heading whose level is more than one higher than the preceding heading level.
Why it matters
A coherent heading sequence can make the static document outline easier to review and navigate.
How ShipReady detects it
What it inspects
On a successful, untruncated HTTP 200 page, ShipReady reads static h1 through h6 elements in source order after excluding comments and script, style, template, and noscript regions.
What triggers a finding
The rule triggers at the first heading whose level is more than one higher than the previous observed heading. Equal levels and decreases do not trigger it.
What the evidence shows
The scanner observed a static source-order heading-level increase greater than one and records the first jump.
Limits of this check
ShipReady does not execute client-side code, evaluate a rendered outline, determine author intent, or perform a complete accessibility or WCAG audit.
How to fix it
Review the source-order heading outline
Use heading levels for document structure and use styling rather than a higher heading level solely to change visual size.
How to verify the change
Inspect deployed heading order
Review the served page's source order and test representative heading navigation.
Expected: Heading-level increases follow the intended document structure without a jump greater than one.