Proof PackDocumentation Standard
Every accessibility issue we identify comes with a comprehensive evidence package— timestamps, screenshots, test results, and step-by-step remediation guidance.
What's in a Proof Pack?
A complete evidence package that documents the issue, quantifies impact, and provides everything needed for remediation.
Evidence Capture
Screenshots, recordings, and test tool outputs that document the issue.
Annotated Screenshots
Visual documentation with highlighted problem areas, element selectors, and context markers.
Screen Reader Recording
Audio/text transcription of what screen readers announce (or fail to announce).
Tool Output
Results from axe-core, WAVE, Lighthouse, or other automated testing tools.
DOM Snapshot
Relevant HTML structure showing the accessibility violations.
Timestamp & Audit Trail
Every piece of evidence includes cryptographic timestamps for legal defensibility.
ISO 8601 Timestamps
Precise date/time recording in universal format with timezone.
Audit Log Hash
SHA-256 hash of evidence files for tamper-proof verification.
Tester Attribution
Name, credentials, and methodology of the person who performed the audit.
Environment Details
Browser, OS, assistive technology versions, and device information.
Impact Assessment
Quantified severity and business impact to prioritize remediation efforts.
Just11y Priority Score
0-100 weighted score based on impact, frequency, business risk, effort, and confidence.
WCAG Mapping
Specific success criteria violated (e.g., 1.1.1 Non-text Content, Level A).
User Impact Statement
Plain-language explanation of who is affected and how.
Legal Risk Flag
Indication of ADA/WCAG compliance implications for legal teams.
Remediation Guidance
Clear, actionable fix instructions with before/after code samples.
Step-by-Step Fix
Numbered instructions that any developer can follow to resolve the issue.
Code Samples
Before/after HTML, ARIA, or CSS snippets showing the exact changes needed.
Component Reference
Links to accessible pattern libraries (WAI-ARIA APG, Inclusive Components).
Testing Verification
How to confirm the fix works, including AT testing steps.
Workflow Integration
Export to your existing tools—GitHub, Jira, CSV, or API.
GitHub Issue
One-click export to properly formatted GitHub issue with labels and assignees.
Jira Ticket
Jira-compatible format with custom fields for accessibility tracking.
CSV Export
Bulk export for spreadsheet analysis or custom reporting.
API Access
Programmatic access for custom integrations and automation.
Example Proof Pack
Here's what a real Proof Pack looks like for a critical accessibility issue.
Missing label on Phone field
Checkout / Contact Form
Evidence
"Edit text, Phone, required" — missing field purpose
⚠ axe-core: form elements must have labels
Metadata & Fix
2024-01-15T14:32:18Z
sha256:a7f3b2c8d4e5f6a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5
<input type="tel" name="phone" required><label for="phone-field">Phone Number</label>
<input type="tel" id="phone-field" name="phone" required>Documentation That Stands Up in Court
Accessibility lawsuits are on the rise. In 2023, there were over 4,000 ADA digital accessibility lawsuits filed in federal court—and many more demand letters and state claims.
When legal teams come knocking, you need more than a spreadsheet. You need timestamped, hash-verified evidence showing exactly when issues were identified, what was found, and how remediation was tracked.
Just11y Proof Packs provide:
- Cryptographic timestamps that prove when audits occurred
- Hash verification to prove evidence hasn't been tampered with
- Clear audit trails showing remediation progress
- Documentation that demonstrates good-faith compliance efforts
Get Your First Proof Pack
See what a professional accessibility audit looks like. We'll document every issue with legal-grade evidence.