The confirmation disappears after 3 seconds.
Someone who looks away can’t tell the invitation went out, and may send it again.
Proposed change. Keep the confirmation until it’s dismissed or the page changes, and put it in a status region.
The usability lens reads each try for wrong turns, backtracking, repeated steps, and dead ends. AI proposes each issue with the evidence behind it. You decide what to do about it.
Heuristics a product designer would recognize, applied to a whole captured try, not a single screenshot.
Did the product say what happened, for long enough, where the person was looking? The example issue: a confirmation that disappeared after 3 seconds.
Did the person know where they were, and where to find the next step? Wrong turns and backtracks are counted and shown.
When something went wrong, could the person tell, and could they get back? Error messages are quoted exactly as they appeared.
Every issue has a title, why it matters to the person trying, a proposed change, and the screen. The tag shows who set it.
Someone who looks away can’t tell the invitation went out, and may send it again.
Proposed change. Keep the confirmation until it’s dismissed or the page changes, and put it in a status region.
demo-target.test/app/team · step 5 of 7 · after “Send invitation”
The confirmation disappears after 3 seconds.
Someone who looks away can’t tell the invitation went out, and may send it again.
An issue is anything that got in the way, or a change that would make the task shorter or clearer. Each one is pinned to the screen where it happened.
Here, the confirmation that disappears is also never announced. Switch the lens to see both on the same capture, with no second review.
Switch the capture above to the accessibility lens: mark 1 becomes WCAG 4.1.3 (Status Messages), set by rule. See the accessibility lens.
Paste your address. Checking public pages is free, and the draft is private to you.