Step 1
Record tool, rule, page, and test dates
EAA accessibility readiness
Accessibility Evidence Report
Organize automated findings, manual test notes, affected journeys, remediation status, limitations, dates, and review ownership.
Direct answerCreate a transparent evidence record that distinguishes automated signals from manual testing and unresolved accessibility barriers.
What this page is for
Accessibility signals inside the same evidence workflow.
Teams sharing accessibility progress with developers, agencies, clients, and internal reviewers.
A score alone does not show what was tested, which pages and journeys were covered, or whether fixes were manually verified.
This is a compliance workflow, risk discovery, and evidence management tool. It is not legal advice, not a legal certification, and manual review is required.
What the workspace generates
Open beta report outputs
- Page language and image alt text signals
- Optional EAA worker accessibility scan when configured
- Accessibility summary inside the product evidence pack
- Developer-friendly issue notes for manual review
- Review reminders and exportable audit trail
- Combined product compliance and accessibility workspace output
Intent-specific review
A practical checklist for accessibility evidence report.
This checklist narrows the workflow to the task on this page. Verify every item against the live product, service journey, and source evidence.
Step 2
Separate automated and manual findings
Step 3
Attach reproduction and verification notes
Step 4
State excluded journeys, limitations, and next review
Example output
Typical findings and generated files
These examples show the shape of the workflow output. They are not legal conclusions and require manual review.
Image alt text signal missing or incomplete
review product images manually.
Page language signal detected or missing
confirm listing and warning language requirements.
EAA worker status
worker_available when the Playwright / axe scan node is configured.
Checkout-flow accessibility requires separate scripted testing and manual review.
Checkout-flow accessibility requires separate scripted testing and manual review.
Methodology and review status
Rules-based evidence review with explicit boundaries.
The workspace extracts bounded page evidence, applies versioned rules, and optionally runs axe in an isolated browser worker. Automated output is directional and must be verified against the live journey, supplier evidence, product-specific requirements, and applicable national law.
Last reviewed: .
Primary references
Authoritative sources for deeper review.
Free public beta
Paste a product or ecommerce URL into the unified workspace.
No login and no payment. All generated outputs are open in the Free Beta workflow.
New product review
Start with a product link
Use one URL for a focused review, or paste a small batch when you need to compare listings.
Sales countries for professional language review · none selected
Manual fallback if a product page is blocked
Run a product link check to generate a complete report.
No login, no payment, no locked report. Results are generated from extracted page signals and structured rules.
FAQ
Questions about this readiness workflow
Is the Accessibility Evidence Report an accessibility certification?
No. It provides readiness signals and an evidence workflow. Conformance claims require an appropriately scoped evaluation, manual testing, and accountable professional review.
Why are manual accessibility tests still required?
Automated tools detect only part of the problem space and cannot fully assess task completion, content meaning, assistive-technology behavior, or the complete customer journey.
Related pages