Review the accessibility of your pages

Collecting good examples is half the work; the pages you build from them should work for everyone. The Accessibility review tab keeps a simple audit of your own pages. It is stored in this browser, separately from your boards, and has its own backup file.

An important limit first: the automated part checks static HTML for common problems. It does not run scripts or evaluate CSS, and it cannot prove that a page conforms to WCAG. Keyboard use, visible focus, screen readers and color contrast need a person – that is why the review tracks them separately.

1. Add pages

Under Add a page, enter a Page name (for example Home) and, if the page is public, a Page URL (optional). Choose Add page. The Pages list shows every page with the number of open observations.

You can attach a screenshot to each page with Attach page screenshot (PNG, JPEG or WebP up to 600 KB; 1.5 MB per review). It stays in the review and is never sent to the scan.

2. Run the scan

Choose Run accessibility snapshot. Pageboard sends the page URL – or, if you pasted something into HTML to scan (optional), that HTML instead – to the usefulweb.site Accessibility Snapshot tool. URL scans fetch the public static HTML once. Pasted HTML is handy for pages behind a login or local drafts.

The results appear under Automated observations: a title, an explanation, the kind (failure, best practice, needs review), the severity, the WCAG success criteria, the line and the element selector. The observation texts come from the tool and are currently shown in English.

3. Work through the observations

Each observation has a Status: Open, Needs retest (you changed something) or Verified by reviewer. Notes keep what you did. When you fix your page, set the status to Needs retest and run the scan again:

• Observations that come back are reopened, with your notes kept.
• Observations that are no longer found become Not seen in latest scan. That is a hint, not proof of a fix – check it yourself.
• If a scan was truncated, missing observations keep their status.

4. Manual checks

Manual checks lists keyboard navigation, visible focus, screen reader and color contrast for every page. Set each Result to Untested, Pass, Fail or Needs retest and write down what you tested. Custom manual check adds your own items, such as Video captions.

5. Backup

The review lives in this browser only. Download audit backup saves it as JSON; Import audit backup… restores it on any device. Project files and Drive saves of your boards do not include the review.

Next: Automate boards with the API and MCP.