Best fit
An ACR can remain in procurement circulation after the product version, scope, test evidence, or issue status that supported its claims has changed.
// Security & Compliance
Accessibility Evidence Freshness Auditor
Check whether accessibility conformance claims still trace to current, scoped, version-matched, manually reviewed, and retested evidence.
What problem does Accessibility Evidence Freshness Auditor solve?
An ACR can remain in procurement circulation after the product version, scope, test evidence, or issue status that supported its claims has changed.
Use it to
- Review an existing ACR claim set for a new release
- Catch stale or version-mismatched accessibility evidence
- Require manual evidence for recorded support claims
- Find closed issues that lack passing retest evidence
What it returns
- Claim-to-evidence lineage ledger
- Freshness, scope, version, and retest findings
- JSON qualified-review gate
- Accessibility-owner review memo
A representative input and result
input A support claim for mobile version 3.0 cites a 2025 automated failure from web version 1.0, has no owner or manual test, and its closed issue has no retest.
result Gate: BLOCK. Stale evidence, scope and version mismatches, contradictory result, missing owner and manual evidence, and unretested fix require qualified review.
Access and approval boundaries
- Read access to user-supplied local JSON and CSV evidence files.
- Write access only to the selected local audit output directory.
- No browser, network, credential, account, or environment-variable access is required.
Known limitations
- The tool does not test a product, generate an ACR, or certify WCAG, ADA, Section 508, or EAA compliance.
- Manual-test type requirements come from the supplied policy and remain organization-specific.
- A ready result means evidence lineage is reviewable, not that the product conforms.
// choose with context
Is Accessibility Evidence Freshness Auditor the right skill?
It returns
Claim-to-evidence lineage ledger. Freshness, scope, version, and retest findings.
Do not use it as
The tool does not test a product, generate an ACR, or certify WCAG, ADA, Section 508, or EAA compliance.
Compatibility, access, version, and licence
- Reads or accesses
- Declared local scope: claims.csv, evidence.csv, issues.csv, policy.json.
- Compatibility
- Documented normalized JSON and CSV input schemas. Python 3 on Windows, macOS, or Linux. Local files only; no account integration is required.
- Version
- 1.0.0
- Licence
- Review the package licence and seller terms at the linked destination.
Questions
Does it create a VPAT or ACR?
No. It audits evidence behind an existing claim ledger.
Does it test WCAG automatically?
No. It reads supplied test records and protects manual-review boundaries.
How is freshness decided?
Evidence age is compared with the supplied assessment date and maximum age.
Does it check releases?
Yes. Claim and evidence scope and product version must match.
Does ready mean compliant?
No. It means the evidence lineage is ready for qualified review.
Who should review blocks?
A qualified accessibility owner and any required procurement or legal reviewer.
Accessibility Evidence Freshness Auditor keeps proof and approval boundaries visible.
The listing includes the tested package, realistic samples, declared permissions, and known limitations.
Get Accessibility Evidence Freshness Auditor on Agensi