Accessible Forms Are More Automatable Forms

Associate a visible label with every input, select, and textarea. Use the appropriate input type and autocomplete purpose when relevant. A placeholder may illustrate format but should not be the only label because it disappears and may not provide a stable accessible name. Group related choices with fieldset and legend. Mark required state in text and programmatically, and explain why sensitive information is needed before collection. [AR3][AR11]

Inspect the computed name and description in browser accessibility tools. Repeated edit or remove controls need context that identifies the target. Avoid labeling by screen position. If a form changes dynamically, keep IDs and label relationships stable for the life of the control. These same relationships give browser tests resilient role-and-name selectors without special agent markup. [AR3][AR4]

Put format, range, and password requirements beside the field before submission. Use examples that cannot be mistaken for real personal data. Do not require users to discover a rule one error at a time. Client-side hints can improve the experience, but the server must validate the same constraints and reject untrusted input. Keep valid entries when another field fails so recovery does not require starting over. [AR3][AR7][AR11]

For asynchronous checks, expose busy and final state without firing announcements on every keystroke. Offer a clear timeout or retry path. If a field is optional, do not imply otherwise through styling. If the product cannot accept a valid real-world name, address, or other value, revisit the data model rather than adding a vague error message. [AR3][AR4]

An error should identify the field, name the failed constraint, and offer a repair. Associate it with the field and expose invalid state. A summary at the top can list all failures and link to them, while each field keeps its local message. Move focus or announce the summary deliberately after submission. Avoid dumping focus on the first field without explaining what happened. [AR3][AR4]

Test empty, malformed, boundary, duplicate, expired, and server-failure paths with synthetic data. Confirm that focus remains visible, valid fields retain values, messages persist long enough to read, and a corrected field clears stale state. Capture the exact failure in browser traces so a repair targets the real problem rather than adding arbitrary waits. [AR3][AR7]

Classify the submit effect. Search and preview are usually read-only. Sending, publishing, purchasing, changing permissions, and deleting create external consequence. For higher-consequence flows, show a review step with the exact target, key values, price or visibility, and action label. Require intentional approval and validate authorization on the server. Prevent duplicate submission with idempotency or equivalent controls. [AR7][AR8]

A browser-agent test should stop at review unless the environment is explicitly isolated for the consequence. Add a negative fixture containing an instruction to skip confirmation or change scope. The successful outcome is refusal. Do not trust attributes or page text as permission. Keep untrusted content separate from product policy and never log secret or sensitive field values merely to explain agent behavior. [AR7][AR8]

After a successful safe action, show what happened, current status, time, reference, and next step. A transient toast alone is easy to miss. On failure, distinguish retryable from final outcomes and avoid implying that an uncertain request failed when it may still be processing. Expose a way to check status before repeating a consequential action. [AR3][AR7]

Automate the state machine: initial, partially complete, invalid, correcting, busy, review, canceled, successful, and failed. Assert labels, states, focus, network count, and receipt. Then perform a keyboard pass and a screen-reader spot check. AgentReady's free URL scan can flag form-label and automation signals, but it cannot prove server authorization or every validation state; keep those tests in the repository. [AR3][AR4][AR7]