Our designer wants to send Claude screenshots of a checkout flow for an early accessibility review. We don’t have a working prototype yet, so there’s no DOM, accessibility tree, or keyboard interaction to inspect.
I can see this being useful for spotting tiny text, unclear error messages, or information conveyed only through color. But I don’t want a confident-looking report that says our form labels or tab order are accessible when those details aren’t visible.
For a screenshot-based accessibility review, how should I ask Claude to separate visible concerns from things that need implementation testing? Would it make sense to request three groups: observed issues, possible issues, and checks that cannot be performed from the images?
I’m particularly unsure about contrast estimates when screenshots have been resized. Has anyone found a useful way to get design feedback without turning it into an unsupported WCAG compliance assessment?
Can you answer this question?
Write Answer0 Answers