VPAT 2.5 · Section 508 · WCAG 2.1

A Drupal Accessibility Statement Generator That Tracks What You Actually Fixed

Most accessibility statement pages are a paragraph written once and never updated, published alongside a site that has drifted further out of compliance every month since. Accessibility Statement & VPAT Generator drafts the page as a Drupal node, then keeps a running conformance record so the statement stays honest.

Procurement Offices and Advocacy Groups Both Read Your Accessibility Statement Closely.

A generic accessibility statement copied from a template, with no update date and no specific conformance claim, is a visible signal that accessibility is not actively managed. A statement backed by a documented WCAG 2.1 AA self-assessment and a visible last-reviewed date reads very differently to a procurement officer or a DOJ complaint reviewer.

This module installs on any Drupal 10.6+ or Drupal 11 site with Composer, and pairs with WPPersona's WCAG 2.1 AA compliance approach. No CMS migration required.

VPAT 2.5

current edition of the Voluntary Product Accessibility Template used in government procurement

Accessibility Features

What Accessibility Statement & VPAT Generator Actually Checks

Every feature below maps to a specific WCAG 2.1 success criterion, not a vague accessibility claim. Here's exactly what changes on your Drupal site.

W3C Accessibility Statement guidance

Guided statement drafting

A step-by-step builder generates a complete accessibility statement node covering conformance status, known limitations, and contact information for reporting issues, following W3C’s recommended structure.

WCAG 2.1 AA

Ongoing conformance tracking

Pulls in scan history from Alt Text Manager, Contrast & Color Checker, PDF Accessibility Remediator, and other WPPersona modules to keep the statement’s claim backed by current data, not a one-time assertion.

Section 508 / WCAG 2.1 / EN 301 549

VPAT 2.5 export

Generates a VPAT 2.5 document mapping current conformance against Section 508, WCAG 2.1, and EN 301 549 criteria, ready for procurement office review.

W3C Accessibility Statement guidance

Issue reporting workflow

Adds a working accessibility feedback Webform connected to your team’s inbox, so residents reporting a barrier get a documented response instead of a dead-end address.

W3C Accessibility Statement guidance

Automatic review reminders

Schedules a recurring reminder on cron to review and republish the statement, since a stale statement with no review date undermines the credibility of the claim itself.

How It Works

From composer require to Fixed, in Four Steps

01

Answer the guided questionnaire

Provide your conformance target, known limitations, and feedback contact, and the module drafts a complete statement node in your site’s voice.

02

Connect your scan data

Link results from any other WPPersona modules already active on the site, so the statement reflects actual, current findings.

03

Publish and export your VPAT

Publish the statement node and generate a VPAT 2.5 for your procurement office or an incoming vendor security review.

04

Review on a set schedule

Get reminded to re-review the statement and conformance data on a recurring basis, keeping the public claim current.

“Our old accessibility statement was three sentences from 2019. The VPAT export alone saved our IT director two weeks during a state procurement review.”

Compliance Officer, State University System

Common Questions About Accessibility Statement & VPAT Generator

What is a VPAT and who actually asks for one?

A Voluntary Product Accessibility Template documents how a product conforms to standards like WCAG 2.1 and Section 508. Procurement offices at government agencies and universities request one before approving a vendor or, in this case, before another agency reviews your own site’s conformance during an audit.

Is publishing an accessibility statement legally required?

Requirements vary by jurisdiction and sector, but the DOJ ADA Title II rule and Section 508 program guidance both point toward publishing one as a documented, good-faith conformance practice. It does not replace fixing actual issues, but it demonstrates active management of them.

Can I write my own statement instead of using the builder?

Yes. The module accepts a manually written statement node if you prefer, while still providing the ongoing conformance tracking, review reminders, and VPAT export on top of it.

Get Started

Get Accessibility Statement & VPAT Generator on Your Drupal Site

There's no self-serve checkout yet. Submit the form and our team confirms your license tier, sends pricing, and gives you private Composer repository access with installation instructions within 1 business day.

  • Drupal 10.6+ or Drupal 11, PHP 8.1+, integrates with other WPPersona accessibility modules and Webform
  • License covers updates and support for 12 months

Need more than one? See the full Accessibility Suite bundle.

Request to Purchase

Tell us which modules you need. We'll send licensing and setup details.

Modules You're Interested In

License Size

We respond within 1 business day · No spam, ever

Free Tool

See Your Agency's PDF Risk in 2 Minutes

Enter your government website URL. We crawl every page, scan every PDF, and deliver a full ADA compliance risk report. No account. No credit card.

Run Free Audit

Talk to Someone Who Speaks Government

Our team understands government procurement, ADA compliance timelines, and what it takes to migrate a government website. Free 20-minute demo. No hard sell.

  • Full platform walkthrough for your agency type
  • Answers to procurement and security questions
  • Honest timeline and migration assessment
Schedule a Free Demo