Accessibility
AccessPoint is built for the public sector, where accessibility isn't a feature request — it's an obligation we share with our customers.
Our commitment
Realizer Services Inc. is committed to making AccessPoint and this website usable by everyone, including people who rely on assistive technologies. Accessibility is a design requirement in our development process, not an afterthought — alongside the platform's full multilingual interface across 11 languages, it's part of building software the whole workforce can use.
The standard we design against
AccessPoint and realizer.io are designed against WCAG 2.1 Level AA (Web Content Accessibility Guidelines). That's the standard referenced by the accessibility legislation our customers answer to, including:
- The Accessibility for Ontarians with Disabilities Act (AODA) and the Accessible Canada Act
- Section 508 of the Rehabilitation Act (United States)
- EN 301 549 (European Union)
Reported accessibility gaps are treated as defects, not feature requests. A self-assessed Accessibility Conformance Report for the AccessPoint application — per-criterion results against WCAG 2.1 A and AA in the VPAT® format, built from static code review, independent adversarial verification, and runtime browser verification, with an open-items roadmap — is published and kept current. If your review needs anything beyond it, contact us.
What this looks like in the product
- 11 languages, natively — English, French, German, Spanish, Italian, Dutch, Danish, Portuguese, Finnish, Swedish, and Polish — the interface is fully multilingual, so accessibility includes working in the language of your workforce. The full multilingual story is at supported languages.
- Built on Microsoft 365 — AccessPoint runs inside SharePoint and Teams, keeping your team in an environment whose assistive-technology behavior they already know.
- Designed to be inclusive — accessibility is a design consideration across the interface, and reports from real assistive-technology users directly shape what we fix first.
- Enforced in the build — an error-severity accessibility lint gate (ARIA validity, labels, alt text, focus rules) fails the product's CI on violations, so conformance holds as the product changes.
Tell us what isn't working
If you encounter an accessibility barrier in AccessPoint or on this site, we want to know about it. Contact us with the page or screen, what you were trying to do, and the assistive technology you were using — we respond within one business day, and accessibility reports are triaged with defects, not feature requests.
This statement was last reviewed in August 2026. It's part of the AccessPoint procurement pack.