Compare document accessibility reports with AI
Group existing findings by file, format or template. Identify recurring issues, compare a previous baseline and decide which fixes deserve investigation first.
To compare document accessibility reports with AI, collect the findings from the documents you want to consider together. A missing title in one application form is a local fix. The same omission in every form built from one template suggests a different place to look. The cross-document-analyzer helper collects that evidence through the Community Access document-accessibility wizard.
The result is only as complete as the original checks. A file that was never tested for keyboard navigation has no evidence on that question. Compare the audit scope before interpreting a higher score as an improvement, and retain a link from each repeated issue to its source report.
What it does
- Find headings or image descriptions missing across several handouts.
- Compare affected documents by format, folder or shared template.
- Identify a fix to the template that could improve future editions.
- Review which reported issues changed since an earlier audit.
- Read a score alongside the severity and confidence of the underlying findings.
Install and use
- Provide the original wizard and its analysis helper with authorised audit results. The shared scoring and report scripts use Node. An earlier baseline is optional.
- Ask “Group these findings by template. Which issue recurs most widely, and which documents would need another test after we fix it?”
- Open the source findings for the leading group before assigning work to a document owner.
FAQ
Source
Made by Taylor Arndt / Community Access. Original skill: cross-document-analyzer, published on GitHub under the MIT licence.
View on GitHub