Product policies · review draft

Accessibility

INSIPS accessibility approach, supported interaction patterns and how to report a barrier.

Draft for operator and legal review · 15 October 2026

These substantive drafts explain the current product. They are not final approved legal terms or a claim of compliance.

Our approach

INSIPS aims to make public discovery and workspaces usable with keyboards, assistive technology, touch and different screen sizes. The design work targets WCAG 2.2 AA principles; this is a goal, not a claim that every screen is independently certified or free of barriers.

Interaction and reading

Pages use meaningful headings, labelled controls, visible focus and error feedback. Important touch controls aim for at least 44 by 44 CSS pixels, with larger primary controls where practical. Responsive layouts, light and dark themes, and reduced-motion preferences are supported. Charts should have labels or accompanying values rather than rely on color alone.

Known limitations

Third-party provider pages, complex Flutter Web semantics, media descriptions supplied by content authors and some dense workspace tables need ongoing review. Not every page, browser or assistive-technology combination has been independently tested. Report the exact route and interaction rather than assume a passing automated check proves full accessibility.

Report a barrier

Contact support@insips.com with the page URL, device/browser, optional assistive technology and the task you could not complete. Do not include passwords or private documents. We can investigate the issue and discuss an alternative support route without promising an unsupported response deadline.

support@insips.com