A goal gives critique something to answer.
UICrit asks designers to identify the interface’s task before critiquing it, then links comments to regions of a screenshot. That work informs our emphasis on task context and evidence tied to a specific place. [1]
Variantly follows the task across browser states. The useful question is whether the invitation reached its intended state and what got in the way. A static screenshot can show a label; the next screen can show that the confirmation disappeared.
Make the perspective explicit.
You describe the knowledge, role or interaction constraints to examine. A new administrator and someone using only a keyboard can expose different conditions in the same task. Stating those assumptions makes the attempt easier to interpret.
Wang, Morgenstern and Dickerson show how identity-conditioned simulations can misrepresent groups and flatten their diversity. That informs our preference for concrete task conditions and context you can substantiate, rather than treating an identity label as evidence of someone’s behavior. [3]
A perspective is a stated test condition. It does not represent a population or establish how people with that background or disability will behave.
Keep the observation close to the claim.
TaskAudit investigates mobile accessibility barriers that appear through interaction, using execution traces to examine what happened. It informs our choice to follow a task through its changing states. Its mobile study and screen-reader proxy do not establish web conformance. [2]
Variantly keeps the screens and recorded steps behind an issue so your team can inspect the condition it describes. An attempt stopping is not, by itself, evidence that the task worked. AgentRewardBench treats evaluating a browser attempt as a separate problem and documents limitations in both model judges and benchmark rules. [4]
WCAG-EM recommends documenting coverage and findings, with supporting details such as screenshots, DOM snapshots, navigation steps and tool versions. This informs our emphasis on evidence someone else can examine. A capture still says only what was available in that state. [6]
Give rules and interpretation different jobs.
Deterministic checks look for defined failure conditions, such as a control without an accessible name. AI can propose context-dependent issues, such as an unclear confirmation. Both keep their evidence; your team decides what to do with it.
ACT Rules distinguishes a check’s applicability, expectation and outcome. A rule can cover only part of a WCAG criterion, so a pass can still require further testing. Variantly’s rule findings therefore attach to the report; they do not decide its conformance rows. [5]
Recheck the condition after a change.
A recheck looks for an issue’s condition again and records what matched, what changed and what could not be compared. Repeatability means keeping the task and comparison visible. It does not mean an AI attempt will always take the same path.
τ-bench studies consistency across repeated attempts as a separate question from success in one trial. That distinction informs how we read rechecks: one observed result is one piece of evidence. The paper’s API-based tasks do not measure Variantly’s repeatability. [11]
Recorded accessibility tasks can also replay when their schedule is enabled. Changed evidence can make a report row stale and require another decision. Finding a condition absent in one run does not show that it is absent everywhere.