Skip to content

Help

Decide a report row

Every row of your report is one WCAG criterion. Each row says how its value was set, in one of three tiers.

Rule checked

The WCAG edition sets the Parsing criterion (4.1.1): Supports in WCAG 2.1, Not Applicable in WCAG 2.2. No rule read the pages to set that value. Current checks attach findings to other rows for a person to rate.

Historical drafts may still contain ratings set by a rule. You can acknowledge those rows together, but their conclusions need review before another version can be published.

AI proposed

A model read the evidence for the row and proposed a value with remarks. Partially Supports and Does Not Support proposals outside your random one-in-five sample are accepted by default. You open each row in the sample and accept or reject its proposal.

Supports and Not Applicable proposals always wait for a person under Needs a person, with the proposal shown, and you accept it once you have opened its evidence.

Rejecting a proposal doubles the sample, and the row waits under Rejected for your value. Proposals outside the sample stay reviewable: choose Review anyway beside their count.

Needs a person

A person reviews the evidence and the criterion's applicability, then chooses a rating. A detected failure alone does not decide Partially Supports versus Does Not Support; the person assesses the affected functionality.

Decide a row

  1. On your product's Overview, choose Decide beside the report rows that need you, or open Review and choose For the report. The group lists the rows waiting on you: your sample first, then the rows that need a person, then the proposals you rejected.
  2. Pick a row. Review shows its captures and the findings on them. Choose Open the full evidence for every tab: Screenshot, Accessibility tree, Focus trace, Screen-reader transcript (virtual), Rule output and Journey. The transcript is generated from the accessibility tree, not recorded from a screen reader; Variantly checks that method against NVDA with Chrome on a fixed set of test pages whenever the capture changes.
  3. Under Conformance, choose Supports, Partially Supports, Does Not Support, Not Applicable or Not evaluated.
  4. Write the remarks. They are printed on the report beside the row.
  5. Choose Accept for a proposal, or Confirm for your own value. Every decision attributed to you requires opened evidence. Choose Reject the proposal to set the value yourself.

Accepting records your name and the date on the row. The row keeps its history: the proposal, each decision, and when you opened the evidence. The report and its exports say who set each row.

Keys while you decide rows

  • J and K move to the next and previous row.
  • 1 to 4 and N pick a conformance value.
  • C accepts or confirms, and R rejects the proposal.
  • F opens the capture full screen, and [ and ] move between findings on it.

Component issues

A component issue is repeated markup, grouped by its fingerprint. It takes its name from the markup where the markup names itself (a data-component, class or test-id), and otherwise from what it renders. A row's evidence opens the capture the row rests on.