A website that welcomes more people.

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We consider keyboard access, readable content, clear forms, focus, motion preferences and assistive-technology support when building the service.

Prepared on 6 September 2026. The current review combines source inspection, automated browser checks and targeted checks of the interface. Manual testing with screen readers and other assistive technologies has not yet been completed.

Full WCAG conformance has not been established. The accompanying report is a draft with evidence and a manual test plan; it is not an accessibility certification. We will need to update its findings after manual testing and when the product changes.

This statement covers the Sairo public website, sign-in and signup, account management, customer workspace, staff web administration, public demo, web-based connection approval, and the Sairo visitor chat interface.

A customer’s own website, custom branding and content, third-party checkout, connected AI applications, operating-system permission dialogs, and native desktop or mobile apps require their own assessment. Adding Sairo does not fix barriers elsewhere on a website.

• Use a keyboard to move between links, buttons and fields. Skip links lead past repeated navigation.
• Enlarge the page using your browser. Content and tables adapt to smaller screens; long code samples and conversations can be scrolled.
• Pause the animated assistant in the homepage hero. A reduced-motion setting in your device also reduces decorative movement.
• Type instead of dictating. Microphone access is optional, and dictated text can be checked before you send it.
• Use a password manager or paste a password into account forms. Password reveal controls are available.
• Read conversation history at your own pace. Visitor reply announcements use complete sentences, while connection and handoff states also appear as text.

Screen-reader reading order, spoken announcements, complete keyboard journeys, high zoom, forced colours and mobile assistive technology need further manual validation. Automated checks cannot establish the quality of those experiences.

Generated answers and customer content may include unfamiliar language or information that needs clarification. Site owners can explicitly acknowledge and save custom theme contrast warnings. Such a configuration is not a conformance claim. Custom colours, logos, source documents and the surrounding host page can affect the visitor experience. Check a customer installation in its real theme and context.

The core service uses HTML, CSS and JavaScript. WebGL is used for a decorative hero scene with a still-image fallback. Dictation additionally depends on browser support and microphone permission. Cross-browser assistive-technology compatibility has not yet been established.

Capabilities added after the review date have not been assessed. That currently includes attaching a file to a conversation, the rating control, proactive prompts, the hosted help centre pages, and the workspace screens for uploaded documents, actions, API keys and custom domains. They were built to the same interaction patterns as the reviewed interface, which is a design intention rather than an evaluation result. Treat them as unassessed until the next review, and report a barrier through the contact form.

Choose Accessibility issue on our contact form. Include the page address, what you were trying to do, what happened, and the browser, device or assistive technology you used. Tell us if you need the information in another format.

You do not need a Sairo account to send the form. Please leave out passwords and sensitive visitor information. If you cannot use the form, ask your workspace administrator to raise the issue through their existing support contact. For a widget on another business’s site, you can also report the barrier to that website’s operator.

This review uses WCAG 2.2 A and AA criteria, axe-core automated checks on the local web build, theme contrast calculations, and inspection of shared components and interactive states. The assessment record identifies its scope and remaining checks.

The next evaluation should include keyboard-only use and screen readers such as NVDA with Windows browsers, VoiceOver with Safari, and mobile assistive technology. Findings should be recorded against the same criteria and fixed before the draft report is issued as a completed conformance report.