About this report
This report is a self-assessment. Kronisys Inc. evaluated Strata itself; no third party took part, and the product has not yet been tested with screen readers or other assistive technology by people who use them. Where a criterion is not fully met, the remarks say exactly where.
Scope
Covered: the Strata web application at desktop and phone sizes, in the light and dark themes (evaluated in Chromium, the engine of Chrome and Edge, with keyboard behaviour also checked in WebKit, the engine of Safari; Firefox was not tested); the Strata add-in in Microsoft Outlook; the documentation site; and the files Strata generates, reported in the tables as Electronic Docs.
Not covered: the Microsoft Teams app, whose cards are drawn by Teams from the text and controls Strata supplies; pages served by other companies (Microsoft, Google and single sign-on providers’ sign-in pages, the Stripe checkout and billing portal, Atlassian’s authorization pages); and content the assistant writes as free-form pages for a request (dashboards and diagrams), whose accessibility depends on what was generated and is noted under the criteria it affects.
How it was evaluated
- Automated testing with axe-core 4.14.0 (Deque Systems) using its WCAG 2.0, 2.1 and 2.2 Level A and AA rules: 294 screens of the web application, driven by Strata’s own browser test harness with representative data, each at a desktop size (1440 by 900 CSS pixels) and a phone size (412 by 915), in both themes (1,112 views); 112 states of the Outlook add-in at 320 and 450 CSS pixels in both themes; and the documentation site (424 page views).
- Scripted checks: reflow at 320 CSS pixels on every screen; on every screen at the desktop size, the WCAG text spacing values applied (recording text a box then cuts that it did not cut before) and Tab pressed through the first 40 stops (recording any stop that could not be seen); and the keyboard operation of the custom controls, by Strata’s automated test suite, which drives them in Chromium and many of them in WebKit.
- Review of the source of each custom control and of the names, roles and states the browser exposes for them, and inspection of generated PDF, Word and PowerPoint files.
- Not done: testing with screen readers or other assistive technology by people who use them, and a third-party audit.
Standards
| Standard or guideline | Included in report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A: Yes. Level AA: Yes. Level AAA: No. |
| Web Content Accessibility Guidelines 2.1 | Level A: Yes. Level AA: Yes. Level AAA: No. |
| Web Content Accessibility Guidelines 2.2 | Level A: Yes. Level AA: Yes. Level AAA: No. |
| Revised Section 508 Standards (36 CFR Part 1194, 2017) | Yes |
| EN 301 549 Accessibility requirements for ICT products and services, V3.2.1 (2021-03) | Yes |
The WCAG 2.2 tables below include every Level A and AA criterion of WCAG 2.0 and 2.1, so they report all three versions; 4.1.1 is reported as WCAG 2.0 and 2.1 define it.
Terms
WCAG 2.2 Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) Understanding 1.1.1 | Web: Partially Supports Electronic Docs: Partially Supports | Web: Buttons that show only an icon are named, and decorative images and icons are hidden from assistive technology. A chart in an answer is an image named by its title, followed by its numbers in a table that only a screen reader reads. Maps list their places as text. Not met: a dashboard page or a diagram the assistant builds may carry charts or drawings with no text alternative, since that page is written by the assistant for each request. Electronic Docs: Word and PowerPoint files name the organization logo, and a PowerPoint image carries the description the deck gives it. PDF files are not tagged: their images and charts have no text alternative. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Understanding 1.2.1 | Web: Not Applicable | Web: Strata has no prerecorded audio or video. Voice mode speaks answers that are also written in the conversation. |
| 1.2.2 Captions (Prerecorded) (Level A) Understanding 1.2.2 | Web: Not Applicable | Web: Strata has no prerecorded audio or video. Voice mode speaks answers that are also written in the conversation. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Understanding 1.2.3 | Web: Not Applicable | Web: Strata has no prerecorded audio or video. Voice mode speaks answers that are also written in the conversation. |
| 1.3.1 Info and Relationships (Level A) Understanding 1.3.1 | Web: Supports Electronic Docs: Partially Supports | Web: Pages use headings, lists, landmarks (main content, navigation), data tables with header cells, labelled form fields and grouped choices, and dialogs that are marked as dialogs. Custom controls (menus, tabs, switches and the sheet grid) expose their roles. Dashboard pages the assistant builds are outside this row (see 1.1.1). Electronic Docs: Word files use real title and heading styles and repeat table header rows. Excel files put column headers in the first row of each named sheet, but define no table, so a screen reader in Excel does not announce the headers from cell to cell. PowerPoint slide titles are text boxes rather than title placeholders, so a slide list does not name the slides. PDF files are not tagged, so their headings, lists and tables are not exposed as such. |
| 1.3.2 Meaningful Sequence (Level A) Understanding 1.3.2 | Web: Supports Electronic Docs: Partially Supports | Web: The reading order of every page follows its visual order: the sidebar, the page, then the message box. Electronic Docs: Word and PowerPoint keep the order in which content was written. PDF files have no tagged reading order. |
| 1.3.3 Sensory Characteristics (Level A) Understanding 1.3.3 | Web: Supports | Web: Instructions name the control and its words; none rely on shape, colour, size or position alone. |
| 1.4.1 Use of Color (Level A) Understanding 1.4.1 | Web: Partially Supports Electronic Docs: Partially Supports | Web: Status, errors and required fields are stated in words, not only in colour, and links in answers are underlined. Not met: the lines and bars of a chart with several series are told apart by colour and by their legend; hovering or focusing a point names its series, and the same numbers are in the chart's table for screen readers. Electronic Docs: Charts in generated files tell series apart by colour and legend. |
| 1.4.2 Audio Control (Level A) Understanding 1.4.2 | Web: Supports | Web: Audio plays only in voice mode, which the person starts, and can be stopped at any time. |
| 2.1.1 Keyboard (Level A) Understanding 2.1.1 | Web: Supports | Web: Every function works from the keyboard, including the menus, the schema map (moving and zooming the map, moving a table), the slide editor (choosing, moving and sizing objects), the sheet editor, the checklist, calendar views and questions that ask for an order. A file card in an answer opens its preview with a pointer; from the keyboard the same file opens from the Outputs list of the conversation's workspace. A dashboard page the assistant builds is keyboard operable to the extent the generated page is. |
| 2.1.2 No Keyboard Trap (Level A) Understanding 2.1.2 | Web: Supports | Web: Focus never becomes stuck. Dialogs close with Escape and return focus. Where Tab has a job inside an editor (indenting in the Markdown editor, moving between table cells), Escape leaves the field and the next Tab moves on; the slide and the sheet grid give up Tab past their last object or cell. |
| 2.1.4 Character Key Shortcuts (Level A) Understanding 2.1.4 | Web: Supports | Web: The only shortcuts made of a single character belong to the schema map and work only while the map has focus. Other shortcuts use a modifier key (for example Ctrl or Cmd with K). |
| 2.2.1 Timing Adjustable (Level A) Understanding 2.2.1 | Web: Partially Supports | Web: Not met: a request for approval waits 10 minutes and a question the assistant asks during an answer waits 90 seconds before the answer continues without it; neither can be extended from the card (an approval is never taken without an answer, and it can be asked again). Sessions end after the period of inactivity the organization sets, without a warning; an unsent message is put back after signing in again. |
| 2.2.2 Pause, Stop, Hide (Level A) Understanding 2.2.2 | Web: Supports | Web: An answer is written only after a request and can be stopped while it is written. Animations, including the working indicator, follow the reduce-motion setting of the operating system. |
| 2.3.1 Three Flashes or Below Threshold (Level A) Understanding 2.3.1 | Web: Supports | Web: Nothing flashes. |
| 2.4.1 Bypass Blocks (Level A) Understanding 2.4.1 | Web: Supports | Web: A skip link is the first stop on every page with the sidebar, and pages mark their main content and navigation as landmarks. |
| 2.4.2 Page Titled (Level A) Understanding 2.4.2 | Web: Supports Electronic Docs: Supports | Web: Every page has a title naming the page and Strata; a conversation is titled by its name. Electronic Docs: Word, PowerPoint and PDF files carry their title, and a PDF asks the reader to show it in place of the file name. |
| 2.4.3 Focus Order (Level A) Understanding 2.4.3 | Web: Supports | Web: Focus moves in reading order; a dialog takes focus when it opens, holds it while open and returns it to the control that opened it. A button that hides once pressed from the keyboard (Jump to latest, Follow response) passes focus on to the message box. |
| 2.4.4 Link Purpose (In Context) (Level A) Understanding 2.4.4 | Web: Supports | Web: Links are named by their text or, for icon links, by an accessible name. Links the assistant writes in answers carry the words it gives them. |
| 2.5.1 Pointer Gestures (Level A) Understanding 2.5.1 | Web: Supports | Web: Pinch zoom on maps and the schema map has zoom buttons beside it; nothing needs a path-based gesture. |
| 2.5.2 Pointer Cancellation (Level A) Understanding 2.5.2 | Web: Supports | Web: Actions run when the pointer is released. The few that act on press (opening a folded search field, choosing a search result) only open or show something and are undone by the next press or Escape. |
| 2.5.3 Label in Name (Level A) Understanding 2.5.3 | Web: Supports | Web: Controls are named by the words they show; where a control needs more context, it is added after those words, unseen. |
| 2.5.4 Motion Actuation (Level A) Understanding 2.5.4 | Web: Not Applicable | Web: Nothing is operated by moving the device. |
| 3.1.1 Language of Page (Level A) Understanding 3.1.1 | Web: Supports Electronic Docs: Partially Supports | Web: The page language follows the language the person chooses, in all 35 languages Strata is written in. Electronic Docs: Word and PowerPoint files take the language set in the reader's Office. PDF files do not state a language. |
| 3.2.1 On Focus (Level A) Understanding 3.2.1 | Web: Supports | Web: Focus never changes the context. |
| 3.2.2 On Input (Level A) Understanding 3.2.2 | Web: Supports | Web: Changing a field or a setting never changes the page or moves focus; settings that save as they change show that they saved. |
| 3.2.6 Consistent Help (Level A) Understanding 3.2.6 | Web: Supports | Web: Help and support are in the same place on every page: the account menu. |
| 3.3.1 Error Identification (Level A) Understanding 3.3.1 | Web: Supports | Web: Errors are named in words beside the field they concern and tied to it for assistive technology. |
| 3.3.2 Labels or Instructions (Level A) Understanding 3.3.2 | Web: Supports | Web: Every field has a visible label or a name, and required fields and formats are stated. |
| 3.3.7 Redundant Entry (Level A) Understanding 3.3.7 | Web: Supports | Web: Nothing already entered in a process is asked for again. |
| 4.1.1 Parsing (obsolete in WCAG 2.2) (Level A) Understanding 4.1.1 | Web: Supports | Web: Obsolete in WCAG 2.2 and always satisfied for HTML content, per the W3C errata to WCAG 2.0 and 2.1. |
| 4.1.2 Name, Role, Value (Level A) Understanding 4.1.2 | Web: Supports | Web: Custom controls expose their role, name, state and value: menus, tabs, switches, comboboxes, the sheet grid (which also says each cell and its value as it moves) and the slide editor. |
WCAG 2.2 Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) Understanding 1.2.4 | Web: Not Applicable | Web: Strata has no prerecorded audio or video. Voice mode speaks answers that are also written in the conversation. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) Understanding 1.2.5 | Web: Not Applicable | Web: Strata has no prerecorded audio or video. Voice mode speaks answers that are also written in the conversation. |
| 1.3.4 Orientation (Level AA) Understanding 1.3.4 | Web: Supports | Web: No page is locked to portrait or landscape. |
| 1.3.5 Identify Input Purpose (Level AA) Understanding 1.3.5 | Web: Supports | Web: Fields about the person filling them in say what they are for: the sign-in email, the profile name and nickname, and the organization name during setup. |
| 1.4.3 Contrast (Minimum) (Level AA) Understanding 1.4.3 | Web: Partially Supports Electronic Docs: Partially Supports | Web: Text meets 4.5:1 (3:1 when large) in the light and dark themes, with two exceptions, both in the light theme. Text in the brand gold (links, and a few buttons and values drawn as links) is 2.8 to 2.9:1 on the white and off-white grounds. The person's own messages are white on a gold bubble, 2.3 to 2.8:1. In the dark theme both meet the ratio. Electronic Docs: Body text and table headers meet the ratio. A palette accent used as text (the gold of the Finance palette) can fall under it. |
| 1.4.4 Resize Text (Level AA) Understanding 1.4.4 | Web: Supports | Web: Text resizes to 200 percent with browser zoom without loss of content or function; layouts reflow. |
| 1.4.5 Images of Text (Level AA) Understanding 1.4.5 | Web: Supports Electronic Docs: Supports | Web: No images of text are used for interface text. Electronic Docs: Generated files contain text as text. |
| 1.4.10 Reflow (Level AA) Understanding 1.4.10 | Web: Supports | Web: At 320 CSS pixels wide the pages reflow to one column with no horizontal scrolling of the page. Content that needs two dimensions (data tables, code, spreadsheet previews, the schema map) scrolls within its own box. |
| 1.4.11 Non-text Contrast (Level AA) Understanding 1.4.11 | Web: Partially Supports | Web: Focus indicators, switches, checkboxes and chosen states meet 3:1. Not met: the hairline borders of some text fields are lighter than 3:1 (each field also has its label), and in the light theme four of the eight chart colours (gold, blue, green and teal) are 2.3 to 2.8:1 against white; a point's value shows when it is hovered or focused, and the chart's numbers are in its table for screen readers. |
| 1.4.12 Text Spacing (Level AA) Understanding 1.4.12 | Web: Partially Supports | Web: With the WCAG text spacing applied (line height 1.5, paragraph spacing 2, letter spacing 0.12 and word spacing 0.16 times the font size) on every screen the audit drove at the desktop size, running text, messages and the labels of form fields are read whole. Titles in the sidebar, the inbox and the conversation header that no longer fit show in full on hover and on keyboard focus, and many other names, values and descriptions cut short show in full in a tooltip. Not met: some names and short captions drawn on one line in a narrow place are cut short with no way to read the rest, among them file names on the file cards of an answer and in the workspace's Outputs list, the names in the API key and knowledge site lists, model names and descriptions in the model catalog, the second line of an entry in the mention menu, the Columns and Relations captions in the schema map's table details and the query line of a Jira search. Text in a spreadsheet preview cell stops at the column's edge, as in the workbook, and shows whole in the formula bar. |
| 1.4.13 Content on Hover or Focus (Level AA) Understanding 1.4.13 | Web: Supports | Web: Tooltips open on hover and on focus, close with Escape without moving focus, can be hovered, and stay until dismissed or the pointer or focus leaves. Popovers follow the same rules. |
| 2.4.5 Multiple Ways (Level AA) Understanding 2.4.5 | Web: Supports | Web: Pages are reached from the sidebar, from search (Ctrl or Cmd with K) and by address. |
| 2.4.6 Headings and Labels (Level AA) Understanding 2.4.6 | Web: Supports | Web: Headings and labels describe their topic or purpose. |
| 2.4.7 Focus Visible (Level AA) Understanding 2.4.7 | Web: Supports | Web: A neutral focus ring, 10:1 on the page in light and 12.8:1 in dark, marks the control with keyboard focus. Controls that appear on hover (the actions under each message) appear on keyboard focus too, and controls hidden from sight (a closed panel, a hidden button) leave the tab order. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA) Understanding 2.4.11 | Web: Supports | Web: On every screen the audit drove at the desktop size, tabbing through its first 40 stops, no control with keyboard focus was entirely hidden. The message box and the Save bar of the agent form, which stay on screen as the page scrolls, keep the control with focus scrolled clear of them; a dialog or an expanded preview over the page keeps focus inside it; a search list closes as Tab moves on. A popover the person opens and leaves open (the microphone picker) can cover a control until Escape closes it, which does not move focus. |
| 2.5.7 Dragging Movements (Level AA) Understanding 2.5.7 | Web: Partially Supports | Web: Not met: some arrangements are made by dragging, or from the keyboard, with no single-pointer alternative: the sidebar's width (it also collapses and opens with one click), moving and sizing objects in the slide editor, the order of slides and of checklist items, and moving tables on the schema map. Ordering the answers to a question has Move up and Move down buttons. |
| 2.5.8 Target Size (Minimum) (Level AA) Understanding 2.5.8 | Web: Supports | Web: Targets are at least 24 by 24 CSS pixels or have that much space around them. Exception used: a link in a spreadsheet preview cell keeps the workbook's own row height. |
| 3.1.2 Language of Parts (Level AA) Understanding 3.1.2 | Web: Partially Supports | Web: Not met: when the assistant answers in a language other than the interface language, the answer is not marked with its language. |
| 3.2.3 Consistent Navigation (Level AA) Understanding 3.2.3 | Web: Supports | Web: The sidebar and page headers are in the same place and order on every page. |
| 3.2.4 Consistent Identification (Level AA) Understanding 3.2.4 | Web: Supports | Web: The same functions carry the same names and icons throughout. |
| 3.3.3 Error Suggestion (Level AA) Understanding 3.3.3 | Web: Supports | Web: Error messages say what to change, with the accepted range or format. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Understanding 3.3.4 | Web: Supports | Web: Billing changes, deletions and anything sent or changed on the person's behalf are confirmed before they happen. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA) Understanding 3.3.8 | Web: Supports | Web: Strata asks for no password and sets no cognitive test: people sign in with Microsoft, Google or their organization's single sign-on, whose pages allow paste and password managers. |
| 4.1.3 Status Messages (Level AA) Understanding 4.1.3 | Web: Supports | Web: Status messages are announced without moving focus: saving and saved states, notifications, counts, the end of each answer ("Strata's answer is ready", or the error), and the position of a reordered answer. |
WCAG 2.2 Level AAA
Level AAA criteria were not evaluated.
Revised Section 508
Chapter 3: Functional Performance Criteria
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Partially Supports | Supported through the semantics, names and keyboard operation in the WCAG table, without testing by people who use screen readers. Exceptions: dashboard pages and diagrams the assistant builds, and PDF files, which are not tagged. |
| 302.2 With Limited Vision | Partially Supports | Zoom to 200 percent, reflow at 320 CSS pixels, light and dark themes. Exceptions: brand gold link text and the person's own message bubble in the light theme (1.4.3), and some names cut short when text spacing is widened (1.4.12). |
| 302.3 Without Perception of Color | Partially Supports | Information is never carried by colour alone, except the series of a multi-series chart (1.4.1). |
| 302.4 Without Hearing | Supports | No information is given by sound alone; voice mode writes what it says. |
| 302.5 With Limited Hearing | Supports | As 302.4. |
| 302.6 Without Speech | Supports | Speech is never required; voice mode is optional and every function is available by typing. |
| 302.7 With Limited Manipulation | Partially Supports | Every function works from the keyboard. Exceptions: some arrangements need a drag or the keyboard (2.5.7), and two time limits cannot be extended (2.2.1). |
| 302.8 With Limited Reach and Strength | Supports | No physical reach or strength is involved. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Partially Supports | Plain language, consistent navigation and help, errors that say what to change. Exception: a question the assistant asks during an answer waits only 90 seconds (2.2.1). |
Chapter 4: Hardware
Not applicable: Strata is software.
Chapter 5: Software
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 501.1 Scope – Incorporation of WCAG 2.0 AA | Supports | Strata is web content and the Microsoft Outlook add-in is web content running in Outlook; both are reported against WCAG in the tables above. |
| 502 Interoperability with Assistive Technology | Not Applicable | Strata is web content (501.1). |
| 502.2.1 User Control of Accessibility Features | Not Applicable | Web content (501.1). |
| 502.2.2 No Disruption of Accessibility Features | Not Applicable | Web content (501.1). |
| 502.3 Accessibility Services | Not Applicable | Web content (501.1). |
| 502.3.1 Object Information | Not Applicable | See WCAG 4.1.2. |
| 502.3.2 Modification of Object Information | Not Applicable | See WCAG 4.1.2. |
| 502.3.3 Row, Column, and Headers | Not Applicable | See WCAG 1.3.1. |
| 502.3.4 Values | Not Applicable | See WCAG 4.1.2. |
| 502.3.5 Modification of Values | Not Applicable | See WCAG 4.1.2. |
| 502.3.6 Label Relationships | Not Applicable | See WCAG 1.3.1 and 4.1.2. |
| 502.3.7 Hierarchical Relationships | Not Applicable | See WCAG 1.3.1. |
| 502.3.8 Text | Not Applicable | See WCAG 4.1.2. |
| 502.3.9 Modification of Text | Not Applicable | See WCAG 4.1.2. |
| 502.3.10 List of Actions | Not Applicable | See WCAG 4.1.2. |
| 502.3.11 Actions on Objects | Not Applicable | See WCAG 4.1.2. |
| 502.3.12 Focus Cursor | Not Applicable | See WCAG 2.4.7. |
| 502.3.13 Modification of Focus Cursor | Not Applicable | See WCAG 2.4.3. |
| 502.3.14 Event Notification | Not Applicable | See WCAG 4.1.3. |
| 502.4 Platform Accessibility Features | Not Applicable | Web content (501.1). |
| 503 Applications | Not Applicable | Web content (501.1). |
| 503.2 User Preferences | Not Applicable | Web applications are excepted. Strata follows the system light or dark appearance and the reduce-motion setting. |
| 503.3 Alternative User Interfaces | Not Applicable | Strata provides no alternative user interface that works as assistive technology. |
| 503.4 User Controls for Captions and Audio Description | Not Applicable | No video or synchronized media. |
| 503.4.1 Caption Controls | Not Applicable | No video or synchronized media. |
| 503.4.2 Audio Description Controls | Not Applicable | No video or synchronized media. |
| 504 Authoring Tools | Partially Supports | Strata writes documents (PDF, Word, Excel, PowerPoint) for people and edits them in place, so it is reported as an authoring tool. |
| 504.2 Content Creation or Editing | Partially Supports | The editors are operable as reported in the WCAG table. What they write: Word files with headings and header rows; PowerPoint files whose slide titles are text boxes; untagged PDF files. |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Partially Supports | Headings and header rows are kept when a Word document is edited. Converting to PDF loses them, since PDFs are not tagged. |
| 504.2.2 PDF Export | Does Not Support | PDF export is not PDF/UA (ISO 14289-1): the files are not tagged. |
| 504.3 Prompts | Does Not Support | A review checks each generated file for layout problems; it does not prompt for accessibility (alternative text, headings, contrast). |
| 504.4 Templates | Partially Supports | The built-in palettes and an organization's own templates are used as given; their accessibility depends on them (the Finance palette's gold accent is under 4.5:1 as text). |
Chapter 6: Support Documentation and Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 601.1 Scope | Supports | Heading. |
| 602 Support Documentation | Supports | Heading. |
| 602.2 Accessibility and Compatibility Features | Supports | The documentation lists the keyboard operation of every surface (Keyboard shortcuts) and the accessibility statement lists the features and limitations. |
| 602.3 Electronic Support Documentation | Supports | The documentation site was checked with axe-core against WCAG 2.2 A and AA (424 page views, desktop and phone, light and dark). |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | All documentation is electronic. |
| 603 Support Services | Supports | Heading. |
| 603.2 Information on Accessibility and Compatibility Features | Supports | Support answers questions about accessibility features by email (accessibility@kronisys.com, support@kronisys.com) and from the support panel in Strata. |
| 603.3 Accommodation of Communication Needs | Supports | Support is by written messages, by email or in the product. |
EN 301 549
Clause 4: Functional Performance Statements
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 4.2.1 Usage without vision | Partially Supports | Supported through the semantics, names and keyboard operation in the WCAG table, without testing by people who use screen readers. Exceptions: dashboard pages and diagrams the assistant builds, and PDF files, which are not tagged. |
| 4.2.2 Usage with limited vision | Partially Supports | Zoom to 200 percent, reflow at 320 CSS pixels, light and dark themes. Exceptions: brand gold link text and the person's own message bubble in the light theme (1.4.3), and some names cut short when text spacing is widened (1.4.12). |
| 4.2.3 Usage without perception of colour | Partially Supports | Information is never carried by colour alone, except the series of a multi-series chart (1.4.1). |
| 4.2.4 Usage without hearing | Supports | No information is given by sound alone; voice mode writes what it says. |
| 4.2.5 Usage with limited hearing | Supports | As 302.4. |
| 4.2.6 Usage with no or limited vocal capability | Supports | Speech is never required; voice mode is optional and every function is available by typing. |
| 4.2.7 Usage with limited manipulation or strength | Partially Supports | Every function works from the keyboard. Exceptions: some arrangements need a drag or the keyboard (2.5.7), and two time limits cannot be extended (2.2.1). |
| 4.2.8 Usage with limited reach | Supports | No physical reach or strength is involved. |
| 4.2.9 Minimize photosensitive seizure triggers | Supports | Nothing flashes (WCAG 2.3.1). |
| 4.2.10 Usage with limited cognition, language or learning | Partially Supports | Plain language, consistent navigation and help, errors that say what to change. Exception: a question the assistant asks during an answer waits only 90 seconds (2.2.1). |
| 4.2.11 Privacy | Supports | Strata collects nothing about the use of accessibility features. |
Clause 5: Generic Requirements
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 5.1 Closed functionality | Not Applicable | Strata is not closed functionality: it runs in a browser or in Outlook, where people use their own assistive technology. |
| 5.2 Activation of accessibility features | Supports | The light and dark themes and the language are chosen in Settings; reduced motion follows the operating system. |
| 5.3 Biometrics | Not Applicable | Strata does not use biometrics. Sign-in providers may offer them, alongside other methods. |
| 5.4 Preservation of accessibility information during conversion | Partially Supports | As 504.2.1: converting to PDF does not keep headings or table structure. |
| 5.5.1 Means of operation | Not Applicable | No hardware operable parts. |
| 5.5.2 Operable parts discernibility | Not Applicable | No hardware operable parts. |
| 5.6.1 Tactile or auditory status | Not Applicable | No locking or toggle keys. |
| 5.6.2 Visual status | Not Applicable | No locking or toggle keys. |
| 5.7 Key repeat | Not Applicable | Key repeat is the operating system's. |
| 5.8 Double-strike key acceptance | Not Applicable | Key acceptance is the operating system's. |
| 5.9 Simultaneous user actions | Supports | No function needs simultaneous actions: pinch zoom has zoom buttons beside it. |
Clauses 6, 7 and 8
Not applicable: Strata has no two-way voice communication between people (6), no video (7) and no hardware (8).
Clause 9: Web
Reported in the WCAG 2.2 tables, under Web.
Clause 10: Non-web Documents
Reported in the WCAG 2.2 tables, under Electronic Docs, for the files Strata generates.
Clause 11: Software
Strata is web content, reported under Clause 9. Its authoring features are reported here.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 11.5.2 Accessibility services | Not Applicable | Web content: see Clause 9 (the WCAG table). |
| 11.6 Documented accessibility usage | Not Applicable | Web content: see Clause 9. |
| 11.7 User preferences | Not Applicable | Web content: see Clause 9. |
| 11.8 Authoring tools | Partially Supports | Strata writes documents (PDF, Word, Excel, PowerPoint) for people and edits them in place, so it is reported as an authoring tool. |
| 11.8.1 Content technology | Partially Supports | Word and PowerPoint can carry the accessibility information their formats support; Strata's PDFs are not tagged. |
| 11.8.2 Accessible content creation | Partially Supports | The editors are operable as reported in the WCAG table. What they write: Word files with headings and header rows; PowerPoint files whose slide titles are text boxes; untagged PDF files. |
| 11.8.3 Preservation of accessibility information in transformations | Partially Supports | Headings and header rows are kept when a Word document is edited. Converting to PDF loses them, since PDFs are not tagged. |
| 11.8.4 Repair assistance | Does Not Support | A review checks each generated file for layout problems; it does not prompt for accessibility (alternative text, headings, contrast). |
| 11.8.5 Templates | Partially Supports | The built-in palettes and an organization's own templates are used as given; their accessibility depends on them (the Finance palette's gold accent is under 4.5:1 as text). |
Clause 12: Documentation and Support Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 12.1.1 Accessibility and compatibility features | Supports | The documentation lists the keyboard operation of every surface (Keyboard shortcuts) and the accessibility statement lists the features and limitations. |
| 12.1.2 Accessible documentation | Supports | The documentation site was checked with axe-core against WCAG 2.2 A and AA (424 page views, desktop and phone, light and dark). |
| 12.2.2 Information on accessibility and compatibility features | Supports | Support answers questions about accessibility features by email (accessibility@kronisys.com, support@kronisys.com) and from the support panel in Strata. |
| 12.2.3 Effective communication | Supports | Support is by written messages, by email or in the product. |
| 12.2.4 Accessible documentation | Supports | Documentation that support refers to is the same accessible documentation site (12.1.2). |
Clause 13: ICT Providing Relay or Emergency Service Access
Not applicable.
Known gaps and next steps
- Tagged PDF output (PDF/UA), slide titles in title placeholders, and text alternatives for charts in generated files.
- A way to give more time to an approval or a question the assistant asks during an answer, and a warning before a session ends.
- Single-pointer alternatives for the arrangements that need a drag (2.5.7).
- Chart colours and link text that meet their contrast ratios in the light theme (1.4.3, 1.4.11).
- Marking the language of an answer written in another language.
- The whole text, on hover and on keyboard focus, wherever wider text spacing cuts off a name or a caption (1.4.12), and file cards in answers that open their preview from the keyboard (today the workspace’s Outputs list does).
- Testing with screen readers by people who use them, and a third-party audit.
Report an accessibility problem to accessibility@kronisys.com; it is handled as a defect.
Legal disclaimer
This report describes the accessibility of Strata as evaluated on the date above, based on the methods described. It is provided for information, is not a warranty, and may change as Strata changes. “VPAT” is a registered service mark of the Information Technology Industry Council (ITI).