Accessibility Requirements for ICT Procurement

This template provides a structured format for embedding accessibility requirements into procurement documentation, such as RFx and tender documents that aligns with Australian Government practice, WCAG and AS EN 301549, while remaining supplier-friendly and enforceable.

1. Scope of Accessibility Requirements

The supplier must ensure that all ICT products, services, and deliverables provided under this contract meet the accessibility requirements defined in this section. Requirements apply to:

Software (web, mobile, desktop, SaaS)
Hardware and ICT equipment
Digital documents, training materials, and support content
User interfaces, APIs, and integrations
Configuration, customisation, and implementation services

2. Applicable Standards

The solution must conform to the following standards unless otherwise specified:

Web Content Accessibility Guidelines (WCAG) current version — WCAG 2.2 Levels A/AA required for all web and mobile interfaces
AS EN 301 549 (latest version) for ICT accessibility across product categories
PDF/UA for any PDF deliverables
WAI-ARIA Authoring Practices for interactive components
ISO 9241-171 for software accessibility (where relevant)

Where standards conflict, WCAG takes precedence for digital interfaces.

3. Supplier Accessibility Documentation

The supplier must provide the following documentation as part of the procurement process:

A current VPAT® / Accessibility Conformance Report (ACR) based on WCAG or EN 301 549
A list of known accessibility issues and their severity
A remediation roadmap with timelines for addressing non-conformances
Details of testing methods, including assistive technologies used
Accessibility statements for any third-party components or dependencies

Documentation must be no more than 12 months old.

4. Functional Accessibility Requirements

The solution must support:

Full keyboard accessibility for all functionality
Clear and consistent focus indicators
Text alternatives for all non-text content
Resizable text up to 200% without loss of functionality
Colour contrast meeting WCAG
Error identification and suggestions
Accessible forms, labels, and instructions
Logical reading and navigation order
Accessible authentication (no cognitive-only tests)
Compatibility with assistive technologies, including screen readers, magnifiers, voice control, and switch devices

5. Non-Functional Accessibility Requirements

The supplier must ensure:

Accessibility is integrated into design, development, QA, and release processes
New features and updates maintain or improve accessibility
Accessibility regressions are treated as high-severity defects
Documentation, help content, and training materials are accessible
Support channels (chat, phone, email, portals) are accessible

6. Accessibility Testing Requirements

The supplier must conduct:

Automated testing using recognised tools
Manual testing by trained accessibility specialists
Assistive technology testing using at least: screen readers (NVDA, JAWS, VoiceOver, TalkBack), keyboard-only navigation, and screen magnification tools

Testing results must be provided to the buyer upon request.

7. Accessibility Deliverables

The supplier must deliver:

Updated VPAT/ACR reflecting the final implemented solution
An Accessibility Test Report summarising methods used, issues found, severity ratings, and remediation actions
An Accessibility Maintenance Plan for the contract term
Accessible versions of all documents, training materials, and user guides

8. Accessibility in Implementation and Configuration

If the solution requires configuration or customisation, the supplier must ensure:

All configured components meet WCAG
Custom code, templates, and workflows are accessible
Any inaccessible third-party components are disclosed with mitigation options
The buyer is notified of any accessibility limitations before implementation

9. Accessibility Acceptance Criteria

The solution will only be accepted when:

All critical and high-severity accessibility issues are resolved
Medium-severity issues have agreed remediation timelines
A final VPAT/ACR and test report are provided
Accessibility requirements are met across all supported browsers, devices, and platforms

The buyer reserves the right to conduct independent accessibility testing.

10. Ongoing Accessibility Obligations

Throughout the contract term, the supplier must:

Maintain accessibility compliance for all updates and releases
Notify the buyer of any new accessibility issues within 10 business days
Provide updated VPAT/ACRs annually
Ensure accessibility is included in product roadmaps
Support accessibility-related incidents through standard support channels

11. Accessibility Governance and Accountability

The supplier must nominate:

A single point of contact responsible for accessibility
A technical lead accountable for remediation
A support contact for accessibility-related incidents

The supplier must participate in accessibility reviews, audits, and governance meetings as required.