The vendor is required to provide web accessibility scanning tools that can:
• Provide detailed, accurate accessibility scans across diverse web properties.
• Integrate effectively within each campus’s web infrastructure.
• Offer robust reporting and remediation guidance to meet accessibility standards.
• Support centralized and campus-specific oversight for accessibility improvement.
- Functional requirements
1. Automated scanning
• Perform automated scans on demand, at scheduled intervals, or continuously.
• Support scanning of a wide range of web content, including static pages, dynamic content, multimedia, pdfs, and other embedded files.
2. Customizable reporting and dashboarding
• Provide comprehensive reporting for individual campuses and the ability to review all campus reports with a single user admin role.
• Allow customization of reports to reflect different accessibility metrics and priorities.
• Support role-based access for different levels of users across campuses and the co.
3. Remediation support
• Offer clear, actionable guidance on fixing identified issues, with links to best practices or examples.
• Track progress on issue resolution over time.
• Provide guidance and context on how the tool’s automated scanning results serve as one part of a
thorough manual evaluation.
• Recommend manual evaluation for content types that cannot be reviewed with an automated scanner.
4. Integration capabilities
• Integrate with popular content management systems (e.g., Drupal).
• Offer APIs or other tools to integrate with other university platforms or workflows.
5. Scalability and performance
• Support the volume of web properties and user access requirements across the university system.
• Efficiently handle simultaneous scans without compromising performance.
- Implementation timeline
• Provide a comprehensive, detailed timeline for implementing the system across all 23 university campuses and the chancellor’s office—from initial setup and user training through the entire system operation.
• The timeline should outline phases, from project initiation and onboarding to system usage and complete integration.
- Licensing and cost structure
• Information on the included or additional cost of 24 instances of your tool with SSO (systemwide) to cover all institutions.
• The number and limit of pages included.
• The number and limit of users included.
• Provide general information on cost structure, including initial implementation costs, annual fees, and potential discounts for systemwide usage.
• Also, provide the cost for specific campuses to add additional services, support, or features over and above the product's core functionality.
- Contract Period/Term: 3 years
- Questions/Inquires Deadline: May 09, 2025