Accessibility Conformance Report
-
- Test
- Name of Product/Version: Swimlane Turbine Cloud 25.3.0
- Report Date: October 2025
- Product Description: Swimlane Turbine is a low-code security automation platform. With Turbine you can prioritize alerts, re-mediate threats and improve your operational performance.
- Contact Information: [email protected]
Turbine is a web-only application.
This report covers the degree of conformance for the following accessibility standard/guidelines:
Standard/Guideline | Included in Report |
|---|---|
Level A (Yes) Level AA (Yes) Level AAA (Yes) |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
Success Criteria, Level A
Criteria | Conformance level | Remarks and explanations |
|---|---|---|
1.1.1 / Non-text Content | 🔶Partially supports | Some images that contain text are missing alt tags. Some icon button links are missing a name that describes its purpose. |
1.2.1 / Audio-only and Video-only (Prerecorded) | 〰 Not applicable | The product does not use prerecorded media. |
1.2.2 / Captions (Prerecorded) | 〰 Not applicable | The product does not use prerecorded media. |
1.2.3 / Audio Description or Media Alternative (Prerecorded) | 〰️Not applicable | The product does not use prerecorded media. |
1.3.1 / Info and Relationships | 🔶Partially supports | The platform lacks a consistent, semantic heading structure for content. Structural elements like heading levels <H1> are used but not applied to all necessary headings. In addition, the platform lacks consistent use of ARIA markup, including: Aria labels, Aria attributes, and Aria roles and landmarks. |
1.3.2 / Meaningful Sequence | 🔶Partially supports | The platform lacks a consistent semantic structure across pages, and navigation does not accurately convey the relationships between sections. As a result, content may not be presented in a meaningful sequence for users relying on assistive technologies. |
1.3.3 / Sensory Characteristics | 🔶Partially supports | Instructions generally do not mention shapes, colors, or layout-related instructions. However, tips and user notifications do not use adequately labeled context. |
1.4.1 / Use of Color | 🔶Partially supports | The platform relies on color alone to communicate information in several places. Links are identified only by color, some form errors lack accompanying text, and charts use color as the primary means of representing data. |
1.4.2 / Audio Control | 〰 Not applicable | The product does not use prerecorded audio. |
2.1.1 / Keyboard | 🔶Partially supports | Not all content or controls can be accessed with a keyboard. Navigation, dragging features, and user profile options are limited to mouse input, reducing accessibility for keyboard users. |
2.1.2 / No Keyboard Trap | 🔶Partially supports | When navigating via keyboard, there are situations when the user is both inappropriately trapped as well as inappropriately not trapped. |
2.1.4 / Character Key Shortcuts | ✅Supports | All keyboard shortcuts in the platform require two or more key combinations, rather than single-character keys, reducing the risk of accidental activation. |
2.2.1 / Timing Adjustable | 🔶Partially supports | Users have limited control over session timeouts. Admins can set global logout durations, and individual users can adjust their own session duration settings, supporting the Adjust and Extend criteria. However, users cannot fully disable time limits (Turn off). |
2.2.2 / Pause, Stop, Hide | ✅Supports | Dashboard cards display a countdown timer that may be paused. |
2.3.1 / Three Flashes or Below Threshold | ✅Supports | The platform does not contain any component that flashes more than three times in any one second period. |
2.4.1 / Bypass Blocks | 🚫Does not support | The platform does not offer bypass blocks. |
2.4.2 / Page Titled | 🔶Partially supports | Most pages have meaningful and descriptive titles. However, some pages—such as Add Role, Edit Role, Dashboards, and Application pages—lack sufficient or unique titles. |
2.4.3 / Focus Order | 🚫Does not support | Keyboard navigation does not always follow a logical or visual order. Some elements are skipped or reached out of sequence, and certain components (like dialogs and overlays) trap focus, limiting navigation. |
2.4.4 / Link Purpose (In Context) | 🔶Partially supports | The Swimlane logo, links and/or buttons only containing an icon are missing discernible description text and/or aria labels. |
2.5.1 / Pointer Gestures | ✅Supports | Only one page in the platform includes complex gestures, and all actions on that page can also be completed using standard mouse clicks. |
2.5.2 / Pointer Cancellation | ✅Supports | The majority of elements meet the requirement No Down-Event, and long-press to delete meets the Up Reversal requirement. |
2.5.3 / Label in Name | 🔶Partially supports | Most form fields include visible and programmatic labels. However, some radio button groups, toggles, and custom elements lack <label> tags. Additionally, icon buttons and other interactive graphics need descriptive labels to ensure accessibility. |
2.5.4 / Motion Actuation | ✅Supports | Motion is not used. |
3.1.1 / Language of Page | ✅Supports | The language of pages within Swimlane contain a lang attribute with the property of en. |
3.2.1 / On Focus | ✅Supports | A change of context is not initiated when user interface components within the platform receive focus. |
3.2.2 / On Input | ✅Supports | Changing the setting of user interface components does not automatically cause a change of context. Forms and input fields within the platform offer submit or save buttons where applicable. |
3.2.6 / Consistent Help WCAG 2.2 | ✅Supports | Help is consistently available across the platform. A link to self-help documentation is accessible from the user profile circle in the banner, visible on every page. |
3.3.1 / Error Identification | 🔶Partially supports | Some inputs, such as missing tracking IDs, provide clear error messages. However, many Integration related errors are too vague and offer insufficient guidance for users to correct the issue. |
3.3.2 / Labels or Instructions | 🔶Partially supports | Most traditional forms (e.g., Settings, Users) generally provide sufficient labels and instructions. However, most Integration related forms lack clear guidance, making it difficult for users to complete tasks successfully. |
3.3.7 / Redundant Entry WCAG 2.2 | 🔶Partially supports | 10x allows saving and reusing credentials and some data as “Assets,” and certain dropdowns pull from existing fields. However, these efficiencies apply to a few workflows, not all processes. |
4.1.1 / Parsing | Obsolete and removed | |
4.1.2 / Name, Role, Value | 🔶Partially supports | Form elements are generally labeled and linked using the for attribute, though not universally. aria-label is applied only when standard labeling conventions cannot be used. We avoid unnecessary wai-aria attributes, as form values should be readable without additional intervention—except when implementing custom form fields. |
Success Criteria, Level AA
Criteria | Conformance level | Remarks and explanations |
|---|---|---|
1.2.4 / Captions (Live) | 〰 Not applicable | The product does not use prerecorded media. |
1.2.5 / Audio Description (Prerecorded) | 〰 Not applicable | The product does not use prerecorded media. |
1.3.4 / Orientation | ✅Supports | Minimum dimensions are implemented, and users are notified—with ability to bypass. |
1.3.5 / Identify Input Purpose | 🚫Does not support | |
1.4.3 / Contrast (Minimum) | 🔶Partially supports | Most large text meets the required 3:1 contrast ratio, but many regular text elements fail to meet the 4.5:1 ratio. |
1.4.4 / Resize text | ✅Supports | Text in the product can be increased by 200% without issue using the browser zoom keyboard shortcut Ctrl/Command + +. |
1.4.5 / Images of Text | ✅Supports | The platform does not contain any images with text. |
1.4.10 / Reflow | 🔶Partially supports | The platform relies on both horizontal and vertical scrolling under normal conditions and is not fully responsive. At 400% zoom, most pages fail to reflow properly, resulting in clipped content and reduced navigability. |
1.4.11 / Non-text Contrast | 🔶Partially supports | Many UI elements do not meet the required 3:1 contrast ratio. Key elements failing the criterion include form fields with error indicators (red error lines), icons in non-selected navigation items, and content within the condition builder (e.g., close buttons). |
1.4.12 / Text Spacing | 🔶Partially supports | Line height meets the criterion in some areas but not consistently (e.g., navigation submenu items, buttons, and search text). Spacing after paragraphs, letter spacing, and word spacing are not supported. Text truncation partially supports the criterion, but at 300% zoom, enlarged text is cut off rather than truncated with a mechanism to reveal the full content. |
1.4.13 / Content on Hover or Focus | 🔶Partially supports | The majority of content triggered on hover, such as tooltips remain visible if the user were to hover over the element. However, that is not true for all situations (such as hover actions inside the App Builder). |
2.4.5 / Multiple Ways | 🚫Does not support | The platform provides and relies on a only single navigation menu. |
2.4.6 / Headings and Labels | 🔶Partially supports | Some HTML headings are used inappropriately (two or more H1s on a page), and some inputs do not have labels. |
2.4.7 / Focus Visible | 🔶Partially supports | Most form controls display a visible focus state, but some UI elements lack clear focus indicators. In some cases, only part of a component (e.g., the radio button circle) is highlighted instead of the entire interactive element. |
2.4.11 / Focus Not Obscured (Minimum) WCAG 2.2 | 🔶Partially supports | Keyboard navigation sometimes does not display a visible focus indicator, making it difficult to determine which element is in focus. The platform partially meets 2.4.7, which this criterion builds upon, and does not fully ensure focus visibility or 3:1 contrast for in-focus elements. |
2.5.7 / Dragging Movements WCAG 2.2 | 🚫Does not support | The Application builder requires drag and drop mouse functionality and does not offer an alternative. |
2.5.8 / Target Size (Minimum) WCAG 2.2 | 🔶Partially supports | Most clickable elements meet the minimum 24×24 px target size, but some elements have smaller targets, down to 6.5x6.5 px, which hinders accessibility. |
3.1.2 / Language of Parts | 🚫Does not support | We currently support English only. For custom widgets or charts containing user-supplied content in other languages, accessibility support is not provided. |
3.2.3 / Consistent Navigation | ✅Supports | Navigation is consistently positioned across the platform. It can expand or collapse, but only when the user manually selects the expand/collapse control. |
3.2.4 / Consistent Identification | 🔶Partially supports | Icons are generally used consistently. However, there are many places where icons either do not have any alt text, or do not have consistent alt text. |
3.3.3 / Error Suggestion | 🔶Partially supports | Many errors lack specific and descriptive information to help the user correct the issue. This is especially troublesome with Integrations. Suggestions are frequently not provided to users. |
3.3.4 / Error Prevention | 🔶Partially supports | Forms are checked for input errors, and in some cases a review mechanism is provided before submitting forms. In situations where the user is navigating via keyboard, there are situations when hitting the enter key submits the form, rather than selects an option within the dropdown. |
3.3.8 / Accessible Authentication (Minimum) WCAG 2.2 | 🔶Partially supports | Authentication supports autofill and password managers and avoids CAPTCHAs, improving accessibility. Basic authentication successfully meets criteria. Two-factor authentication (2FA) could be more accessible—TOTP codes require manual transcription, and QR-based setup may be inaccessible to users with visual, physical, or cognitive impairments. |
4.1.3 / Status Messages | 🚫Does not support | We don't use role="status", role="marquee" , or aria-atomic at all. |
Success Criteria, Level AAA
Criteria | Conformance level | Remarks and explanations |
|---|---|---|
1.2.6 / Sign Language (Prerecorded) | 〰 Not applicable | The product does not use prerecorded media. |
1.2.7 / Extended Audio Description (Prerecorded) | 〰 Not applicable | The product does not use prerecorded media. |
1.2.8 / Media Alternative (Prerecorded) | 〰 Not applicable | The product does not use prerecorded media. |
1.2.9 / Audio-only (Live) | 〰 Not applicable | The product does not use prerecorded media. |
1.3.6 / Identify Purpose | 🔶Partially supports | 1.3.6 builds upon 1.3.5 which we do not support. Specific to 1.3.6, icons are missing text for assisted technologies. We do identify some regions of the page for screen readers. |
1.4.6 / Contrast (Enhanced) | 🔶Partially supports | Most large text meets the 4.5:1 ratio requirement. Some regular text meets the 7:1 ratio, including tooltips and chart titles. However the majority of text elements do not meet the enhanced contrast requirement. |
1.4.7 / Low or No Background Audio | 〰Not applicable | The product does not use prerecorded media. |
1.4.8 / Visual Presentation | 🚫Does not support | The platform does not provide mechanisms for users to adjust text presentation to meet their needs. Features such as changing text or background color, controlling text width, adjusting alignment, or modifying line and paragraph spacing are not supported either natively or through browser settings. |
1.4.9 / Images of Text (No Exception) | ✅Supports | |
2.1.3 / Keyboard (No Exception) | 🔶Partially supports | Some platform elements, including navigation, are not fully operable via keyboard. Drag-and-drop functionality also requires a mouse, preventing complete keyboard accessibility. |
2.2.3 / No Timing | 🔶Partially supports | No features rely on timing for completion and dashboard cards with auto-refresh enabled have controls for time-related functionality. However, some alerts and notifications are time sensitive, and cannot be paused. |
2.2.4 / Interruptions | 🔶Partially supports | Users can enable or disable in-app notifications, but there is no option to control the timing or frequency of these notifications. Adding features like “pause,” “snooze,” or scheduling notification delivery would improve compliance. |
2.2.5 / Re-authenticating | 🚫Does not support | Users lose all data when a user session ends and they need to re-authenticate. |
2.2.6 / Timeouts | 🚫Does not support | Users are warned about session timeouts ~30 seconds before expiration and can extend the session. However, if they miss the warning, unsaved data may be lost, and sessions cannot resume where they left off. There’s also no notification when users sign back in after a timeout. |
2.3.2 / Three Flashes | ✅Supports | The product does not contain anything that flashes. |
2.3.3 / Animation from Interactions | 🚫Does not support | |
2.4.8 / Location | 🔶Partially supports | The product does not currently include breadcrumb navigation or a sitemap. HTML headings are used but not always applied consistently or in a clearly meaningful hierarchy. It’s unclear whether ARIA landmarks are implemented consistently across all pages. |
2.4.9 / Link Purpose (Link Only) | 🔶Partially supports | Many links in the platform use vague text (e.g., “Delete,” “Email,” “Configure”) or icon-only buttons, making it unclear where they lead when read out of context. All links require clear, descriptive text to meet this criterion. |
2.4.10 / Section Headings | 🔶Partially supports | The platform uses headings inconsistently, which can hinder navigation with assistive technologies. Some pages have multiple H1 elements, while other sections are missing HTML headings altogether. |
2.4.12 / Focus Not Obscured (Enhanced) WCAG 2.2 | 🔶Partially supports | 10x has minimal sticky elements, and when users navigate via keyboard, the focus moves the page with the keyboard so focused elements are typically not obscured. However, there are a few instances of cursor focus that may become obscured by popover UI elements. |
2.4.13 / Focus Appearance WCAG 2.2 | 🚫Does not support | The majority of our focus indicators do not have a border 2px thick or wider. |
2.5.5 / Target Size | 🚫Does not support | Nearly every element failed. |
2.5.6 / Concurrent Input Mechanisms | 🔶Partially supports | The platform primarily supports mouse input. Keyboard interactions are partially supported, while touch and voice input are not currently supported, limiting users who rely on alternative input methods. |
3.1.3 / Unusual Words | 🚫Does not support | The product does not have a mechanism to help users attain definitions of technical jargon and/or unusual words. |
3.1.4 / Abbreviations | 🔶Partially supports | In some places, users can see an abbreviation directly next to its full length word. However, in places where the full word is not visible, users do not have a mechanism to see it. |
3.1.5 / Reading Level | 🚫Does not support | 10x contains a lot of technical processes, technical terminology, and profession-specific language. In addition, there are complicated processes without clear explanations or supplemental information, like illustrations, or summaries. |
3.1.6 / Pronunciation | 🚫Does not support | 10x has not been designed for assistive technology. |
3.2.5 / Change on Request | 🔶Partially supports | Most changes are user-initiated. However, there are times when changes occur without user initiation. Some situations include: viewing co-edited Records and clicking on specific links. |
3.3.5 / Help | 🚫Does not support | Users should have access to in-line help. In-line help can be in the form of a description, tooltip, or a link to context-specific information. The majority (90%+) of forms do not have descriptions or links to contextual information. Orchestration is probably the area users need the most guidance. Many fields have their type (string, number, boolean, etc.) listed but they do not have in-line help. Some fields have in-line tooltips, but they don’t typically give the user enough information to act on. |
3.3.6 / Error Prevention (All) WCAG 2.2 | 🔶Partially supports | Not all user-submitted forms provide clear, actionable error messages. Some forms may submit unexpectedly when navigating via keyboard (e.g., pressing Enter in a dropdown), without a confirmation prompt or a way to reverse the submission. |
3.3.9 / Accessible Authentication (Enhanced) WCAG 2.2 | 🔶Partially supports | Criterion requires login to be as easy as possible and have no cognition tests. Basic authentication: Supports 2Factor authentication: Does not support |