Learn / For your team
Agent readiness for developers
Agent readiness is largely progressive enhancement and structured data rather than a new discipline: facts present in the served response, actions expressible as forms, and controls that work without a pointer. Most of it overlaps with accessibility work, which means the same changes settle two obligations and can be guarded by the same tests.
Agent readiness is mostly progressive enhancement and structured data. There is no new framework and no specification to implement for a typical store, which makes it unusually cheap and unusually easy to deprioritise.
The requirements, concretely
- Facts in the served response. Price, availability, variant options and terms present before any script runs. Emitting structured data server side is enough; full server rendering is one way to get there, not a requirement.
- Actions as forms. Add to cart as a real form with a method, an action and named inputs, with your existing script intercepting the submit.
- Controls without a pointer. Variant selection through real form controls, operable by keyboard, with options in the markup rather than attached on load.
- A checkout that survives a cold session. No account requirement, no overlay in the path, no state kept client side across a redirect.
The accessibility overlap
An agent and a keyboard user need almost the same things, which is worth raising when this competes for priority: it is not a new obligation, it is an existing one with a second payer.
See how to make variant pickers agent accessible.
The in-app browser case
Assistant referred purchases land in an embedded browser: no cookies, restricted storage, different redirect handling. Any flow that stashes state client side across a redirect is the thing most likely to break, and it fails as an error rather than as an obstacle.
See how to test checkout in an in-app browser.
Guard it with a test
Fetch a product page without executing scripts and assert that price, availability and variant options are present. That single test catches most regressions, and it belongs in the pipeline rather than in a checklist.
Questions
Is this just accessibility work?
A large part of it is, and that overlap is the most useful thing to know. Real form controls, keyboard operability and options present in the markup serve both, so one change satisfies two requirements.
Do we have to server render everything?
No. The facts have to be in the served response. Server rendering the product page is one way; emitting structured data server side alongside a client rendered view is another and is often less disruptive.
How do we stop it regressing?
Assert it. A test that fetches a product page without executing scripts and checks for price, availability and variant options catches nearly everything, and runs in seconds.