See where a task breaks down, and check the fix.

Describe a task the way your customers would. Variantly attempts it from the perspectives you describe, on your live product or a staging site, and shows what it saw on each screen.

See plans with task reviewsRead an example review

The review is the explanation.

ILLUSTRATIVE REVIEW · DEMO TARGET · NOT A RUN

Ledgerly demo · Invite a teammate with the right accessExample · 2 attempts as New administrator
Expected result
“Invitations waiting for a reply” check: seen in 2 of 2 attempts.
Usability
1 finding, 1 needs a decision.
Accessibility, from rule checks
1 finding on 1 screen.

Needs a decision

Usability · feedbackAI interpretationNeeds a decision

The confirmation disappears after 3 seconds.

Seen in 2 of 2 attempts as New administrator · step 5

From your files: none. It rests on the screens alone.

Same condition · Accessibility · WCAG 4.1.3Rule check

The confirmation isn’t announced.

From rule checks, listed separately. Not decided here, and not a report row.

Your decision

Open the evidence to decide. A decision needs the evidence in view.

What happens nextRequired. It’s kept with the decision.

What this review didn’t cover

  • Only one perspective was tried. Other roles, such as an invited member, weren’t.
  • Whether the invitation email arrives. The check reads the screen only.
  • Real screen-reader use. The transcript is a virtual one.
  • No recheck has run.

Attempts

PerspectiveAttemptHow it endedCheck
New administrator1Finished, 7 stepsSeen
New administrator2Finished, 7 stepsSeen

Brief for an engineer or coding agent

Finding: The confirmation disappears after 3 seconds. (Usability, feedback; AI interpretation)
Same condition: The confirmation isn’t announced. (Accessibility, WCAG 4.1.3; rule check)
Where: /app/team, after "Send invitation" (step 5 of 7, attempts 1 and 2 as New administrator)
Element: #invite-flash, removed by a 3000 ms timer, not in a live region
Proposed change: keep the confirmation until dismissed or the page changes; render it with role="status".
Recheck: after sending, "Invitation sent to <email>." is still on screen on the next step and is announced.
Evidence: in a real review, links to the step 5 screen and its transcript.

  1. Start from the task, not a recording.

    A task is what someone needs to get done: invite a teammate, recover from a validation error, save a setting without losing work. You write it in your own words and say how you’d know it worked. Nothing runs until you start a review.

  2. Every result says how it was known.

    Each attempt’s check says “seen”, “not seen”, “couldn’t tell”, or “not checked” if the attempt stopped first. With no check, the assessment judges the task done or not done from the screens, marked as judged. Attempts are counted, never averaged. There’s no score or pass rate.

  3. Usability and accessibility, on the same screens.

    Usability findings each wait for a person’s decision. Accessibility findings from rule checks on the same screens are listed separately and aren’t decided in the review. Task-review findings don’t set report rows. Those come from full-coverage scans and replays of the live product.

  4. Bring what you already know.

    Upload research notes and support or analytics exports as Markdown, text, CSV, JSON or PDF with a text layer. Each finding shows the statements it relied on. The attempts don’t read them. Your files belong to your product.

  5. What a review can’t tell you.

    Attempts aren’t people. They show how the interface behaves, not how many people are affected, whether they’d convert or how they feel. Claims about comprehension or effort need research with people. Findings from what you tell it about a person are synthetic and directional: how that attempt chose, not how many users would. How we handle product access and evidence.

Task reviews come with every paid plan.

The free check is a different, smaller thing: accessibility results for your public pages. It doesn’t attempt tasks, sign in or submit forms.

Compare plansCheck public pages free
ACR package · $799 once
10 attempts with the purchase
Starter · $2,400 a year
40 attempts a month
Team · $7,200 a year
200 attempts a month, shared by its products

An attempt is one try at a task from one perspective.