Government CMS Buyer's Guide: Evaluating Platforms for ADA Compliance
Ten questions your RFP should ask before it goes out. A VPAT reading guide that catches the tricks. A feature matrix built from real vendor demos. And a cost model that shows what the license fee hides.
About This Guide
68 pages. Published July 2026 by Logan Nathan. Written for procurement officers, IT directors, and city managers picking a CMS with ADA Title II in mind. You'll get RFP language templates, VPAT evaluation checklists, and platform comparison data.
Why Government CMS Procurement Gets Accessibility Wrong
Most RFPs treat accessibility as a checkbox. The vendor hands over a VPAT, claims WCAG 2.1 AA, and the procurement file moves on. Here's the catch. VPATs are self-reported. They're rarely validated. “WCAG 2.1 AA compliant” often means the theme templates pass while document publishing has no guardrails at all. And a platform that was compliant when the VPAT was signed may have drifted since the last release.
The agencies that end up with violations three years after signing a “WCAG-compliant CMS” usually made one of three mistakes. They took the VPAT at face value without testing it. They didn't look at how the platform behaves when a staff editor is publishing at 4:45 on a Friday. Or they left document accessibility out of the evaluation entirely.
This guide gives your procurement team sharper questions and a way to pressure-test vendor claims, so the platform you buy for compliance still delivers compliance in year three. Agencies that prefer a co-op procurement path can also acquire compliant CMS platforms through the Carahsoft government contract vehicle instead of running a full RFP.
The 10 Questions Every Government CMS RFP Must Ask
Q1.What is your current WCAG conformance level, and what is the date of your most recent third-party accessibility audit?
Why it matters: A self-reported VPAT is not an audit. Ask for the third-party report from an independent accessibility firm. If the vendor can't produce one, or the last audit was three years ago, you have your answer.
Q2.Does your platform scan PDF documents for accessibility compliance at the point of upload? Can you demonstrate this feature?
Why it matters: This is the single most important question if your archive has more than a few hundred documents. Most platforms don't scan. The ones that do often only warn, they don't block. Ask whether a non-compliant PDF can still be published anyway.
Q3.What happens when a content editor attempts to publish a page with a missing heading structure or skipped heading levels?
Why it matters: Platform-level enforcement of semantic structure is rare. Most CMSes let editors pick any heading level for visual styling. You want a platform that either blocks the publish or throws a hard warning your editor can't click past.
Q4.Is alt text required before an image can be published, or can editors skip it? What is the default behavior?
Why it matters: The default is what happens when a busy editor uploads 40 images before a council meeting. If alt text is optional, most of those images ship without it.
Q5.Do you have a published accessibility statement for your own platform? What known non-conformances does it disclose?
Why it matters: A vendor that doesn't publish an accessibility statement for their own product isn't serious about the topic. Ironically, a statement that lists real known issues is more trustworthy than one claiming perfect compliance.
Q6.How do you handle accessibility regressions introduced by platform updates? What is your testing process before a release?
Why it matters: Regressions from platform updates cause more ongoing compliance headaches than the original build. Ask about the pre-release testing process. Ask what remediation SLA the vendor commits to when a regression ships.
Q7.Can you provide references from three government agencies that have conducted a third-party WCAG 2.1 AA audit of their site on your platform? Will you give us permission to contact them?
Why it matters: Vendor-picked references are picked for a reason. References tied to an independent WCAG 2.1 AA audit give you verification you didn't have to trust.
Q8.Does your platform support multi-language content with properly set HTML lang attributes for each language? How is this implemented?
Why it matters: Many government platforms have translation features that quietly break the lang attribute. Screen readers then announce the translated page in the wrong pronunciation. Ask for a live demo, not a slide.
Q9.What accessibility training do you provide to content editors on our platform, and what documentation exists for ongoing reference?
Why it matters: Platform enforcement handles the structural stuff. Content quality still needs trained editors. What training and reference docs does the vendor keep current?
Q10.What contractual remediation commitment do you make if a third-party audit finds WCAG 2.1 AA violations attributable to the platform (not content)?
Why it matters: If the platform itself introduces failures, the contract should spell out the vendor's obligation to fix them. No clause means every dollar of remediation lands on your agency.
Platform Feature Comparison: CivicPlus vs. Granicus vs. WPPersona
Note: Feature information reflects Logan Nathan's research as of July 2026. Platforms change; confirm current capabilities with each vendor before you sign.
| Feature | CivicPlus | Granicus | WPPersona |
|---|---|---|---|
| WCAG 2.1 AA compliant templates | ✓ Theme level | ✓ Theme level | ✓ Full platform |
| PDF scan at upload (blocking) | ✗ | ✗ | ✓ |
| Alt text enforcement (required) | Optional | Optional | Required |
| Heading hierarchy enforcement | ✗ | ✗ | ✓ |
| Third-party accessibility audit (public) | VPAT only | VPAT only | ✓ Published |
| Multi-language (100+ languages) | ✗ | ✗ | ✓ |
| Real-time compliance dashboard | Partial | Partial | ✓ Full |
| Implementation timeline | 12 to 20 weeks | 12 to 20 weeks | 7 to 21 days |
| Pricing (mid-sized city) | $30K to $55K/yr | $30K to $55K/yr | $499 to $999/mo |
| Contract flexibility | 3-yr term typical | 3-yr term typical | Month-to-month |
| SOC 2 Type II | ✓ | ✓ | ✓ |
Annual license cost, mid-sized city (USD)
WPPersona 2 to 4x lower
Low and high ends of published vendor pricing bands. WPPersona monthly rates multiplied by 12.
Total Cost of Ownership Analysis
Most CMS decisions get made on the license fee. That's the smallest number in the file. The real cost of running a government website compliantly for three years lives in eight buckets, and the guide's TCO model walks through each one:
License / subscription fees
Annual platform cost including all users
Implementation cost
One-time cost to configure, migrate, and launch
Ongoing accessibility remediation
Staff time or vendor cost for fixing new violations as they surface
PDF remediation (historical archive)
Cost to fix existing non-compliant documents
Annual accessibility audit cost
Third-party WCAG audit that holds up if DOJ calls
Staff training cost
Yearly training for content editors and document creators
Opportunity cost of IT staff time
Platform maintenance hours your team could spend elsewhere
Compliance risk cost
Actuarial cost of a DOJ complaint and response, weighted by platform risk
The full guide ships with a spreadsheet TCO calculator. You get inputs for each category, pre-populated with typical numbers for three platform tiers (enterprise, mid-market, and Starter-level). Agencies that run the model usually find that the “cheaper” legacy platform ends up 2 to 4 times the true cost of a purpose-built compliant one, once you add the pieces the RFP never asked about.
Implementation timeline to launch (days)
7 to 21 vs 84 to 140
Get the Full Buyer's Guide
Book a 15-minute demo and we'll send you the full guide, the TCO calculator spreadsheet, and the RFP language template. No procurement forms required.
Schedule Demo to Get Access