Coding and Data
Provide code and the user flow. A screenshot can reveal contrast or layout problems, but not keyboard or screen-reader behaviour.
Audit this interface against the supplied interaction and markup. Check semantics, heading order, keyboard operation, focus visibility, accessible names, form errors, contrast assumptions, zoom, motion and screen-reader announcements. Do not infer compliance from a screenshot alone. Mark what needs browser or assistive-technology testing. Markup: [HTML OR COMPONENT]. Styles: [CSS]. Interaction: [USER FLOW].HTML OR COMPONENTCSSUSER FLOWEvidence-based findings, test steps and narrowly scoped fixes with manual checks clearly separated.
AI output can be incomplete or wrong. Verify facts, run code, check citations and keep private data out of tools that your organization has not approved.
Subscribe now to keep reading and get access to the full archive.