Skip to content
Agentic Experience Design Language Help Go to the portal

Read accessibility check results

Find a check on the portal, read its issues, pages and keyboard map, and accept issues as known.

For designers, publishers and admins2 min read

The portal keeps each accessibility check's results: those your CI uploads, and those the portal runs itself. You need the designer role or above, because reports show what the checked pages showed.

Find a check

  1. Open Accessibility checks (/accessibility-checks).
  2. The list shows your organisation's checks, newest first, with who started each, its status and result, and how many issues are New and Known. Filter by project with the chips above it.
  3. Choose a check to open it.

The top of a check compares its figures with the run before it, and lists notes about what wasn't checked.

The tabs

  • Issues: each problem once, grouped by Check or Page. Search, and filter by Errors, Warnings, the kind of check, or New only. Open an issue for why it matters, how to fix it, where to fix it, where it happens, and up to three screenshots with the element outlined. Copy for an issue tracker copies it as markdown.
  • Pages: every page checked, and whether it was checked, failed or skipped.
  • Keyboard map: the tab order as a picture, each stop numbered, and as text.
  • To review: results the checks couldn't decide, such as text over an image. They never fail a run; look at each yourself.
  • Details: versions, CI details, and Files: download report.json, junit.xml and report.html, or Open report in a new tab.

Errors fail a run; warnings only when the pipeline asks. A run with no issues means these checks found nothing, not that the pages are accessible: test keyboard and screen reader use too.

Accept issues as known

For checks of your organisation's sites, publishers and admins can accept issues they won't fix now. Later checks of the site then show them as known instead of new.

  1. On Issues, choose Accept issues as known, or Accept as known on one issue.
  2. Choose the issues, and say Why, such as "Fixed in the next release, tracked as WEB-1234".
  3. Confirm.

The site's Known issues tab lists them, and Download baseline file gives the same file for your CI (see Accessibility checks in CI).

How long results are kept

The portal keeps runs and their issues for a set time, and screenshots for less; the latest complete run of each project is always kept. Admins can delete a check with Delete check under Details.

If something goes wrong

If something goes wrong
What you seeWhat to do
You can't open Accessibility checksYou need the designer role or above, and your organisation's plan must include it. Ask your admin.
"No checks yet"Nothing was uploaded yet. Choose Copy CI step, or see Accessibility checks in CI.
"This check failed"The check couldn't run. Read the reason in the alert, fix it, then check again.