Suggestions and accessibility

Act on the visual suggestions and the accessibility report an exploration leaves.

Besides its bugs, an exploration leaves two reports on the pages its subagents opened. Suggestions are small visual problems that are not bugs, such as names that do not line up in a list or text below the contrast of WCAG's highest level, Level AAA. The accessibility report checks the same pages against Levels A and AA of WCAG 2.2, the shared standard for accessible websites. This page shows how to read both and what to do with each item in them.

Where to find them Link to Where to find them

Rehearsal writes both reports when the exploration ends. In the chat, the panel lists Accessibility and Suggestions after Bugs, each with how many items still stand, and the card at the end of the exploration has a square for each that opens it.

On the Bugs page, the Accessibility and Suggestions pills show the newest exploration of the app chosen at the top, under a line such as "From the exploration of 3 November, on 9 pages." A report describes the app on the day it was explored, so an older report stays in the chat where it was made.

Suggestions Link to Suggestions

Suggestions come from two places. Once the exploration has ended, Rehearsal looks at a screenshot of each page the subagents opened, at the width they opened it at, and notes what could look better. That look leaves out bugs, broken parts, accessibility and the words themselves, because other checks cover those. The accessibility checker adds the Level AAA suggestions. Suggestions are grouped by kind:

KindWhat it covers
Out of lineThings in one row, column or list that should line up and do not.
Uneven spacingGaps between alike things that differ when they should match.
Looks offOne thing that does not match the rest of the page, such as its colour, size or shape.
Level AAAText colours below the stricter contrast of WCAG's highest level, such as "Grey text is 4.91 to 1 at its lowest. Level AAA asks for 7 to 1." The accessibility checker measures these.

Press a suggestion to open its page. It shows the sentence, the page and width it was seen at, and the screenshot cut round the part it is about, outlined with dashes. Where they apply, Colours lists the colours that were read and Where lists every place it was seen.

What to do with a suggestion Link to What to do with a suggestion

  • Watch the recording opens the subagent's browser at the step that reached the page.
  • Copy prompt for your coding agent copies a prompt with the whole suggestion: its kind, its sentence, the page and width, and where on the page it is. Paste it into your agent and it makes the change.
  • Copy copies the suggestion as plain words, for a message or an issue.
  • Mark as fixed says the change is made, and Rehearsal offers to check the page again, as the next section shows.
  • Ignore sets the suggestion aside, and it stays aside: a later exploration that sees the same thing on the same page files it already ignored. Undo brings it back.

When an exploration ended on its spending limit, Rehearsal does not look at the screenshots, so only Level AAA suggestions can appear, and an empty list says Rehearsal did not look for suggestions. Anyone who can read the project can copy a suggestion. Changing one, like changing an accessibility issue, needs the Manage projects and Use Re:agent permissions.

Check a change again Link to Check a change again

After Mark as fixed, the card asks Check the page again? Check again opens the page at the width it was seen and runs the check that found the item: the accessibility checker for an issue or a Level AAA suggestion, and another look at a screenshot for the rest. Not now keeps your mark without a check, and the card keeps Check again for later.

While it runs, the card says "Checking /cards again." Then it says what it found:

  • "Fixed. Rehearsal checked the page again and it is gone." The item folds to Fixed.
  • "Still there when Rehearsal checked again." The item stands again, ready for another try.
  • "Rehearsal could not tell from the page.", or another line that says why it could not check. Nothing was decided, so your mark stays.

A later exploration that sees an item you marked fixed brings it back, with "Seen again on" and the day under it.

Good to know

A check never signs in, so Rehearsal offers Check again only for pages it opened without a test account. For a page behind a sign-in, Mark as fixed takes your word for it without asking.

The accessibility report Link to The accessibility report

The report holds all 55 criteria of WCAG 2.2 Levels A and AA, and puts each one in one of three groups by how it was checked, so the groups always add up to 55:

GroupHow its criteria were checked
Checked automaticallyAn accessibility checker tested the pages for the eleven criteria it can judge on its own, such as text contrast, page titles, names of buttons and links, target size and pages that fit a narrow screen.
Checked by subagentsA subagent checked a planned test case against the criterion, such as Escape closing a menu. The group appears only when there are some.
Not checkedEvery other criterion, listed by name.

A criterion with issues shows how many in a rose pill and starts open. One that Rehearsal checked everywhere and found nothing wrong with says No problems found. The report never says a criterion passed and gives no score, because a check that finds nothing has not proved there is nothing.

Open a criterion to see its reference, such as WCAG 1.4.3, Level AA, which is the number audits and developers cite. Then come its issues, or one line of how it was checked, such as "Checked on 9 pages at 1440 and 320 pixels wide." Where the checker could not decide, the criterion says so, as in "Rehearsal could not tell in 2,048 places, such as text over a picture."

An issue Link to An issue

An issue is one problem across every page it was seen on, so one text colour that fails on twenty buttons is one issue in "20 places on 9 pages", fixed once. A contrast issue is one per text colour, and any other issue is one per rule and element.

Press an issue to open its page, which leads with a sample of what failed. For a contrast issue that is a tile in the failing colours with the page's own words on it, the ratio beside it, such as 3.66 to 1, what the level asks, such as Level AA asks for 4.5 to 1, and the two colour codes. For any other issue it is one sentence of what the level asks, such as "Every button has a name a screen reader can say.", with the code of the element that fails. Where then lists every element with its page.

The card under it is Fix this issue, with the same presses a suggestion has: Copy prompt for your coding agent, Copy and Mark as fixed, with Check again after it. In place of Ignore it offers Mark as not an issue, which folds the issue to Not an issue with Undo, and a later exploration that finds it files it already marked. Rehearsal writes no test for an accessibility issue, so Check again and the next exploration are how a fix is checked.

Next steps Link to Next steps