Choose a complete user journey
Choose a path through input, submission, error correction and result confirmation. A clickable button does not establish completion of the screen’s purpose. Record the browser and device and require every necessary operation from the agreed behavior. This turns a visual inspection into a repeatable interaction check.
Verify keyboard movement and exit
Navigate without a pointer and verify that the current focus is understandable. Open and leave dialogs and menus and return to the task. An intentional modal focus boundary differs from an inescapable trap. Check the complete interaction rather than concluding that a component is accessible because it receives focus once.
Inspect names and states
Inspect the control name and any state changes exposed to assistive technology. An icon-only action needs a meaningful purpose, and expandable or selected controls need their state checked. Visible text does not by itself establish a correct programmatic relationship, so inspect actual output instead of relying on appearance.
Test recovery from invalid input
Deliberately submit missing and invalid values and verify that the correction is understandable and associated with the relevant field. Do not depend on color alone. Client-side assistance and server validation have different roles; an interface refusing one input is not proof that the underlying endpoint enforces the required rules.
Example: revise an application form
In a hypothetical application form, submit a missing required field, locate the explanation and correct it using the keyboard. Check the result and retained input on return. Give the agent the failed interaction and expected behavior rather than a vague request for usability. Repeating the same journey provides an acceptance check for the revision.
Combine automation and observation
Use automated checks as assistance and retain interaction and assistive-technology observation. More agent capacity does not replace this verification. Record tested scope and untested conditions and leave a reproducible journey for another maintainer. This guide describes practical checks, not a claim of complete accessibility conformance.
Official sources
Pricing, availability and feature limits can change. Check the linked official pages before subscribing.
- W3C WAI form input validationInformation checked: 2026-10-28
- W3C keyboard trap guidanceInformation checked: 2026-10-28
- Cursor Agent overviewInformation checked: 2026-10-26
- Kiro specificationsInformation checked: 2026-10-28
- Cursor pricingInformation checked: 2026-10-26
- Cursor models and pricingInformation checked: 2026-10-26
- Kiro documentationInformation checked: 2026-10-28
- Kiro pricingInformation checked: 2026-10-28
- Kiro hooksInformation checked: 2026-10-28
- Google Antigravity IDEInformation checked: 2026-10-27
- Google Antigravity pricingInformation checked: 2026-10-27
- Google Antigravity plans and overagesInformation checked: 2026-10-27