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.2 Level AA (Web Content Accessibility Guidelines). WCAG 2.2 builds on 2.0 and 2.1 — it keeps every earlier success criterion except the retired 4.1.1 Parsing and adds six of its own, such as focus that is never hidden and controls large enough to hit — so designing against it covers the versions referenced by the accessibility laws and standards our customers answer to, including:

Our self-assessment

We publish a self-assessed Accessibility Conformance Report for AccessPoint in the VPAT® format, with per-criterion results against both WCAG 2.2 and WCAG 2.1, Levels A and AA. It covers both editions: the Microsoft 365 edition, in SharePoint and Teams, and Hosted AccessPoint, the hosted edition Realizer serves in the browser at app.realizer.io. The current edition, revised on 12 November 2026, evaluates AccessPoint 2.6.0. It is built from a static review of the full application source, runtime checks in the browser and from the keyboard, and screen-reader testing, and it assesses the public request portal, the media viewer, training and Lab mode, AccessPoint Learning, and the response packages AccessPoint generates in their own sections.

Against WCAG 2.2 Level A and AA, 48 of the 52 applicable criteria Support in the Microsoft 365 edition and four Partially Support, with none that Does Not Support. In the hosted edition, 2.2.1 Timing Adjustable is also rated Partially Supports: a session can be extended before it ends for inactivity, but its 12-hour limit cannot, as a security control. The surfaces new in 2.6.0 and the hosted edition have been checked by code review, automated scans, checks in the browser and a 320 CSS px reflow pass, and by an NVDA screen-reader pass; the report says section by section what each check covered and what is still open. The report names each open item and what we are doing about it, and it is updated with each release. It is a self-assessment: no third-party audit has been performed. Reported accessibility gaps are treated as defects, not feature requests — if your review needs anything beyond the report, contact us.

What this looks like in the product

This website

realizer.io is designed against the same standard: semantic headings and landmarks, keyboard-operable navigation and FAQs, visible focus that the sticky header never covers, colour contrast that meets AA, and controls sized for WCAG 2.2's minimum target. The documentation is published in 11 languages, and each page carries its own language for screen readers.

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 November 2026. It's part of the AccessPoint procurement pack.