Procurement Examples
- Do you have an up-to-date accessibility statement relating to the platform?
- Describe your Accessibility testing process?
- What is your release schedule for future accessibility features?
- Are you compliant with WCAG 2.1 AA and do you have the documentation to support this?
- If you are not compliant, are you aware of the accessibility issues you have and what is your roadmap to fixing them?
- Have you considered not only the accessibility of your front facing product but the accessibility of the back-end UI that staff will use?
- Has any testing of this product been completed with screen readers or other assistive technology?
- Have you done any user testing with people who have additional access needs?
- Which assistive technologies do you work with?
- Does your service support WCAG 2.1 for content creation?
- How do users find information about the accessibility of your service?
Example Criteria for Tenders
- Provide details of how the system supports content creation that is compliant with WCAG 2.1 AA standards and The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
- Provide details of how the back-end user interface is compliant with WCAG 2.1 AA standards and The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
- Provide details of how the user interface of the system is compatible with assistive technology.
- Provide details of the automated testing available with the system that is used for identifying accessibility issues in the content produced, e.g., missing alt text.
- Provide details of how accessibility standards are embedded within your working practices
- Provide details of your ongoing support and development of the product in terms of its accessibility.
- Provide details of how you will ensure that the website (or web-based system) is compliant with WCAG 2.1 AA standards and The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
- Provide details of how you will ensure that back-end user interface is compliant with WCAG 2.1 AA standards and The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
- Provide evidence of experience of building accessible websites (or web-based systems) in line with the WCAG 2.1 AA Standards and best practices.
- Provide a detailed overview of how you carry out ongoing accessibility testing.
- Provide details of how accessibility standards are embedded within your working practices.
- Provide details of how the website (or web-based system) is compatible with assistive technology.
- Provide details of how the system’s front-end user interface is compliant with WCAG 2.1 AA standards and The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
- Provide details of how the back-end user interface is compliant with WCAG 2.1 AA standards and The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
- Location of accessibility statement for this product.
- Provide details of your ongoing support and development of the product in terms of its accessibility.
- Provide details of how accessibility standards are embedded within your working practices.
- Provide details of how the system is compatible with assistive technology.