Example review

Invite a teammate with the right access.

A worked example on Ledgerly, a demo product: the tries, the issues, the decision, and the fix brief. Screens are redrawn from the demo product. No real review was run.

Product
Ledgerly demo
Reviewed on
3 October 2026
What success looks like
“sam@demo-target.test” appears in “Invitations waiting for a reply”.
Who tried
New administrator (2 tries)

7 steps, and the confirmation vanished at step 6

Steps 5 and 6 are marked. At step 5 the confirmation showed. At step 6 it was gone.

Try 1 7 steps

  1. Opened Team
  2. Typed sam@demo-target.test into Email address
  3. Left Role as Member
  4. Pressed Send invitation
  5. Saw “Invitation sent to sam@demo-target.test.” (marked)
  6. On the next screen the message was gone (marked)
  7. Reloaded; the invitation is listed as Pending

Try 2 8 steps

  1. Opened Team
  2. Typed sam@demo-target.test into Email address
  3. Left Role as Member
  4. Pressed Send invitation
  5. Looked away from the screen
  6. Looked back: no confirmation on the screen (marked)
  7. Pressed Send invitation again (marked)
  8. Reloaded the page: the invitation was listed as Pending

Try 2 ran the same task. Steps 6 and 7 are marked: it looked away, saw nothing, and sent the invitation again.

Invite a teammate with the right access.Try 1 of 2 as New administrator, 3 October 2026

demo-target.test/app/team · step 5 of 7 · after “Send invitation”

  1. The confirmation disappears after 3 seconds.

    Proposed by AI

    Someone who looks away can’t tell the invitation went out, and may send it again.

  2. Try 2 sent the invitation a second time.

    Seen in try 2

    It looked away, saw nothing, and pressed Send invitation 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.

Example screen redrawn from a demo product, not from a real review.

One message, two issues: usability and accessibility

AI proposed the usability issue and a rule set the accessibility one. A person decided.

Proposed by AIUsability

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.

Set by ruleAccessibility · WCAG 4.1.3

The confirmation isn’t announced.

A screen reader announces the page load and the Team heading, but nothing about the invitation.

Proposed change. Give the message role="status" so screen readers announce it without moving focus.

Decision: Act on it. Ledgerly reviewer, 3 October 2026. “Both readings point at the same element. One change closes both.”

The fix brief your coding agent gets

Plain text, written to paste into a prompt. The capture is attached.

Fix brief · issue 1Draft · proposed by AI

Fix:      keep the invitation confirmation until dismissed or the page changes, in a status region.
Where:    /app/team, #invite-flash (removed after 3000 ms; no role="status")
Change:   render the message in <div role="status">; remove the 3000 ms timeout; keep a Dismiss button.
Recheck:  message present at step 6; transcript includes "Invitation sent to sam@demo-target.test."
Evidence: capture 3 October 2026, try 1, steps 5 and 6
Paste it into Claude Code, Codex, Cursor or a pull request. The capture it rests on (screenshot, transcript and focus trace) goes with it, and the recheck runs the same task after the change.

Rechecked 5 October 2026 as New administrator: the message was present at step 6 and in the transcript, and both issues closed.

What this review didn’t cover

Listed so nobody mistakes a missing issue for a pass.

  • Other people. Only a new administrator tried this; a long-time administrator may read the page differently.
  • Whether the invitation email arrived.
  • A real screen reader. The transcript comes from the captured accessibility tree.
  • Other tasks on the Team page, such as changing a teammate’s role.

Start with your public pages.

Pick a task on your public pages. For signed-in tasks, add a test account in the app first.

Leave your email for when Variantly opens.