The fix, in one snippet
<label for="email">Email</label><input id="email" name="email">Illustrative values. Change the paths, hostnames and options to match your own site before using it.
The sections below explain what is tested, why it matters and the alternatives.
What we test
Scan.now performs deterministic HTML checks for document language, image alt attributes, programmatic form-control and button names, and heading order. This is a useful baseline, not a WCAG conformance claim.
Why it matters
These semantics are how screen readers and other assistive technology identify content and controls.
How to fix it
Use native elements, associate every control with a visible label, provide meaningful alternatives, declare the document language and keep headings hierarchical.
Where this fits
Structural accessibility basics is check 10 of 19 that the website accessibility scanner runs under page content and javascript, ordered the way they are worth fixing. That ordering is the point: Fixing this one while the check above it still fails buys less than it looks like.
Fix this one first
Above it in the same category sits POST form without recognisable CSRF protection (medium), where a POST form has no recognisable anti-CSRF field. An attacker who has that does not need this, so it is the better use of the same hour.
What fixing this still leaves open
Structural accessibility basics closes one route in. Immediately below it: Web performance baseline, where the initial response is slow, oversized or contains many parser-blocking scripts; Advertising and tracking endpoints, where which of the page's third-party hosts exist to advertise to the visitor or to follow them, matched against the EasyList and EasyPrivacy blocklists that also power our <a href="/ad-blocker">ad blocker</a>; CMS / generator version disclosure, where the page announces the CMS or static-site generator it was built with, usually including the version, in a meta tag, header or comment banner.
Found in the same scan
The website accessibility scanner reports this alongside checks from other categories that are at least as serious, including Path traversal / local file inclusion, where a path-like parameter returned a known local operating-system file signature, and Session token exposed in URL, where a session-like token name appears in a discovered URL. A single run of website accessibility scanner answers all of them at once.
The first few lines
You are a senior web engineer. I ran a security and SEO scanner against my site and it reported the finding below. Fix it properly rather than suppressing the symptom.
Finding: Structural accessibility basics (medium severity)
Scanner check id: accessibility-basicsThe rest of this prompt names the pages and line numbers we found the problem on, the configuration to change, and the constraints a good answer has to respect. It is free, it just needs an account so the work is not scraped wholesale.
Sign in with GoogleSigning in is free and takes one click. We store your email address and nothing else.
