Experimental project

This is a sandbox project, which contains experimental code for developer use only.

Extensible, network-able plugin platform for examining and reporting compliance posture across Drupal and WordPress sites.

A modular core plus pluggable extensions for running, recording, and reporting on conformance scans against Drupal and WordPress sites. Built for institutions and agencies that need defensible, sovereign, auditable evidence, not another vendor dashboard.

What this is

Note on the name: we use "conformance" deliberately. Conformance is a measurable, continuous, evidence-based posture; compliance is a legal determination. This platform produces conformance evidence that supports compliance assessment. The two words are not interchangeable.

conformance is a sandbox project under early development. The architecture is a small core plus a family of plugins:

  • Scan engines (pluggable). Local scanners (axe-core, pa11y, custom CMS-aware rule engines) and external API-driven partners. Run any combination, swap in or out, or run multiple in parallel.
  • Rule packs (pluggable). WCAG 2.1 Level AA is the first pack. The platform is designed to support additional regulatory and policy domains as packs.
  • Report renderers (pluggable). PDF for legal-quality evidence, JSON for archival and integration, additional formats as needed.
  • Workflow primitives. Scanning, finding, capturing remediation in tickets, collecting in an evidence archive, closing the loop with re-testing. Standard Drupal / WordPress entity patterns throughout.
  • Audit log. Defensible record of who scanned what, when, what was found, what was remediated, what evidence was produced.

The goal is one platform, two CMSes, many rule packs, customer's choice of engines.

Who this is for

Compliance officers and general counsel at institutions facing regulatory deadlines. HHS Section 504 (effective May 11, 2026 for HHS-funded entities). ADA Title II (effective April 26, 2027 for state and local government and public-university web content serving 50,000 or more people). The platform produces the kind of evidence that holds up in DOJ enforcement reviews and HHS Office for Civil Rights reviews: documented testing methodology, scan history, remediation tracking, exportable archive.

Accessibility coordinators and IT directors in higher education and public-sector organizations who need a workflow that fits an existing Drupal or WordPress stack without a new vendor relationship. Customer-owned data, customer-controlled infrastructure, no required cloud dependency.

Agencies and consultancies serving regulated verticals (healthcare, government, higher education, member associations) who want a contrib platform they can extend with vertical-specific rule packs rather than build from scratch or compete against commercial vendors.

On AI

The regulatory frame around accessibility is converging with the regulatory frame around AI. Institutions and agencies need workflows that address both, with no vendor lock-in to either.

conformance includes optional AI-assisted remediation guidance for findings that benefit from generative help (drafting alt text, evaluating language clarity, suggesting reading-level adjustments). The AI integration is sovereign by design:

  • Local LLM (run on your own hardware via Ollama, LM Studio, llama.cpp, vLLM, or any OpenAI-compatible local endpoint).
  • Bring-your-own API key (OpenAI, Anthropic, Azure OpenAI, Google AI). Your contract, your data flow.
  • Or no AI at all. The rule-based platform works fully without it.

Positioned alongside the Drupal AI Initiative, not against it. The Initiative's roadmap focuses on AI capabilities (page generation, context management, content creation, governance, design system integration). conformance focuses on the regulatory-conformance work that sits over those capabilities. The two are complementary; we expect to contribute reusable primitives upstream where appropriate.

Status

Sandbox / early development. The architecture is taking shape; the first scan engine and rule pack are in active build. WordPress parity is on the same roadmap, not a port-later.

Working with regulated-vertical Drupal or WordPress sites and want to compare notes?

Reach the team at conformance@success.build. This is a peer-to-peer reach-out, not a sales funnel, not a demo request flow. Topics worth discussing: what your current accessibility-conformance posture looks like, what you have built or considered, where the gaps are that you see from your seat, whether the platform being prototyped here would help.

License

GPL-2.0-or-later.

Maintainer

Sterling Solutions LLC, steward of success.build.

Supporting organizations: 
Sterling Solutions LLC
Leads project architecture and development, and provides ongoing maintenance. Sterling Solutions is also the steward of the conformance.success.build content network and the related accessibility/compliance services practice that support project users.

Project information