Report details
WCAG Edition, based on VPAT® Version 2.5Rev (April 2025), published by the Information Technology Industry Council (ITI). Prepared 6 September 2026 for the Sairo web application, package version 0.1.0, local development revision reviewed on that date.
Sairo provides website-grounded answers, text-based live chat, customer workspaces, administrative tools and OAuth connection approval. This draft targets WCAG 2.2 Level A and Level AA. It does not report Section 508, EN 301 549 or Level AAA conformance.
This is an evaluation working draft, not an issued procurement ACR. A blank or unassigned conformance cell means a rating still needs to be decided. “Not Evaluated” is not used as an A or AA rating. The complete report must be reviewed and approved after manual validation.
Source references
Scope and evaluation methods
The reviewed product includes public information pages, account flows, customer and staff web interfaces, the public demo, visitor widget and web-based OAuth approval. Customer host pages, customer-provided content and branding, external checkout, connected applications and native apps are outside this report’s conformance scope.
Methods include source inspection, axe-core 4.11.1 in the Chromium-based local browser, inspection of hydrated controls, narrow-layout and text-spacing checks, and contrast calculations for shared theme colours and image-backed forms. Sample records are used for authenticated workflows.
No screen-reader user testing, independent certification or full assistive-technology compatibility assessment is claimed. Automated passes are evidence for a review, not proof that a complete page or process conforms. Each row below gives the remaining verification task.
- HTML, CSS and JavaScript support the core web interface.
- Decorative WebGL has a still-image fallback.
- Optional microphone dictation requires browser permission.
- Customer installations must be tested as complete pages in their own environment.
Conformance terms for the completed report
The editable report retains the standard conformance column. Its ratings are intentionally blank during this draft stage. Use the following ITI terms only when the relevant evidence supports a conclusion.
- Supports
- At least one method meets the criterion without known defects, or meets it through equivalent facilitation.
- Partially Supports
- Some of the product functionality does not meet the criterion.
- Does Not Support
- Most of the product functionality does not meet the criterion.
- Not Applicable
- The criterion is not relevant to the product being reported.
WCAG 2.2 Level A
This table preserves the historical 4.1.1 row from the template. Parsing was removed from WCAG 2.2 and is excluded from its 55 current A and AA criteria.
| Criterion | Conformance level | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content | Not yet assigned (draft) | Product illustrations have descriptions; purely decorative icons and the WebGL scene are hidden from assistive technology. Charts include text values. Next check: Review descriptions, charts and customer-supplied logos with a screen reader. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not yet assigned (draft) | The reviewed web routes contain no prerecorded audio-only or video-only informational media. Optional dictation is user input. Next check: Reassess when recorded media is introduced. |
| 1.2.2 Captions (Prerecorded) | Not yet assigned (draft) | No prerecorded synchronized media is included in the reviewed web interface. Live chat is text. Next check: Reassess captions when synchronized media is introduced. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not yet assigned (draft) | No prerecorded synchronized media is included in the reviewed web interface. Next check: Reassess media alternatives when synchronized media is introduced. |
| 1.3.1 Info and Relationships | Not yet assigned (draft) | Pages use headings, navigation landmarks, labelled forms, fieldsets and semantic tables. Shared field hints are connected to controls. Next check: Read complex tables, grouped settings, chart values and dialog relationships with assistive technology. |
| 1.3.2 Meaningful Sequence | Not yet assigned (draft) | Source order follows the content sequence. Responsive tables retain explicit row, cell and header roles. Next check: Check reading order at mobile widths and with styles disabled. |
| 1.3.3 Sensory Characteristics | Not yet assigned (draft) | Instructions name controls and describe actions in words; status indicators also include text. Next check: Review complete tasks for instructions that depend on position, shape or sound. |
| 1.4.1 Use of Color | Not yet assigned (draft) | Validation, availability, connection and conversation states have text labels. Active navigation also exposes aria-current. Next check: Check selected states and charts in grayscale and forced-colours mode. |
| 1.4.2 Audio Control | Not yet assigned (draft) | The reviewed pages do not start audio automatically. Dictation begins only after a user request. Next check: Reassess if autoplay media or audio notifications are added. |
| 2.1.1 Keyboard | Not yet assigned (draft) | Actions use native buttons, links and form controls. Scrollable chat transcripts and code can receive keyboard focus. Next check: Complete every primary workflow using only the keyboard, including live handoff and OAuth consent. |
| 2.1.2 No Keyboard Trap | Not yet assigned (draft) | The visitor chat is nonmodal and has Escape handling. Workspace navigation uses a native dialog with a close button. Next check: Confirm forward and reverse tabbing, Escape and focus restoration in all dialogs. |
| 2.1.4 Character Key Shortcuts | Not yet assigned (draft) | Message shortcuts are handled on the focused composer; there are no global single-character shortcuts in the reviewed web source. Next check: Check speech-input interactions and focused composer shortcuts. |
| 2.2.1 Timing Adjustable | Not yet assigned (draft) | Save confirmations remain until dismissed. Request limits and session expiry exist; long-running tasks show status and retry options. Next check: Assess expiry, recovery and preservation of unsent input through complete timed processes. |
| 2.2.2 Pause, Stop, Hide | Not yet assigned (draft) | The moving hero offers Pause motion and follows reduced-motion preferences. Other decorative effects follow the shared motion setting. Next check: Verify the pause control, all loading animations and automatic updates in a reduced-motion environment. |
| 2.3.1 Three Flashes or Below Threshold | Not yet assigned (draft) | Reviewed motion consists of slow scene movement and loading indicators; no deliberate flashing sequences are present. Next check: Inspect final rendered animations for flashes across supported devices. |
| 2.4.1 Bypass Blocks | Not yet assigned (draft) | Public, account, demo and workspace shells provide skip links and main landmarks. Next check: Activate each skip link using a keyboard and screen reader; verify its landing point. |
| 2.4.2 Page Titled | Not yet assigned (draft) | Public pages have descriptive titles. Account, workspace and staff routes have task-specific titles rather than one shared title. Next check: Check title and page-change announcements during client navigation. |
| 2.4.3 Focus Order | Not yet assigned (draft) | No positive tabindex is used. Failed form submissions move focus to feedback; dialog and chat close actions restore focus. Next check: Trace focus through validation, history, dynamic replies, navigation and removed controls. |
| 2.4.4 Link Purpose (In Context) | Not yet assigned (draft) | Links describe destinations or have their purpose provided by their containing card, table row or related text. Next check: Review repeated actions in context and the screen-reader links list. |
| 2.5.1 Pointer Gestures | Not yet assigned (draft) | Product actions use single-pointer activation. The decorative 3D scene is not required for any task. Next check: Verify no operation requires a multipoint or path-based gesture. |
| 2.5.2 Pointer Cancellation | Not yet assigned (draft) | Core actions use click or form submission, rather than completing a task on pointer-down. Next check: Test pressing, moving off a target and releasing, including touch controls. |
| 2.5.3 Label in Name | Not yet assigned (draft) | Controls generally use their visible text as their name. Icon-only controls have explicit labels. Next check: Check voice-control matching against all visible labels and state changes. |
| 2.5.4 Motion Actuation | Not yet assigned (draft) | No web task requires device movement, shaking or orientation gestures. Next check: Reassess when motion-controlled functionality is introduced. |
| 3.1.1 Language of Page | Not yet assigned (draft) | The document root declares English with lang="en". Next check: Verify the browser exposes the page language to assistive technology. |
| 3.2.1 On Focus | Not yet assigned (draft) | Focus highlights controls without submitting forms or opening destinations. Next check: Tab through complete processes and confirm there are no unexpected context changes. |
| 3.2.2 On Input | Not yet assigned (draft) | Save and submit actions have explicit controls. Filters and example selectors update content within the page. Next check: Review scope selectors and filters for clear, predictable changes. |
| 3.2.6 Consistent Help | Not yet assigned (draft) | Shared shells link to accessibility information and support in consistent locations for that group of pages. Next check: Confirm help remains discoverable throughout onboarding and error recovery. |
| 3.3.1 Error Identification | Not yet assigned (draft) | Native required and format validation is used. Server errors are written in text and shared form feedback receives focus. Next check: Test every validation branch with screen readers and check error association and recovery. |
| 3.3.2 Labels or Instructions | Not yet assigned (draft) | Inputs have labels, optional fields are identified, and password and message-length instructions are provided. Next check: Review all constraints before input and check screen-reader announcement of hints. |
| 3.3.7 Redundant Entry | Not yet assigned (draft) | Forms preserve entries when server validation fails. The demo can prefill the website when continuing to signup. Next check: Follow complete onboarding, recovery and correction processes for unnecessary repeated entry. |
| 4.1.1 Parsing | Does not apply to WCAG 2.2 | This success criterion was removed from WCAG 2.2. The retained template row is historical and is not counted in the WCAG 2.2 total. Next check: No WCAG 2.2 rating is required. |
| 4.1.2 Name, Role, Value | Not yet assigned (draft) | Controls expose names, roles and relevant states. Dropdown and dialog relationships use local element identifiers. Next check: Test names, roles and changing values across browser and assistive-technology combinations. |
WCAG 2.2 Level AA
These criteria are evaluated in addition to Level A. Remarks identify implementation evidence and the manual work still needed.
| Criterion | Conformance level | Remarks and explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not yet assigned (draft) | The service supplies text chat and does not supply live synchronized audio/video content in the reviewed web routes. Next check: Reassess when live audiovisual media is introduced. |
| 1.2.5 Audio Description (Prerecorded) | Not yet assigned (draft) | No prerecorded synchronized video is present in the reviewed web routes. Next check: Reassess audio description when prerecorded video is introduced. |
| 1.3.4 Orientation | Not yet assigned (draft) | Layouts use responsive rules without orientation locks. Next check: Complete primary workflows in portrait and landscape, including small-height windows. |
| 1.3.5 Identify Input Purpose | Not yet assigned (draft) | Account and contact fields use applicable name, email, URL and password autocomplete tokens. Next check: Check browser and assistive-technology identification of fields about the current user. |
| 1.4.3 Contrast (Minimum) | Not yet assigned (draft) | Text and preset themes have automated contrast checks. Custom low-contrast themes require explicit acknowledgement. Image-backed account surfaces have a tested opaque colour floor. Next check: Review image and gradient contexts, all interactive states and user-supplied branding. |
| 1.4.4 Resize text | Not yet assigned (draft) | The site does not restrict browser zoom; layouts and typography use responsive sizing. Next check: Check actual 200 percent browser zoom and text-only enlargement without lost content or actions. |
| 1.4.5 Images of Text | Not yet assigned (draft) | Interface copy is rendered as text. Logos and decorative illustrations are the remaining image content. Next check: Confirm new imagery does not carry instructions that are missing from the text. |
| 1.4.10 Reflow | Not yet assigned (draft) | Responsive layouts and tables adapt to narrow containers. Main content and controls are checked at 320 CSS pixels. Next check: Complete tasks at 400 percent zoom; check overlays, diagrams and long user content. |
| 1.4.11 Non-text Contrast | Not yet assigned (draft) | Theme focus and field boundaries are checked against adjacent surfaces. Custom contrast warnings require acknowledgement. Forced colours remain available. Next check: Review icons, chart marks, selected controls and focus against adjacent colours in all states. |
| 1.4.12 Text Spacing | Not yet assigned (draft) | Containers generally grow with their content. A local testing control applies the WCAG text-spacing values. Next check: Inspect every workflow with increased line, paragraph, letter and word spacing; test text inside Shadow DOM too. |
| 1.4.13 Content on Hover or Focus | Not yet assigned (draft) | Public navigation is explicitly opened, can be dismissed, and closes when focus leaves. Browser-native tooltips are used for supplementary hints. Next check: Check all popovers with keyboard and pointer for dismissibility, persistence and hoverability. |
| 2.4.5 Multiple Ways | Not yet assigned (draft) | The public site provides primary navigation, footer links, a complete HTML sitemap and contextual links. Next check: Confirm essential pages remain reachable through more than one route. |
| 2.4.6 Headings and Labels | Not yet assigned (draft) | Pages have descriptive primary headings; fields, sections and actions use task-oriented labels. Next check: Review clarity and heading order with the screen-reader heading list, including empty states. |
| 2.4.7 Focus Visible | Not yet assigned (draft) | Shared focus-visible rules draw contrasting outlines; scoped connection styles inherit the active theme. Next check: Inspect every focused control in light, dark and forced-colours modes. |
| 2.4.11 Focus Not Obscured (Minimum) | Not yet assigned (draft) | Page focus targets have scroll margins. The floating widget yields when it overlaps a focused page control. Next check: Check sticky headers, dialogs, notices and chat at high zoom and on short screens. |
| 2.5.7 Dragging Movements | Not yet assigned (draft) | The reviewed product has no task that requires a dragging movement. Next check: Reassess if sortable, draggable or gesture-only controls are introduced. |
| 2.5.8 Target Size (Minimum) | Not yet assigned (draft) | Most standalone controls use generous targets; automated checks cover the WCAG minimum and spacing rules. Next check: Inspect all responsive states, inline-link exceptions and densely grouped controls. |
| 3.1.2 Language of Parts | Not yet assigned (draft) | The authored interface is English. Visitor messages, customer knowledge and generated text can contain other languages without reliable per-passage language metadata. Next check: Evaluate multilingual messages and announce language changes correctly before assigning a rating. |
| 3.2.3 Consistent Navigation | Not yet assigned (draft) | Shared page shells preserve navigation order within the public site, account flows and each workspace. Next check: Confirm consistent navigation across roles and responsive breakpoints. |
| 3.2.4 Consistent Identification | Not yet assigned (draft) | Shared components keep recurring actions, help links and controls consistently named. Next check: Review labels across error, empty, pending and completed states. |
| 3.3.3 Error Suggestion | Not yet assigned (draft) | Validation messages explain common corrections such as required values, format, length and password rules. Next check: Exercise server-side failures and confirm useful correction suggestions without exposing protected data. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not yet assigned (draft) | Knowledge changes can be reviewed and undone where supported. Billing uses an external checkout; workspace forms save on explicit submission. Next check: Review financial and data-changing workflows, confirmations and irreversible operations end to end. |
| 3.3.8 Accessible Authentication (Minimum) | Not yet assigned (draft) | Sign-in allows password managers and paste. Password reveal and recovery are available; no puzzle or memory task beyond supported password entry is imposed. Next check: Complete sign-in, signup, invitation acceptance, recovery and OAuth with assistive technology and a password manager. |
| 4.1.3 Status Messages | Not yet assigned (draft) | Status and error regions expose pending, completion and failure messages. Streaming visitor replies use a separate sentence announcer; the visible log is explicitly aria-live="off". Next check: Listen for lost, repeated or excessive announcements during streaming, live chat, saves and errors. |
Complete the manual validation
Record the release, browser and assistive-technology versions, tested pages and roles, test steps, result, evidence and issue reference. Test a full process, including its errors and recovery, before assigning a conformance rating.
Use the editable report to replace the open ratings with supported conclusions. Record any exceptions precisely, rerun automated checks after fixes, update the date and scope, and review the result before sharing it as a completed ACR.
Keyboard and focus
Complete navigation, signup, sign-in, recovery, setup, data changes, live handoff and connection approval using Tab, Shift+Tab, Enter, Space, Escape and arrow keys where appropriate.
Screen readers
Check headings, landmarks, forms, tables, source links, errors, streaming replies, live messages and focus changes with NVDA and VoiceOver. Include mobile screen readers.
Visual adaptation
Check 200 percent text enlargement, 400 percent zoom, 320 CSS pixel reflow, portrait and landscape, increased text spacing, forced colours and both workspace themes.
Complete processes and content
Include long content, validation failures, session expiry, saved-answer changes and undo, billing handoff, OAuth consent, customer branding and multilingual conversations.