Paperfort Editorial
Who writes Paperfort's accessibility guides, and how we keep them accurate.
Paperfort Editorial is the team that writes and maintains the guides, blog posts, and reference pages on this site. The writing is plain on purpose. A Shopify merchant who just opened a demand letter does not need jargon; they need to know what the documents are and what to do next.
How we write these guides
Every guide rests on three things. The first is axe-core, the open-source WCAG engine Paperfort runs, which also sits inside the automated testing tools at Microsoft, Google, and Deque. The second is the W3C Web Accessibility Initiative's published success criteria for WCAG 2.2. The third is primary sources we link to directly: the FTC's January 2025 order on the accessibility-overlay category, the ITI VPAT 2.5Rev specification, and the annual Seyfarth Shaw and UsableNet litigation surveys. We check claims against those sources before a page goes live, and we date each post so you can judge how current it is.
What we are, and what we are not
Paperfort is automated-only. We are not certified accessibility professionals, and we make no CPACC or IAAP claim. An automated scan catches only a portion of WCAG issues (industry estimates put it at roughly a third to half), so our guides say where a manual review is still needed rather than pretend a scan is the whole job. Paperfort produces documentation and a prioritized remediation plan. It is not legal advice, it is not a law firm, and nothing here guarantees compliance or prevents a lawsuit.