One review, from intent to change
One booking flow. Design, usability and access together.
Fieldday’s builder wants people to choose a visit confidently. One screen brings design, usability and keyboard access into the same review.
Fieldday’s booking screen, before and after the proposed change
- Design interpretation: Back and Confirm visit have the same visual weight.Use one primary action; keep Back quiet.
- Usability concern: Time choices show 9:00 and 9:30 without a time zone.Name the time zone before selection and in the saved visit.
- Synthetic observation: In the illustrated trace, Tab skips the date and time controls.Make the day and time controls keyboard reachable, with visible focus.
Fieldday and Ledgerly below are different fictional products, so nothing here is a measured before and after.
A longer example: Invite a teammate with the right access.
A worked example on Ledgerly, a demo product: the attempts, the issues, the decision, the fix brief and the recheck. Screens are redrawn from the demo product. No real review was run.
Attempt 1 saw the confirmation at step 5. By step 6 it was gone.
Steps 5 and 6 are marked. Attempt 2 lost it sooner, and sent the invitation twice.
- Opened Team
- Typed sam@demo-target.test into Email address
- Left Role as Member
- Pressed Send invitation
- Saw “Invitation sent to sam@demo-target.test.” (marked)
- Three seconds later the message was gone (marked)
- The invitation is listed as Pending
0 retries · task completed, confirmation missed
- Opened Team
- Typed sam@demo-target.test
- Pressed Send invitation
- “Invitation sent” showed, then vanished after 3 seconds (marked)
- Looked for a confirmation. None on screen (marked)
- Pressed Send invitation again (marked)
- Two invitations waiting for sam@demo-target.test (marked)
1 retry · 1 duplicate · completed, at a cost
Attempt 2 ran the same task. From step 4 it went wrong: the confirmation vanished, it found none, and it sent the invitation again.
- Gone after 3 secondsUsability · attempt 1, step 6
- Never announcedAccessibility · set by rule
- Sent twiceUsability · attempt 2, step 6
See the screen. Decide the issue. Recheck it.
Issue 1, step by step, the way a reviewer meets it in Variantly.
Intended
From the task: what should happen
- Someone wants to
- Invite a teammate with the right access.
- It worked when
- sam@demo-target.test is listed, and the admin knows it was sent.
Step 5: the confirmation appears, as the task expects. Observed
Seen in this attempt: attempt 1 as New administrator, step 6 of 7
- Intended
- The admin knows the invitation was sent.
- Observed
- About 3 seconds after Send invitation, the confirmation disappears.
A screen reader announced nothing about it either.
Step 6: 3 seconds later, the confirmation is gone. Pin 1 marks where it was. Decision
- Proposed by AI · UsabilityThe confirmation disappears after 3 seconds.
- Set by rule · Accessibility · WCAG 4.1.3The confirmation isn’t announced.
Decided: Fix it
Ledgerly reviewer, 3 October 2026. “Both readings point at the same element. One change addresses both.”
Not chosen: Not sure yet · Working as intended
Proposed change · not checked yet
Keep the confirmation until it’s dismissed or the page changes, and put it in a status region.
Checked in step 4, Recheck
Step 6: both issues point at the same element, pins 1 and 4.1.3. Recheck
Checked on screen, 5 October 2026
Rechecked as New administrator, the same task from the same perspective
- Intended
- The admin knows the invitation was sent.
- Rechecked
- Seen: at step 6 the confirmation stays, and it’s announced.
Sending the invitation twice, from attempt 2, is a separate issue, and still open.
Step 6 of the recheck: the confirmation stays until it’s dismissed.
The fix brief your coding agent gets.
Plain text, written to paste into a prompt. The capture is attached.
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, attempt 1, steps 5 and 6
What this review didn’t cover.
- Other perspectives. Only a new administrator attempted this; a long-time administrator may read the page differently.
- The email. 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.