AI tools for UX design: test the interaction, not the mockup Evidence date: 2026-10-07 Decision criteria Prototype behavior and implemented keyboard and assistive-technology support. Editorial evaluation scenario Fictional checkout: the address is invalid; the screen shows only a red border. A useful error message tells the user what to fix and keeps their entered information. Check focus and announcement in the working interface; a static visual cannot establish either behavior. Prototype behavior and implemented keyboard and assistive-technology support. Input / draft / final edit Fictional checkout: the address is invalid; the screen shows only a red border. The form is clear because the red outline indicates the error. Specification: show “Enter a postcode” beside the field, associate the message with it and preserve the entered address. Verify focus and announcement in implementation. Before buying Figma Documented: Figma documents accessibility considerations for prototypes. Check: Prototype behavior and implemented keyboard and assistive-technology support. Manual or conventional route Documented: Use direct prototyping when the flow is already defined and needs interaction review. Check: Editorial workflow advice; this is not a measured comparison or vendor performance claim. Official sources https://help.figma.com/hc/en-us/articles/7810391964695-Accessible-prototypes-in-Figma Record your own test: selected plan, date, input, output, corrections, export and total cost. This sheet does not claim a vendor test.