This Accessibility Statement explains the accessibility standard we aim for, the measures we have taken, the current conformance status of canprocx.ca and the CanProcX service (the “Service”), and how to contact us if you encounter an accessibility barrier. It applies to the public website and the signed-in application, including the Standard and SAFE Defence tiers.

1.1   We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). WCAG 2.1 AA is an internationally recognised standard for making web content more accessible to people with a wide range of disabilities, including visual, auditory, motor, and cognitive impairments.

1.2   Our accessibility work is also informed by the goals of Canadian accessibility legislation, including the Accessible Canada Act and provincial standards such as the Accessibility for Ontarians with Disabilities Act (AODA), which reference WCAG 2.0/2.1 Level AA as their benchmark for information and communications.

2.1   We do not claim full conformance at this time, and we have not yet completed a formal third-party audit. We assess accessibility through a combination of manual review, keyboard testing, and automated tooling during development, and we prioritise fixes based on the severity of the barrier and how many users it affects.

3.1   In building and maintaining the Service, we take the following measures to support accessibility:

• Semantic HTML: we use meaningful, structured markup (headings, lists, landmarks, and native form controls) so the page is understandable to assistive technologies such as screen readers.
• Keyboard navigation: interactive elements (links, buttons, form fields, menus) are designed to be reachable and operable using a keyboard alone, without requiring a mouse.
• Colour contrast: we aim for text and essential interface elements to meet WCAG 2.1 AA contrast ratios so content remains legible for users with low vision.
• Text alternatives: we provide alternative text for meaningful images and icons, and we treat purely decorative graphics as such so they do not clutter the screen-reader experience.
• ARIA where appropriate: where a native HTML element is not sufficient, we use WAI-ARIA roles, states, and properties to convey the purpose and state of interface components.
• Responsive, resizable content: the layout is responsive and supports browser zoom and text resizing, so content reflows for smaller screens and larger text sizes.
• Clear focus and labels: form fields are labelled, and we work to keep a visible keyboard-focus indicator so users can tell where they are on the page.

4.1   Despite our efforts, some parts of the Service may not yet be fully accessible. We are being honest about this because we would rather set an accurate expectation than overclaim. Known or possible limitations include:

• Complex data views: some tender tables, filters, and dense data displays may not yet be fully optimised for every screen reader or for keyboard-only navigation.
• Dynamic and AI-generated content: interactive, AI-assisted features (such as bid drafting and the Pax assistant) may present content that has not yet been fully verified against every WCAG 2.1 AA success criterion.
• Third-party components: certain elements provided by third parties (for example, payment checkout, embedded documents, or externally sourced procurement notices) may not fully match our accessibility target and are partly outside our direct control.
• PDF and generated documents: some downloadable or generated documents may not yet be fully tagged for accessibility.

4.2   We are actively improving these areas. If any of them prevents you from completing a task, please contact us (Section 6) and we will help and prioritise a fix.

5.1   CanProcX is designed to work with current versions of major browsers (such as Chrome, Edge, Firefox, and Safari) and, where feasible, with common assistive technologies including screen readers. Because assistive technologies and browsers vary, some experiences may differ across combinations. If a particular combination does not work for you, let us know so we can investigate.

5.2   The Service relies on HTML, CSS, and JavaScript. Where JavaScript is required for a feature to function, we aim to keep the experience operable with assistive technologies; if you experience a barrier with a specific feature, the contact options below apply.

6.1   We welcome your feedback on the accessibility of CanProcX. If you encounter an accessibility barrier, need information in an alternative format, or want to request assistance completing a task, please contact us and we will respond as promptly as we reasonably can:

6.2   We aim to acknowledge accessibility enquiries and, where possible, provide the requested information or a reasonable alternative. If you are not satisfied with our response, please tell us so we can try again.

7.1   Accessibility is an ongoing commitment. We incorporate accessibility considerations into our design and development process and revisit this area as the Service evolves. We plan to review this statement periodically and to work toward a more complete conformance assessment over time.

7.2   We may update this Accessibility Statement from time to time to reflect changes to the Service or improvements to our accessibility practices. The “Effective” date and version shown at the top of this page indicate when it was last revised.