Draft accessibility requirements for tenders
Version 1.0, published 28 February 2022.
These are offered for use in Defra when writing requirements for a tender. They have been used as part of a tender but have not yet been used more widely.
Table of requirements
Download table of requirements as an Excel file
| Type | Requirement | MoSCoW | Guidance notes |
|---|---|---|---|
| Functional | The solution must conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at double A level without use of any plugins or overlays. | Must | Making the overall solution accessible means making sure all aspects can be used by as many people as possible within the core solution, and not through the use of additional plug-ins or overlays. This includes, but is not restricted to, those with: impaired vision; motor difficulties; cognitive impairments or learning disabilities; deafness or impaired hearing. This applies to all users of the system. Reference: Web Content Accessibility Guidelines (WCAG) 2.1 URL: https://www.w3.org/TR/WCAG21/ For guidance it is noted that we are required to conform with accessibility requirements for public sector bodies (GOV.UK) URL: https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps |
| Non-Functional | The supplier should provide evidence that an accessibility audit was undertaken by an independent third party to assure conformance to the required WCAG level. | Should | A 'third party' will mean a party independent of the supplier, who has included participation by people who are disabled, against a comparable installed and configured solution, not a base version. In the case of non-compliance, please state who, if anybody, has undertaken an audit to assure accessibility conformance. Reference: Website Accessibility Conformance Evaluation Methodology (WCAG-EM) 1.0 URL: https://www.w3.org/TR/WCAG-EM/ |
| Functional | The solution must be compatible and work with the listed assistive technologies mandated by GDS and used across the Defra Group. | Must | These are the assistive technologies currently used across the Defra Group and / or mandated by the Government Central Digital and Data Office:
|
| Non-Functional | The solution could be compatible with Microsoft Office 365 Productivity Tools. | Could | Microsoft Office 365 Productivity Tools include:
|
| Non-Functional | The supplier should have methods that assure accessibility standards are maintained for currency, against WCAG-2.1 throughout the lifecycle of the solution. | Should | This should include a method for assuring that updates or future solution developments, including those initiated from / with Defra maintain accessibility to the WCAG standard. |
| Non-Functional | Where applicable, conform to Government Digital Service Standards and the Technology Code of Practice. | Should | References: Government Service Standard URL: https://www.gov.uk/service-manual/service-standard The government technology code of practice URL: https://www.gov.uk/guidance/the-technology-code-of-practice |
| Non-Functional | It should take an assistive technology user no more than 200% of the time taken by a user not using assistive technology. | Should | EXPERIMENTAL: The aim of this requirement is to avoid a system being technically accessible (conforms to the letter of WCAG) but in reality there is no way a user could actually use it for their role because it would take them too long to actually perform the task. The 200% is a guess and should be validated. |
| Non-Functional | The solution should be compliant with ISO 9241-171:2008 Ergonomics of human-system interaction — Part 171: Guidance on software accessibility | Should | EXPERIMENTAL: reference URL is https://www.iso.org/standard/39080.html |