Accessibility Conformance Report

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 mailto\ info\@swimlane com turbine is a web only application this report covers the degree of conformance for the following accessibility standard/guidelines standard/guideline included in report https //www w3 org/wai/standards guidelines/wcag/new in 22/ 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 http //www w3 org/tr/wcag20/#text equiv all / 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 http //www w3 org/tr/wcag20/#media equiv av only alt / audio only and video only (prerecorded) 〰 not applicable the product does not use prerecorded media http //www w3 org/tr/wcag20/#media equiv captions / captions (prerecorded) 〰 not applicable the product does not use prerecorded media http //www w3 org/tr/wcag20/#media equiv audio desc / audio description or media alternative (prerecorded) 〰️not applicable the product does not use prerecorded media http //www w3 org/tr/wcag20/#content structure separation programmatic / 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 http //www w3 org/tr/wcag20/#content structure separation sequence / 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 http //www w3 org/tr/wcag20/#content structure separation understanding / 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 http //www w3 org/tr/wcag20/#visual audio contrast without color / 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 http //www w3 org/tr/wcag20/#visual audio contrast dis audio / audio control 〰 not applicable the product does not use prerecorded audio http //www w3 org/tr/wcag20/#keyboard operation keyboard operable / 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 http //www w3 org/tr/wcag20/#keyboard operation trapping / 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 https //www w3 org/tr/wcag21/#character key shortcuts / 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 http //www w3 org/tr/wcag20/#time limits required behaviors / 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 ) http //www w3 org/tr/wcag20/#time limits pause / pause, stop, hide ✅supports dashboard cards display a countdown timer that may be paused http //www w3 org/tr/wcag20/#seizure does not violate / three flashes or below threshold ✅supports the platform does not contain any component that flashes more than three times in any one second period http //www w3 org/tr/wcag20/#navigation mechanisms skip / bypass blocks 🚫does not support the platform does not offer bypass blocks http //www w3 org/tr/wcag20/#navigation mechanisms title / 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 http //www w3 org/tr/wcag20/#navigation mechanisms focus order / 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 http //www w3 org/tr/wcag20/#navigation mechanisms refs / 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 https //www w3 org/tr/wcag21/#pointer gestures / 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 https //www w3 org/tr/wcag21/#pointer cancellation / pointer cancellation ✅supports the majority of elements meet the requirement no down event , and long press to delete meets the up reversal requirement https //www w3 org/tr/wcag21/#label in name / 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 https //www w3 org/tr/wcag21/#motion actuation / motion actuation ✅supports motion is not used http //www w3 org/tr/wcag20/#meaning doc lang id / language of page ✅supports the language of pages within swimlane contain a lang attribute with the property of en http //www w3 org/tr/wcag20/#consistent behavior receive focus / on focus ✅supports a change of context is not initiated when user interface components within the platform receive focus http //www w3 org/tr/wcag20/#consistent behavior unpredictable change / 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 https //www w3 org/wai/standards guidelines/wcag/new in 22/#326 consistent help a / 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 http //www w3 org/tr/wcag20/#minimize error identified / 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 http //www w3 org/tr/wcag20/#minimize error cues / 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 https //www w3 org/wai/wcag22/understanding/redundant entry html / 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 https //www w3 org/wai/wcag22/understanding/parsing html / parsing obsolete and removed http //www w3 org/tr/wcag20/#ensure compat rsv / 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 http //www w3 org/tr/wcag20/#media equiv real time captions / captions (live) 〰 not applicable the product does not use prerecorded media http //www w3 org/tr/wcag20/#media equiv audio desc only / audio description (prerecorded) 〰 not applicable the product does not use prerecorded media https //www w3 org/tr/wcag21/#orientation / orientation ✅supports minimum dimensions are implemented, and users are notified—with ability to bypass https //www w3 org/tr/wcag21/#identify input purpose / identify input purpose 🚫does not support http //www w3 org/tr/wcag20/#visual audio contrast contrast / 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 http //www w3 org/tr/wcag20/#visual audio contrast scale / resize text ✅supports text in the product can be increased by 200% without issue using the browser zoom keyboard shortcut ctrl / command + + http //www w3 org/tr/wcag20/#visual audio contrast text presentation / images of text ✅supports the platform does not contain any images with text https //www w3 org/tr/wcag21/#reflow / 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 https //www w3 org/tr/wcag21/#non text contrast / 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) https //www w3 org/tr/wcag21/#text spacing / 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 https //www w3 org/tr/wcag21/#content on hover or focus / 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) http //www w3 org/tr/wcag20/#navigation mechanisms mult loc / multiple ways 🚫does not support the platform provides and relies on a only single navigation menu http //www w3 org/tr/wcag20/#navigation mechanisms descriptive / 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 http //www w3 org/tr/wcag20/#navigation mechanisms focus visible / 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 https //www w3 org/wai/wcag22/understanding/focus not obscured minimum html / 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 https //www w3 org/wai/wcag22/understanding/dragging movements html / dragging movements wcag 2 2 🚫does not support the application builder requires drag and drop mouse functionality and does not offer an alternative https //www w3 org/wai/wcag22/understanding/target size minimum html / 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 http //www w3 org/tr/wcag20/#meaning other lang id / 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 http //www w3 org/tr/wcag20/#consistent behavior consistent locations / 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 http //www w3 org/tr/wcag20/#consistent behavior consistent functionality / 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 http //www w3 org/tr/wcag20/#minimize error suggestions / 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 http //www w3 org/tr/wcag20/#minimize error reversible / 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 https //www w3 org/wai/wcag22/understanding/accessible authentication minimum html / 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 https //www w3 org/tr/wcag21/#status messages / 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 http //www w3 org/tr/wcag20/#media equiv sign / sign language (prerecorded) 〰 not applicable the product does not use prerecorded media http //www w3 org/tr/wcag20/#media equiv extended ad / extended audio description (prerecorded) 〰 not applicable the product does not use prerecorded media http //www w3 org/tr/wcag20/#media equiv text doc / media alternative (prerecorded) 〰 not applicable the product does not use prerecorded media http //www w3 org/tr/wcag20/#media equiv live audio only / audio only (live) 〰 not applicable the product does not use prerecorded media https //www w3 org/tr/wcag21/#identify purpose / 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 http //www w3 org/tr/wcag20/#visual audio contrast7 / 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 http //www w3 org/tr/wcag20/#visual audio contrast noaudio / low or no background audio 〰not applicable the product does not use prerecorded media http //www w3 org/tr/wcag20/#visual audio contrast visual presentation / 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 http //www w3 org/tr/wcag20/#visual audio contrast text images / images of text (no exception) ✅supports http //www w3 org/tr/wcag20/#keyboard operation all funcs / 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 http //www w3 org/tr/wcag20/#time limits no exceptions / 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 http //www w3 org/tr/wcag20/#time limits postponed / 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 http //www w3 org/tr/wcag20/#time limits server timeout / re authenticating 🚫does not support users lose all data when a user session ends and they need to re authenticate https //www w3 org/tr/wcag21/#timeouts / 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 http //www w3 org/tr/wcag20/#seizure three times / three flashes ✅supports the product does not contain anything that flashes https //www w3 org/tr/wcag21/#animation from interactions / animation from interactions 🚫does not support http //www w3 org/tr/wcag20/#navigation mechanisms location / 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 http //www w3 org/tr/wcag20/#navigation mechanisms link / 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 http //www w3 org/tr/wcag20/#navigation mechanisms headings / 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 https //www w3 org/wai/wcag22/understanding/focus not obscured enhanced html / 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 https //www w3 org/wai/wcag22/understanding/focus appearance html / focus appearance wcag 2 2 🚫does not support the majority of our focus indicators do not have a border 2px thick or wider https //www w3 org/tr/wcag21/#target size / target size 🚫does not support nearly every element failed https //www w3 org/tr/wcag21/#concurrent input mechanisms / 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 http //www w3 org/tr/wcag20/#meaning idioms / unusual words 🚫does not support the product does not have a mechanism to help users attain definitions of technical jargon and/or unusual words http //www w3 org/tr/wcag20/#meaning located / 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 http //www w3 org/tr/wcag20/#meaning supplements / 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 http //www w3 org/tr/wcag20/#meaning pronunciation / pronunciation 🚫does not support 10x has not been designed for assistive technology http //www w3 org/tr/wcag20/#consistent behavior no extreme changes context / 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 http //www w3 org/tr/wcag20/#minimize error context help / 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 http //www w3 org/tr/wcag20/#minimize error reversible all / 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 https //www w3 org/wai/wcag22/understanding/accessible authentication enhanced html / 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