There are numerous documents in the process of ICT procurement. These include, but are not limited to:
Each of these is an opportunity to ensure that the requirement for digital accessibility is captured and progressed.
An institution's ICT Risk Register is also an opportunity to ensure that digital accessibility is given due consideration and that accountability for accessibility shortfalls is maintained.
What follows are snippets of text based on examples of what other organisations have used in their procurement processes. They are organised according to the stages of the procurement process. They should be seen as a "Clause Bank" from which procurement teams can draw and tailor to their own needs. They are options to be considered, not a definitive statement that they are the most appropriate in any given situation.
In any case, any document which has legal or commercial implications for your organisation should always be checked with a legal professional.
There are also suggested clauses for inclusion in risk registers and for generic procurement policies.
This document should be read in conjunction with others in this guide, in particular Waypoints in Accessible Procurement.
Some organisations write dedicated policies which describe accessible procurement requirements. These are used in addition to the main procurement policy they operate. This is an excellent strategy, and we have included links to model policies which we know work well in other organisations around the world in the Resources document in this Guide. A dedicated accessible procurement policy allows the institution to go into more detail as to what it means and expects in the procurement of ICT products and services.
However, it is also a good idea to ensure that accessibility requirements are included in the main procurement policy, albeit by necessity in less detail than a document in its own right.
This sends a clear message about the importance your institution places on accessibility: a message no vendor would be wise to ignore.
Suitable text might include:
"This institution is committed to ensuring all persons with disability have access on an equal basis to all equipment, services, websites and other written information. In order to achieve this, all Information and Communication Technologies (ICTs) provided by and maintained by, or on behalf of the institution or used by its students and staff must be accessible to and usable by persons with disability. Such requirements must be explicitly referenced in the tendering process."
"Where a preparatory study, testing or demonstration is conducted prior to or during a procurement exercise, it shall include accessibility laid down in recognised standards such as AS EN 301 549 or the Web Content Accessibility Guidelines (WCAG). The business need the procurement is intended to meet and the needs of all potential end users, including in particular end users with disability should be considered."
"The procurement team shall ensure that vendors demonstrate their conformance with accessibility standards or, where relevant, their capability to deliver accessible ICT products or services."
An RFI/RFP/RFQ is a detailed document which provides plenty of opportunities to send a clear message to prospective vendors that you expect them to offer a product which meets your digital accessibility requirements. This section contains sample snippets of text which can be used and which range from a brief passing reference to more detailed statements. We have also included a list of questions which you may wish to ask in your tender document.
Note: the Commonwealth Procurement Rules are actually designed for Government, but they do provide an excellent baseline for other sectors (see Appendix 1 – Commonwealth Procurement Rules).
"The Respondent warrants that the information technology offered under this proposal
is available, whenever possible, without modification for compatibility with software and hardware which provides accessibility functionality for use by people with disability."
By submitting a Proposal, the vendor warrants that:
(i) Web-based ICT products included in the Proposal shall conform to Web Content Accessibility Guidelines ("WCAG") 2.1 AA
(ii) non-web-based ICT products included in this Proposal shall meet or exceed the applicable accessibility requirements of Australian Standard AS EN 301 549.
If successful in its proposal, the vendor agrees to provide evidence of compliance with these requirements before an Agreement becomes effective and at any other time upon reasonable request of the university."
Asking the right questions of a prospective vendor is critical if you are going to determine their ability to meet accessibility requirements. There is a separate list of questions elsewhere in this guide (see document titled " Accessibility Procurement Questions") you might consider asking in your RFI/RFP/RFQ documents. It should be noted that they are designed for you to pick and choose the ones which work best in your circumstances – you would not use every one of them at one time, rather you would use combinations of them to get the optimum result. Some of the questions therefore seek the same information but in different ways.
Beware of promises not kept or over-optimistic commitments by potential vendors, or of a complete absence of a response to your accessibility criteria.
RFPs should contain a clause which deals with the consequences or penalties if the solution is not accessible. to ensure the request for accessibility is taken seriously, consequences must be defined and should be significant enough so RFP respondents pay appropriate attention to the accessibility criteria. The penalty may be to withhold part of the payment until accessibility requirements have been satisfied. In is important to stress that this juncture that in no way does this constitute legal advice or specific guidance with respect to what you can or should do with respect to the law – these are simply suggestions based on practices in organisations around the world.
Examples would be:
Note : The author of the RFP should adjust the penalties or fines as needed, or alternatively, they could be prescribed in the institution's procurement policy or similar appropriate location.
If a penalties clause is in place, it will be important to have a clearly understood means of determining whether or not the vendor has failed to meet its obligations, so thought must be given to the process of evaluating vendors' claims.
This is another reason for vendors to supply an up-to-date Accessibility Conformance Report (ACR) for the product in question. Typically, an ACR can be produced based on the Voluntary Product Accessibility Template (VPAT), one version of which has been prepared with the requirements of AS EN 301 549 in mind. Some examples of language for conformance are:
The following text could be included in the tender document.
"Within x days of the Effective Date of the Agreement, Vendor shall complete and return an Accessibility Roadmap document which addresses all accessibility gaps.
The roadmap will identify gaps, describe the timelines by which these accessibility gaps will be remediated, as well as recommendations regarding interim workarounds. If the product has been the subject of a VPAT or ACR, any criteria which was not fully met should be included in the template. The vendor will provide revised Accessibility Roadmaps whenever revised VPATs are submitted."
The following text would be useful in a final contract between your institution and the successful vendor. Note how the first part echoes one of the proposed wordings in the RFP/RFQ section.
If the vendor has supplied a roadmap to make good accessibility shortfalls earlier in the procurement process, use the timings in that roadmap in the contract.
7.26 For procurements valued at or above the relevant procurement threshold, where applying a standard for goods or services, relevant entities must make reasonable enquiries to determine compliance with that standard, including:
a) gathering evidence of relevant certifications; and
b) periodic auditing of compliance by an independent assessor.
10.10 In prescribing specifications for goods and services, a relevant entity must, where appropriate:
a) set out the specifications in terms of performance and functional requirements; and
b) base technical specifications on international standards, when they exist and apply to the relevant procurement, except when the use of international standards would fail to meet the relevant entity's requirements.
10.11 Where an Australian standard is applicable for goods or services being procured, tender responses must demonstrate the capability to meet the Australian standard, and contracts must contain evidence of the applicable standards (see paragraph 7.26).
Please note: We view this as a living resource and welcome feedback. We are improving our website to ensure this content is fully accessible for all users. There is also a fully accessible version of the content available on the ADCET website. We welcome feedback about the content and its accessibility as part of our ongoing process for improvement — email: firstname.lastname@example.org.
CAUDIT acknowledges the Traditional Owners of the lands where we live, learn and work. We pay our respects to Elders past and present and celebrate the stories, culture and traditions of all First Nations people.