Why it matters
Skipping from h2 to h4 breaks the document outline that assistive technology exposes.
How to fix it
Use heading levels in order; style with CSS rather than picking levels by size.
References
More accessibility rules
void a11y reports 48 rules in this category. WCAG 2.2 AA through axe-core, plus checks axe can't do alone: visible keyboard focus, 24/44px target size on mobile, 320px reflow and disabled zoom.
landmark-one-mainPage has no <main> landmarkregionContent is outside landmark regionslandmark-uniqueLandmarks are not uniquely identifiablepage-has-heading-onePage has no level-one headingempty-headingHeading is emptylistList contains invalid childrenlistitem<li> is not inside a listaria-allowed-attrARIA attribute is not allowed on this role