Skip to content

See where the task got harder, on the screen where it happened.

The usability side of a review reads each attempt the way a design review would: missing feedback, wrong turns, repeated steps and dead ends. AI proposes each issue with the screens behind it. You decide what to do about it.

New administrator · Team · the retry, step 6Redrawn example
  • 1Gone after 3 secondsUsability · attempt 2, step 4
  • 2Sent twiceUsability · attempt 2, step 6

The path is the evidence.

Analytics shows where people left. An attempt shows the screen it was on when the task got hard, and what it tried next.

New administrator · attempt 2 of 2Redrawn example
  1. Opened Team
  2. Typed sam@demo-target.test
  3. Pressed Send invitation
  4. “Invitation sent” showed, then vanished after 3 seconds4.1.3No status role, so nothing was announced
  5. Looked for a confirmation. None on screen
  6. Pressed Send invitation againRetry
  7. Two invitations waiting for sam@demo-target.test

1 retry · 1 duplicate · completed, at a cost

What it checks.

Heuristics a product designer would recognize, applied to a whole captured attempt, not a single screenshot.

Feedback

Did the product say what happened, clearly and for long enough to be noticed?

Wayfinding

Could the attempt tell where it was, and find the next step? Wrong turns and backtracks are counted and shown.

Recovery

When something went wrong, did the screen say so, and was there a way back? Error messages are quoted exactly as they appeared.

Each issue says what happened and what to change.

Every issue has a title, why it matters to the perspective attempting the task, a proposed change, and the screen. Its tag says where it came from: a rule, the AI, or a person.

Proposed by AIUsability · feedback

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.

Step 5 · demo-target.test/app/teamRedrawn example

What a person decides

  • Fix itWrites the fix brief. After the change, a recheck looks for what you intended.
  • Not sure yetThe issue waits, with its screens, for your next study.
  • Working as intendedCloses the issue and keeps the reason.

Where each tag comes from.

  • Set by ruleSame answer every run, like WCAG 4.1.3.
  • Proposed by AIWhat an attempt hit, with its screens.
  • Decided by a personFix it, Not sure yet or Working as intended.
  • RecheckedThe same task again, after the change.
  • Not coveredWhat no attempt reached, listed and never counted as passing.

Beside your research, and beside accessibility

  • Where it sits beside your research. An attempt shows where to look; it can’t say how many people would hit it or how they felt. Choose Not sure yet and the issue waits, with its screens, for your next study. What a review can and can’t tell you
  • Some of what gets in the way is also a barrier. The confirmation that vanished is also never announced. The same capture, read for accessibility, gives WCAG 4.1.3, set by rule. Accessibility reviews

Start with what you meant.

Start with a public URL. Arrange signed-in or private access separately. No static design files.

We use these details to reply about the review.