Advancement · School Operations

From a scan report
to a fix list with owners

Enter the findings from any accessibility scanner, one rule per row, with its WCAG criterion, impact, instances, owner and status. The tool totals the instances, tracks the share fixed and the critical and serious ones still open, finds open findings with no owner, says where to start and prints a fix list sorted by impact, with the checks by hand a scanner cannot do.

Add a scanWhat you get
$12one-time · every device you sign in on
Buy · $12

Included with Caveat Classroom and Whole-school licenses. Or get it in the School operations toolkit, $49 for 66 items.

Scans

The worked example is made up: a district website scan with the critical findings fixed, an elementary school site scan with no owners yet and a first scan of a parent portal. Saved on this device only.

Loading the scan form. If nothing appears, turn on JavaScript.

What you get

Advancement · School Operations$12 · included with Classroom and Whole-school licenses

What you finish with
A record per scan: the site, tool, date, pages and what was included; a row per finding with rule, WCAG criterion, impact, instances, owner and status; five checks by hand and the next scan date. Total instances, open critical and serious instances, share fixed, findings with no owner and where to start; a printed fix list sorted by impact.
Who it is for
Web coordinators, technology directors, communications staff and vendors who maintain school, district and nonprofit websites.
Format
Browser tool with a saved record per scan. Prints the fix list, the record, every scan in a table or a blank form; downloads a spreadsheet (.csv); exports and imports a file.
Access
$12 one-time, yours on every device you sign in on; the tool opens once you are signed in with it. Included with Caveat Classroom and Whole-school licenses. Also in the School operations toolkit ($49) and the Advancement Suite pass ($99), and 1 more bundle. Everything you type stays in this browser; nothing is sent to Caveat.
Where it lives
The School Operations space in Caveat Advancement.
Support
Questions about access, an order or a correction: team@caveatacademic.com.

How to use it

  1. Run your scanner and add a scan record.
  2. Enter one row per rule, with its count.
  3. Give every open finding an owner.
  4. Mark findings fixed, or cleared by a check by hand.
  5. Print the fix list and set the next scan.

Add a scan

What a scan covers

What a scan can and cannot tell youScanners findMissing alt text andform labelsText contrast below theratioMissing page languageand titleEmpty links and buttonsPeople findWhether alt text andlabels make senseKeyboard traps and lostfocusReading order andmeaningCaptions that match thespeechSo the record keepsEach rule with its countand ownerWhat was cleared byhand, and whyThe date of the nextscanWhat a scan can and cannot tell youScanners findMissing alt text and form labelsText contrast below the ratioMissing page language and titleEmpty links and buttonsPeople findWhether alt text and labels make senseKeyboard traps and lost focusReading order and meaningCaptions that match the speechSo the record keepsEach rule with its count and ownerWhat was cleared by hand, and whyThe date of the next scan
An automated scan is a starting list, not a verdict: a clean scan still needs the checks by hand.

Impact and instances

Most scanners rate each rule by impact on people using assistive technology and count the instances. Start with critical and serious findings that block a task, such as unlabelled buttons on an enrollment form, then the ones with the most instances, which often share one cause in a template. Fixing the template once can clear hundreds of instances.

Why the checks by hand

Automated tests can only check what can be measured from the code, so they find a minority of the barriers people meet. WCAG conformance needs people to test keyboard use, screen reader output, zoom, reading order, captions and whether text alternatives make sense. Mark a finding “not an issue” only after someone has checked it.

Sources

  1. World Wide Web Consortium (W3C). Web Content Accessibility Guidelines (WCAG) 2.2 (w3.org/TR/WCAG22).
  2. W3C Web Accessibility Initiative. Selecting Web Accessibility Evaluation Tools (w3.org/WAI/test-evaluate).
  3. W3C. Website Accessibility Conformance Evaluation Methodology (WCAG-EM) 1.0 (w3.org/TR/WCAG-EM).
  4. U.S. General Services Administration. Section508.gov: Test for accessibility (section508.gov).

The worked example is made up, including the sites, counts and owners. This tool organizes results you enter from any scanner; it does not scan sites, and it is not a conformance claim or legal advice. Nothing you type is sent to Caveat. Support: team@caveatacademic.com.