Build a web application that helps development teams track accessibility problems across website releases and determine whether recent changes introduced new barriers.
Users can upload accessibility scan results, manually record audit findings, import supported test reports, and associate each finding with a URL, page component, release, and severity.
The system should:
Group recurring findings across pages and releases.
Identify newly introduced issues, resolved issues, and regressions.
Map repeated issues to shared components when reliable identifiers are available.
Track keyboard navigation, focus visibility, accessible names, contrast, labels, and semantic structure.
Compare scan results across builds and display changes in issue counts.
Assign remediation owners and record verification evidence.
Generate a release accessibility report with unresolved blockers and historical trends.
Include a page inventory, component-level issue map, release comparison view, and CSV export.
Do not treat automated scans as complete accessibility evaluations. Distinguish automated detections from manual testing results, preserve tool versions and scan conditions, and avoid claiming legal compliance based solely on a passing scan. Include sample reports and tests for issue deduplication and regression classification.
0 Comments