landing-page-accessibility

Native semantic HTML first, automated scanners as a floor, a real manual pass before ship.

The failure this fixes

AI website builders scaffold a page in seconds, but the output is an "accessibility black box": div-soup with no semantic landmarks, silent keyboard traps, DOM/focus order that doesn't match the visual order, hallucinated or generic alt text (alt="image" passes a scanner but fails the requirement), and either missing or over-applied ARIA. The governing correction — verbatim in the W3C ARIA spec — is "No ARIA is better than bad ARIA": pages with ARIA average more errors than pages without, because devs reach for <div role="button"> and never wire up the keyboard, focus, and state that <button> gives for free. And accessibility overlays are a liability, not a fix.

When to use / when NOT to use