Digital access
OPS Hub Accessibility Statement
OPS Hub is committed to providing a digital experience that can be used by as many people as reasonably possible, including people who use keyboards, screen readers, zoom, larger text, high contrast and reduced motion.
Standard and current status
OPS Hub is designed toward the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We have not yet completed an independent whole-product accessibility audit. This statement therefore does not claim full WCAG 2.2 Level AA conformance.
Measures already taken
- Skip links to main content and structured headings in the operations workspace.
- Keyboard navigation, visible focus indicators and labelled form controls.
- Light or dark themes, high-contrast mode, text-size, font and accent-colour preferences.
- Support for reduced-motion preferences and avoidance of unnecessary animation.
- Status, error and warning messages that do not rely on colour alone.
- Automated contrast checks plus device, browser and key-workflow acceptance testing.
- English and Malay interface support across major areas of the system.
Known limitations
Some areas may not yet provide an equally effective experience for every user. Limitations being monitored include:
- Interactive maps, route optimisation and third-party content may be harder to use with a screen reader or keyboard alone.
- Camera, code-scanning, signature and media-capture workflows depend on device and browser capabilities.
- User-uploaded photos, videos, documents and evidence may not contain complete alternative text, captions or transcripts.
- Very large data tables, complex planning views and some legacy workflows may require further improvement.
- Exported PDFs, spreadsheets, documents or files produced by external systems may not always match the accessibility level of the web application.
Technical compatibility
OPS Hub is designed for modern desktop and mobile browsers. Experience can vary by operating system, browser, assistive technology, device settings and third-party module. Browsers no longer supported by their vendor may not work fully.
How accessibility is assessed
Current assessment combines self-evaluation, automated checks, keyboard testing, contrast verification, device testing and commercial acceptance cases. Independent auditing and testing with disabled users should be completed before any claim of full conformance is made.
Feedback and alternative assistance
Tell us when you encounter a barrier or need an alternative way to complete a task. Include the page or screen, the task you were trying to complete, your device and browser, any assistive technology used, and your preferred contact method.
Contact your organisation's OPS Hub administrator or the support address recorded in your deployment profile or service agreement.
Accessibility reports are handled through the deployment support process. Priority and response targets depend on operational impact and the active support policy.
Escalation and further review
When the first response does not resolve the issue, ask for the case to be escalated to the OPS Hub support owner or your organisation's management. Applicable legal and contractual requirements should be reviewed by appropriate advisers.
Statement dates
Prepared: 5 August 2026
This statement should be reviewed when major interface changes are released, after an accessibility audit, or at least annually.
References
This statement describes current targets, measures and known limitations. It is not a guarantee that every screen is barrier-free and is not legal advice.