The interaction details matter.
The chat launcher has an accessible name. Opening and closing the widget manages focus, and Escape returns the visitor to the launcher. A separate polite announcement region reads complete reply sentences while the transcript stays available to browse.
Live chat states use words such as waiting, connected, and ended, and the specialist’s name identifies the speaker. Controls use generous targets, and reduced-motion preferences are respected.
- Named controls and keyboard operation
- Clear live chat status and speaker names
- Polite transcript announcements
- Reduced-motion support
An optional way to speak your question.
When enabled for the website and supported by the browser, dictation lets a visitor record a short question after granting microphone permission. Sairo converts the recording to text and inserts it into the composer so the visitor can check or edit it before sending.
Typing remains available. This is speech-to-text input, not a telephone service or a spoken conversation with the assistant. Availability depends on site settings, the configured transcription provider and the workspace’s dictation allowance. Test microphone permission, recording status and the typing fallback in your own website.
Test the widget as part of the whole page.
A widget can interact with sticky navigation, consent banners, zoom, and other fixed elements. Test the installation in your website’s actual layout, including narrow screens and enlarged text.
The widget uses Shadow DOM instead of an iframe. Its accessible relationships stay within the same component boundary; this does not remove the need to check the resulting experience with assistive technology.
Design intent is not a certification.
Sairo targets relevant WCAG 2.2 AA interaction requirements. The accessibility statement and VPAT-based draft report describe the current review and the manual validation still needed. Full conformance has not been established.
A chatbot cannot repair accessibility barriers elsewhere on your website. Include the assistant in your normal audit, document the tested browsers and assistive technologies, and report any issue through the contact form.