Product Decisions This Supports
- Accessibility compliance as a roadmap workstream. The addon turns an abstract obligation (WCAG / EAA / Section 508 document accessibility) into a tracked, filterable finding queue with a severity model, giving you the evidence base to schedule remediation work rather than argue about it.
- Prioritising the remediation backlog. With v1.4.0 the queue paginates beyond the first fifty findings, so a library with hundreds of untagged PDFs is now fully enumerable. Filters persist across pages, which means a team can own a slice (e.g. "all critical, untagged PDFs in the Policies collection") and work it to zero — a prerequisite for any real burndown plan.
- Executive and stakeholder reporting. The new Documents band on the Site Weather tile converts the dashboard's numbers into a single status word — clear, fair, overcast, rain, storm — with unknown used when nothing has been checked or the addon isn't configured. This is the difference between "we have a scan report" and "here is our document accessibility health on the same board leadership already watches." The deliberate refusal to show clear on unconfigured or unrun state is a genuine product decision worth citing: it prevents false assurance in a governance context.
- Build vs buy evaluation. A free, in-control-panel checker reduces the case for a per-seat third-party scanning subscription, at least for the "do we know what's broken?" stage. It does not replace remediation tooling (tagging, OCR, PDF repair), so the realistic decision is buy remediation, adopt this for detection and tracking.
- Content governance and publishing gates. Findings live in the CMS where editors work, not in a separate portal. That supports decisions like "block release of the annual report until document findings clear," or assigning findings to the owning author.
- Vendor and dependency risk review. The Site Weather band is an optional soft integration: suggested, not required, and without it nothing changes. Worth noting as a decision about how much of your control-panel surface depends on sibling addons by the same author.
- Upgrade planning. "Upgrading re-checks nothing" means no reindex cost, no queue invalidation, no surprise backlog churn — a low-friction upgrade that can ride a routine maintenance window.
When to Consider This Package
Consider adopting when:
- You run a Statamic site (this is Statamic, not standalone Laravel — the Laravel relevance is indirect) with a document library of meaningful size: PDFs, policy papers, reports, prospectuses, syllabi, tender packs.
- You operate in a regulated or scrutinised context — public sector, education, financial services, healthcare, or any organisation with a published accessibility statement to defend.
- You need cheap, continuous detection rather than an annual external audit, and you want the findings inside the tool editors already log into.
- You want a single-glance health signal for non-specialist stakeholders, which the Weather band now provides — and you already use, or are willing to add, the free Site Weather addon for it.
- Your finding volume exceeds fifty items, which the pagination in v1.4.0 now accommodates properly.
Look elsewhere when:
- You are not on Statamic, or your content is largely HTML rather than downloadable documents — page-level accessibility scanning is a different problem.
- You need actual remediation, not detection: PDF tagging, alt-text authoring at scale, OCR, or converting scanned documents. This queue tells you what is wrong; it does not fix it.
- You require certified or contractually defensible audits, VPAT/ACR generation, or legal-grade reporting.
- You need multi-site, multi-brand enterprise reporting with SSO, role hierarchies, and API-level exports to a GRC platform — this is a focused addon, and its scope is deliberately the control panel.
- You have no appetite for a second addon dependency even optionally; though note the Weather band degrades cleanly to nothing.
How to Pitch It (Stakeholders)
For executives: We have a free addon that continuously checks every document in our library for accessibility problems and reports it in a single word on a dashboard leadership already reads — clear, fair, overcast, rain, storm. It stays at unknown until checks are actually run, so it will never tell us we are fine when we haven't looked. This gives us an early-warning system for a compliance area where most organisations only find out during an audit or a complaint, and it costs nothing beyond the time to fix what it finds. The latest release also removes the practical ceiling on how many findings we can work through.
For engineering: Additive release, no migrations, no breaking changes, and upgrading triggers no re-scan — nothing recomputes, so it is safe to ship in a routine deploy. The queue now uses Statamic's native pagination with filter state preserved, so large libraries are navigable without custom work on our side. The new Weather band is an optional integration with the free Site Weather addon and is fully inert if absent or unconfigured. The release also fixes accessibility defects in the addon's own UI — table header rows and visible filter labels — which matters both for screen-reader users and for the credibility of a tool that audits other people's accessibility.
For content and compliance teams: Findings are attributed and filterable, so you can own a subset of the backlog and page through it to completion rather than refreshing a single screen of fifty. Labels on filters and proper table headers make the queue practical to operate with assistive technology, and the dashboard is now named consistently with its nav item, which sounds cosmetic but reduces mis-navigation in a panel with many similar screens.