Once you determine the Section 508 accessibility requirements that apply to your procurement, the next step is to create solicitation language. A well written solicitation goes a long way toward ensuring agency Section 508 compliance and accessible ICT. Standard language is not an option. Review basic guidance on "Solicitation Do and Don't" to document solicitations in compliance with Section 508.
Tools, Guidance, and Resources
Check out the Quick Links to get pre-packaged Solicitation Language for a number of standard ICT deliverables. Choose your deliverable and Quick-Links will generate
- Solicitation language that includes Program Need, Deliverable Requirements, Evaluation and Acceptance Factors related to Section 508.
- Government Product Accessibility Template (GPAT) which identifies the applicable Section 508 provisions.
The solicitation language (above) requires vendors to fill out the GPAT to let you know how well their product and service meets these requirements.
If your deliverable is not listed in Quick Links, you can use the BuyAccessible Wizard to generate solicitation language for your ICT deliverable by going through a wizard session.
BuyAccessible Wizard can be used to generate solicitation language for your ICT deliverable by going through a wizard session.
Solicitation Do and Don't
Shows the criteria used by the GSA Section 508 team to review FedBizOpps solicitations: things to do and things to avoid.
Guidance on Creating 508 Compliant IT Solicitations
Understand the responsibilities and the appropriate content required for effective and compliant ICT solicitation documentation.
Review Solicitation Assessment Data
Find out more about GSA review of FebBizOpps solicitations.
Evaluation Scenarios for Solicitations
Learn about the criteria for evaluating how well ICT solicitations include appropriate Section 508 language, and typical patterns (scenarios) observed when reviewing solicitations using the criteria.
Section 508 blog
Real life examples: