Attachment_F_AccessibilityTG.docx
DOCX document 50 KB Posted
- Attached to
- MNIT/AELSBOA RFP ITN Licensure Compliance System
- Solicitation number
- 2000018382
- Issued by
- Ramsey County, Minnesota
About this file
This is an Accessibility Requirements attachment for a Minnesota Department of Information Technology Services (MNIT) request for proposal in partnership with the Minnesota Board of Architecture, Engineering, Land Surveying, Landscape Architecture, Geoscience and Interior Design (AELS) and the Board of Accountancy (BOA) for a cloud-based licensing and compliance system. The attachment outlines mandatory accessibility compliance requirements that all vendor responses must address. Vendors are required to demonstrate their organization's ability to ensure the State fulfills its accessibility responsibilities in accordance with the State of Minnesota Digital Accessibility Standard, which comprises Section 508 and WCAG 2.1 Levels A and AA. The document does not specify response dates, due dates, site visits, bidder meetings, award dates, or contract terms; rather, it functions as a set of evaluation criteria and compliance standards that vendors must address as part of their proposal submissions.
The accessibility requirements document does not contain pricing terms, set-asides, incumbent information, funding details, or contract value information. Instead, it establishes eight specific response requirements for vendors, including documentation of accessibility integration in business processes, staff knowledge and skills, development and testing approaches, tools and test results, corrective action processes, alternate service methods for non-compliant products, examples of accessible digital products, and completion of a VPAT 2.5 INT (November 2023) form covering Section 508 and WCAG 2.1 A and AA standards for all proposed software, hardware, and websites. These responses may be scored as part of the solicitation evaluation process.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 4.3.2026_ptsamplecontractsandexhibits.pdf | ||
| Attachment_A_and_B.pdf | ||
| AELS_BOA_LCS.RFP_Final_5.19.26.pdf | ||
| Attachment_D.pdf | ||
| rfpaddendum2_7.2.26.pdf | ||
| Attachment_E_FunctionalReq_SelfAssess3.13.26.xlsx | XLSX spreadsheet | |
| Attachment_C_Cost_Detail_4-15-25.docx | DOCX document | |
| rfpaddendum3_-_Clean.pdf | ||
| MNIT_AELSBOA_RFP_ITN_Licensure_Compliance_System.pdf | ||
| rfpaddendum1.pdf | ||
| rfpaddendum4_-_Clean.pdf | ||
| Replaced_Attachment_C_Cost_Detail_7.6.26_LCS.docx | DOCX document |
Show all 12
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment F – Accessibility
The State of Minnesota requires all information and communication technology (ICT) to conform to the State of Minnesota Digital Accessibility Standard, which comprises Section 508 and WCAG 2.1, A and AA. Please respond to the questions below. Responses should detail your organization’s ability to ensure the State fulfills its accessibility responsibilities as outlined in the standard. Suppose you cannot answer a question; state why. Please identify the document(s) in the responses below if attaching supporting documentation.
1. Describe or provide documentation on how your organization includes digital accessibility in crucial business processes. (Examples are product development, procurement, HR, etc.).
2. Describe how you ensure your staff and contractors have the knowledge and skills to create accessible digital technology within the scope of the project or services requested within this RFP.
3. Describe your approach to ensuring accessibility for your solution (e.g., strategy, tools, design, testing, ongoing validation).
a. Include if/how you incorporate accessibility into your development process (e.g., requirements, design, development, testing, maintenance, bug prioritization).
b. Include how you ensure accessibility post-implementation (e.g., future enhancements.
4. Describe your organization's development and test tools to produce accessible digital technology offerings. Provide examples of typical project test cases for accessibility and samples of your organization’s documents test results.
5. Describe your organization’s corrective actions process(es) or system(s) for documenting, tracking, and resolving accessibility issues/defects.
6. Describe alternate methods for digital products or services that do not support the State of MN accessibility standard. (example: 24 hour/7 day/week toll-free phone support number).
7. Provide links to websites, copies of documents, or access to other samples of digital information technology your organization has developed that meet accessibility standards. The materials should be relevant to the services and technical skills called for in this solicitation.
8. Include, in an accessible format, a VPAT® 2.5 INT (November 2023) for all software, hardware, and websites (as applicable) as proposed in response to the solicitation. Vendors can use the VPAT form from the ITIC VPAT site. Vendors should complete the Section 508 and WCAG 2.1 A and AA sections. The EN 301 549 section can be left blank or deleted. For systems with multiple interfaces (such as an admin and user interface), report on each interface whether in the same or separate VPATs. These documents may be scored according to the solicitation evaluation..
| Document Name | 1 |
| Accessibility | 1 |
File details come from the government source that posted it. Updated .