Skip to content

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

Before · illustrativeThree concerns worth a look.

Illustrated focus route: Work email → Confirm visit. Dashed blue marks the keyboard gap. It is an annotation. A fictional booking screen in Fieldday, read for three concerns. Back and Confirm visit have the same visual weight; the time choices show no time zone; and in the illustrated keyboard trace, Tab goes from Work email straight to the buttons, past Choose a day and Choose a time.

After · proposed changeOne clearer way to book.

Illustrated focus route: Work email → Day → Time → Confirm. Solid blue shows the proposed focus indicator. The same Fieldday booking screen after the proposed change: Confirm visit is the one primary action, Europe/Berlin is named beside the time choices, and the illustrated keyboard route reaches Choose a day and Choose a time with a visible focus ring.
  1. Design interpretation: Back and Confirm visit have the same visual weight.Use one primary action; keep Back quiet.
  2. 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.
  3. 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.

Product
Ledgerly
Reviewed on
3 October 2026
It worked when
sam@demo-target.test is listed, and the admin knows it was sent.
Perspective
New administrator (2 attempts)

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.

Attempt 1 as New administrator · 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. Three seconds later the message was gone (marked)
  7. The invitation is listed as Pending

0 retries · task completed, confirmation missed

Attempt 2 as New administrator · 7 steps

  1. Opened Team
  2. Typed sam@demo-target.test
  3. Pressed Send invitation
  4. “Invitation sent” showed, then vanished after 3 seconds (marked)
  5. Looked for a confirmation. None on screen (marked)
  6. Pressed Send invitation again (marked)
  7. 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.

New administrator · Team · 2 attemptsRedrawn example
  • 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.

  1. 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.
    Attempt 1 · step 5 of 7Redrawn example
    Step 5: the confirmation appears, as the task expects.
  2. 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.

    Attempt 1 · step 6 of 7Redrawn example
    Step 6: 3 seconds later, the confirmation is gone. Pin 1 marks where it was.
  3. 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

    Attempt 1 · step 6 of 7Redrawn example
    Step 6: both issues point at the same element, pins 1 and 4.1.3.
  4. 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.

    Recheck · step 6 of 7Redrawn example
    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 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, attempt 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.

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.

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.