Government website redesign RFP generator
Generate a city, county, or agency website redesign request for proposal (RFP) template with accessibility, security, performance, and AI-readiness requirements from ScanGov Standards.
About the RFP generator
Writing a website redesign request for proposal (RFP) means turning accessibility, security, performance, and search and AI readiness into requirements a vendor can be held to. This generator writes the ScanGov Standards into section 3 of a complete RFP, links every requirement to the standard that defines it, and adds contract terms so compliance is verified by checks, not promises. Nothing you enter is stored.
What the RFP requires
Section 3 of the generated RFP covers the five categories ScanGov scores, with each requirement linked to its standard and guidance:
- AI and search readiness: the site can be crawled and understood by search engines and AI assistants, with content in the HTML rather than only after JavaScript runs.
- Accessibility: WCAG 2.1 AA and all 66 ScanGov accessibility standards, from color contrast to touch target size.
- Security: HTTPS, HTTP Strict Transport Security (HSTS), a content security policy, security.txt, and the other headers the Cybersecurity and Infrastructure Security Agency (CISA) and the Open Worldwide Application Security Project (OWASP) recommend.
- Usability: Core Web Vitals thresholds, page titles and descriptions, mobile viewport, and social sharing tags.
- Readability: content written in plain language, scored by reading grade level on every page.
The rest of the document is a conventional RFP skeleton you can edit: background, functional requirements, content management system (CMS) and integrations, design, deliverables, timeline, proposal requirements, evaluation criteria, and contract terms.
Writing the policy behind the RFP? The digital experience policy generator writes the same standards into a policy.
Frequently asked questions
What does the Request for Proposal (RFP) generator include?
A complete website redesign request for proposal: executive summary, background, compliance requirements, functional and technical requirements, design, deliverables, timeline, proposal requirements, evaluation criteria, and contract terms. Section 3 writes the ScanGov Standards in as requirements across accessibility, botability, security, and usability, with a link to each standard so vendors know exactly what will be checked. Fill in your organization and contact details and the generator produces a document you can copy, print, or edit.
How do I verify that a vendor's website work is actually accessible before signing?
Ask for an Accessibility Conformance Report (ACR)—produced from the Voluntary Product Accessibility Template (VPAT)—for the platform, then test rather than trust it. Run the vendor's existing government sites through an automated scan and a manual check with a screen reader and keyboard. Every government site ScanGov has scanned has a public scorecard on scangov.org, so you can look up a vendor's current clients before you shortlist them. The General Services Administration's (GSA) Section 508 accessibility FAQ covers verification in more depth.
Should the RFP require a VPAT or ACR?
Yes, for any platform or product the vendor supplies. A VPAT is the template; the completed document is the ACR. Require a current ACR against the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, ask how old it is and which version of the product it covers, and treat "partially supports" entries as items the vendor must remediate or explain. GSA's ACR and VPAT FAQ explains what each document is and is not.
What contract language makes vendor-developed content meet WCAG 2.1 AA?
Require that all content, templates, and features delivered under the contract conform to WCAG 2.1 Level AA; that the vendor fixes failures found in acceptance testing before launch and failures found after launch within a set period; and that compliance is measured by an automated scan plus manual review, not by the vendor's own statement. The generator's contract terms section includes this. The Municipal Research and Services Center's (MRSC) guidance on the Americans with Disabilities Act (ADA) web rule for local governments recommends the same approach.
What if no vendor can promise full compliance?
Pick the most accessible option and write the gaps into the contract as remediation obligations with dates. The Department of Justice's rule allows for minor failures that do not affect access, but not for known barriers left unfixed. GSA's Section 508 FAQ addresses choosing between products when none is fully accessible, and the ADA Title II web rule fact sheet describes the minor-failure provision.
When does the ADA Title II web accessibility deadline apply?
April 26, 2027 for state and local governments serving 50,000 or more people, and April 26, 2028 for those under 50,000 and for all special district governments, under the Department of Justice's ADA Title II web rule. A redesign contracted now should be scoped to launch compliant before your deadline. Confirm the dates for your entity on ada.gov.
Indicators
Accessibility
Meet WCAG standards so every type of user can use your website.
Botability
Help AI and search engines discover, crawl, and index your website.
Readability
Write content at a reading level most users can understand.
Security
Secure your site and protect users with proper security practices.
Usability
Optimize content and design so users can quickly find what they need.
Features
Readability
Find the pages that are hard to read and set a reading level for your team.
News
New ScanGov readability scanner
Helping web managers evaluate content readability.
First Contentful Paint (FCP) + Largest Contentful Paint (LCP) demo
ScanGov demos how we conduct performance audits related to First Contentful Paint (FCP) and Largest Contentful Paint (LCP).
Time to First Byte (TTFB) demo
ScanGov demos how we conduct performance audits related to Time to First Byte.