Accessibility statement

Accessibility status

The Safe-In web application has undergone internal automated and manual checks against selected WCAG 2.2 Level A and Level AA requirements. Full conformance has not yet been established, so this statement is not an accessibility certification or a claim that every page and feature meets WCAG 2.2 AA.

The reviewed scope includes public account and legal pages, shared application components, authenticated workspace foundations, and the browser-based visitor portal. The iOS, Android, macOS and Windows applications share much of this interface, but still require platform-specific assistive-technology testing.

Accessibility features implemented

• A keyboard-visible Skip to main content link and one main landmark on each reviewed route.
• Route-specific page titles, page headings, document language, and announcements after client-side navigation.
• Consistent visible keyboard focus, including support for Windows forced-colors mode.
• Keyboard-accessible menus, mobile navigation, dialogs and confirmation popovers, with Escape handling, focus trapping and focus restoration where applicable.
• Labelled form fields, associated instructions and errors, live status messages, accessible password visibility controls, and consistent primary styling for submit actions.
• Minimum 24 by 24 CSS-pixel targets for interactive controls, with larger targets for shared buttons.
• Reduced-motion support for people who disable nonessential animation.
• Semantic headings, lists and data-table headers that expose page structure to assistive technology.
• Layouts that reflow at 320 CSS pixels and tolerate WCAG text-spacing overrides without two-dimensional page scrolling on the audited public routes.
• Automatic foreground-color selection for organisation branding colors to improve contrast in the visitor portal.

Testing and verification

The latest internal review on 23 September 2026 included automated semantic tests for authenticated workspace, visitor portal, form, table and dialog foundations. The test suite checks WCAG 2.0 A and AA, WCAG 2.1 AA and WCAG 2.2 AA rules supported by axe-core.

A rendered Chromium audit covers login, organisation registration, support, privacy request, terms, privacy, cookie, data-processing and accessibility pages. It checks keyboard bypass navigation, focus appearance, landmarks, page titles and headings, color contrast, target sizing, reduced motion, text spacing and 320 CSS-pixel reflow.

Regression tests run alongside linting, TypeScript checks and the production build. Automated tools can identify many barriers, but they cannot establish complete WCAG conformance.

Limitations and checks still needed

End-to-end testing with VoiceOver, NVDA and TalkBack remains outstanding, as does full keyboard testing at 200% and 400% zoom. The native mobile and desktop applications, physical kiosks, camera flows, quizzes, compliance documents and timeout behavior also require platform-specific review.

Organisation-provided logos, documents, backgrounds and custom colors can affect accessibility. Third-party sign-in, payment, messaging and other external services have not been fully assessed and may vary.

We have not yet completed an independent comprehensive audit or structured usability testing with people with disabilities. These checks are required before Safe-In makes a formal claim of WCAG 2.2 AA conformance.

Feedback and accessible alternatives

Use the Support link below to report an accessibility problem or request an accessible way to complete a task. Include the page or task, what went wrong, and your browser, device and assistive technology if relevant. Do not include passwords or sensitive visitor information.

If you cannot complete visitor registration at a location, ask the reception team or your host for assistance.