A11yPDF
Validate PDF accessibility remediation with PAC in one click
- Problem
- Teams and freelancers must deliver accessible PDFs (WCAG, PDF/UA), but after remediation they have no easy way to prove it actually passes. A recent Show HN for a PDF remediation tool emphasized that you can 'verify the improved score with PAC before and after' — meaning verification itself is a distinct, painful step. Today it's manual: open PAC, inspect every failure one by one.
- Solution
- A local-first CLI/desktop tool that runs PAC against a PDF, produces a before/after diff report (score, failing checks, fix hints), and supports batch processing plus CI integration with an exportable compliance artifact.
- Users
- Government contractors, universities, freelance accessibility consultants, and documentation teams who must ship compliant PDFs
- MVP
- Wrapper around PAC CLI for single-PDF checks; before/after HTML comparison report; batch folder scan; GitHub Action / CI template; one-click export of compliance evidence
- Revenue
- Per-seat subscription for consultants/teams, or pay-per-validation API; open-source core with paid CI integration
- Why now
- Accessibility regulations (European Accessibility Act, US Section 508) are becoming mandatory, yet the validation toolchain is still fragmented. A solo dev can wrap PAC's free engine into a polished workflow without competing head-on with Adobe.