Form fields have stable names

What it is worth

Two numbers rather than one, because a check's weight is inside its pillar and the pillar is a share of the whole. The largest check in the smallest pillar moves your score less than a middling one in the largest, and knowing which you are looking at is the difference between fixing the right thing and fixing the loudest thing.

Why an agent cares

Worth saying plainly: this is not a search-engine ranking factor and passing it will not move you up a results page. It measures something else — whether software with no browser, no JavaScript and a few hundred tokens of budget can tell what your page is and do something with it. Those are the conditions an AI assistant reads you under, and they are much harsher than a browser's.

How to fix it

Give each field a stable, human-readable name that survives your build.

That remediation is the one the scanner itself offers when this check fails, read from the same code that does the scoring rather than written alongside it. If it were typed out separately it could drift from the check that judges it, which is the failure that makes published advice worthless.

How often the web fails this

Measured on 2026-09-06 against AX specification v1.5.1, across a sample of 292 public websites.

The last row is kept out of the percentages deliberately. A check that did not apply to 172 of 292 sites is not a check most of the web passes, and folding those in is the commonest way this sort of table is used to say something untrue.

At 12% this is something most sites already get right, which makes failing it more costly than the point value suggests — you are behind the field rather than level with it.

Testing it on your own site

Copynpx axray-cli your-site.com

All 70 checks against one URL, this one among them, with what was found rather than only whether it passed. Add --min 70 in a pipeline and the command exits non-zero below that score, so a change that breaks what agents can read fails the build instead of shipping.

Questions about this check

What does the "Form fields have stable names" check mean?

It sits in the Actionability pillar of the Agent Experience rubric and is worth 6 points within that pillar, which works out at about 1.5 points of the overall score out of 100.

How do I fix form-names?

Give each field a stable, human-readable name that survives your build. It is an engineering change rather than a setting, so it needs a deploy rather than an edit.

Is it unusual to fail form-names?

No. Of 120 public sites where this check applied, 14 failed it — 12%. The measurement was taken on 2026-09-06 against AX specification v1.5.1, and no site is named.

How do I test form-names on my own site?

Run npx axray-cli your-site.com from a terminal. It runs all 70 checks against one URL and prints this one among them, with what it found rather than only whether it passed. It is free, needs no account and installs nothing.

The rest of the Actionability pillar

Can the agent take the next step - navigate, search, submit, buy - without guessing?

• Navigation uses real links — 12 points
• Link text describes the destination — 8 points
• Links onward into the site — 6 points
• Form fields are labelled — 8 points
• Fields declare autocomplete tokens — 4 points
• Controls are real buttons — 6 points
• Reachable by a human, discoverably — 5 points
• Site search is machine-usable — 4 points
• Declares what an agent can do here — 5 points
• Programmatic surface is discoverable — 6 points