RFP support
Make accessibility measurable in your RFP response.
A practical mapping of common accessibility requirements in public-sector RFPs to how Parity supports them. Use the language directly in your proposal or adapt it to your team's context.
RFP requirement → how Parity supports it
| RFP requirement | How Parity supports it |
|---|---|
| Provide automated accessibility testing across all public-facing pages | Schedule WCAG 2.1 AA crawls via axe-core. Crawl scope is configurable; results dedupe across pages into fix surfaces. |
| Detect accessibility issues on PDF documents the site publishes | PDF discovery during crawl + structural heuristics (tagged-PDF, document language, image-alt indicators). Discovery + triage, not PDF/UA validation. |
| Track remediation status across releases | Fix-surface workflow: open → in-progress → fix-applied → ready-for-rescan → completed. Verification runs validate fixes stick. |
| Detect regressions when content or templates change | Per-scan diff: new, unchanged, regressed, fixed. Configurable email alerts when regressions cross a threshold. |
| Produce audit-ready accessibility reports | PDF compliance exports, CSV finding exports, and VPAT/conformance matrix exports with WCAG references and severity breakdowns. |
| Document evidence of testing for procurement and legal review | Every export carries an org-configured disclaimer. Reports include the scan scope, date, and finding-by-finding evidence. |
| Provide role-based access for contractor and agency-staff users | Six built-in roles (Agency Admin, Client Admin, Editor, Developer, Content Manager, Viewer). Cross-org access for contractors who serve multiple clients. |
| Integrate with the agency's CMS for content-aware scanning | Native integrations with Ibexa, WordPress, and Drupal: URL-level publish/update/delete events trigger scans. |
Downloadable: accessibility appendix language
We maintain a one-pager you can drop into the accessibility section of an RFP response. It includes Parity capabilities, the disclaimer language we use ourselves, and references to ADA Title II and WCAG 2.1 AA.
One-pager preparing for publish — request directly while it's in review.
Get RFP languageWorking an active RFP?
Tell us the deadline and procurement vehicle and we'll respond with what you need within one business day.
Talk to our team about your RFP