Accessibility

Our commitment

Sentia Labs builds software that product teams use for hours at a time. We want every one of those people to be able to use it, including people who navigate by keyboard, use a screen reader, magnify the interface, need higher contrast, or are affected by motion. This statement covers the Sentia web application and the sentialabs.ai website.

Conformance status

We treat an accessibility defect as a defect rather than as an enhancement request. A conformance report reflecting our own assessment is available on request, including for procurement and vendor review, from hello@sentialabs.ai.

What we have built in

These are properties of the shipped interface, enforced by our component library and our review process rather than applied page by page.

• Keyboard and focus. Every interactive element is semantic HTML and carries a visible focus indicator. Overlays, menus, dialogs, and comboboxes are built on accessible primitives that we style rather than reimplement. On navigation, focus moves to the main content region, and in multi-step flows to the heading of the new step. Keyboard shortcuts are consistent and discoverable through an in-app overlay.
• Screen readers and structure. Each page has exactly one level-one heading and does not skip heading levels. Icon-only buttons carry accessible labels, form inputs have visible labels, and content that changes without a page load is announced through live regions. Toggled states such as sort direction are conveyed visually as well as through ARIA.
• Color and contrast. Color is never the only carrier of meaning, and status and category indicators always keep a text label. Contrast for every foreground and background pairing is asserted by automated tests in both the light and the dark theme.
• Motion. The prefers-reduced-motion setting is honored throughout, including in charts. Loading indicators swap rotation for an opacity pulse rather than freezing, so they still signal that work is in progress.
• Data and charts. Charts carry a text summary, custom visualizations carry a screen-reader-only data table of the underlying values, and tables use proper header semantics and an accessible name.

Automated accessibility testing runs in our end-to-end suite against the running application. Because automated testing catches only a minority of accessibility problems, it is supplemented by manual keyboard-only walkthroughs of the primary flows and by review before a change ships.

Known limitations

Sentia is a desktop application, designed for viewports of 1024 pixels and wider. That is a deliberate product decision about a dense analytical workspace, and it is a limitation for anyone who relies on a small screen or on high levels of zoom. Alongside it:

• Some data visualizations remain difficult to interpret without sight of the graphic. Text summaries and data tables mitigate this but do not fully replace it.
• Content supplied by customers, including uploaded documents, transcripts, screenshots, and prototype pages rendered inside the product, is outside our control. We cannot guarantee the accessibility of material we did not author.
• Third-party components that we embed conform to their own vendors' standards rather than to ours.
• This statement reflects our own assessment and testing rather than an independent audit.

Tell us where we fall short

If you encounter a barrier in the Sentia application or on this website, tell us and we will fix it. Email hello@sentialabs.ai with the page or feature, what you were trying to do, what happened, and the assistive technology and browser you were using if that is relevant.

If you need information from the product in an alternative format while we resolve a barrier, ask at the same address and we will provide it.

Contact: hello@sentialabs.ai.