Where: index.html's Methodology section (id="methodology", around line 1929).
The gap: the section has one <h2 id="methodology-heading">The pipeline</h2>, then jumps straight to five <h4> elements for the pipeline steps (Load Dataset, Train Biased Model, Measure Fairness Gap, Remove Attributes + Proxies, Retrain & Re-measure) - no <h3> anywhere in between.
Repro:
grep -n "<h[234]" index.html
in this section shows <h2> immediately followed by five consecutive <h4>s.
Why it matters: skipping a heading level (h2 straight to h4) violates WCAG 1.3.1's guidance against skipped heading levels - screen-reader users navigating by heading level lose the section's actual hierarchy, and the h4 steps read as more deeply nested than they structurally are.
Suggested fix: change the five step headings from <h4> to <h3> so the hierarchy is contiguous (h2 section title → h3 step titles), or insert an intermediate <h3> wrapping heading if the steps are meant to nest under a subsection.
Where:
index.html's Methodology section (id="methodology", around line 1929).The gap: the section has one
<h2 id="methodology-heading">The pipeline</h2>, then jumps straight to five<h4>elements for the pipeline steps (Load Dataset, Train Biased Model, Measure Fairness Gap, Remove Attributes + Proxies, Retrain & Re-measure) - no<h3>anywhere in between.Repro:
in this section shows
<h2>immediately followed by five consecutive<h4>s.Why it matters: skipping a heading level (h2 straight to h4) violates WCAG 1.3.1's guidance against skipped heading levels - screen-reader users navigating by heading level lose the section's actual hierarchy, and the h4 steps read as more deeply nested than they structurally are.
Suggested fix: change the five step headings from
<h4>to<h3>so the hierarchy is contiguous (h2 section title → h3 step titles), or insert an intermediate<h3>wrapping heading if the steps are meant to nest under a subsection.