Accessibility Statement

Last updated: 2026-06-24

This statement covers the CISO Assistant application — the product you log into and use — not this marketing website (intuitem.com). It documents the accessibility review and ongoing tracking of the application itself.

Our commitment

We are committed to making CISO Assistant accessible to as many people as possible, regardless of ability or technology. Accessibility is an ongoing part of how we build the product, not a one-time exercise. CISO Assistant evolves continuously, with new pages and features released regularly, so our accessibility testing is a continuous activity: new and changed screens are assessed as they ship, and this statement is updated to reflect the current state.

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, level AA, and we align our work with the automatable criteria of the French Référentiel Général d’Amélioration de l’Accessibilité (RGAA).

Current status

Partial conformance — actively improving.

CISO Assistant is not yet fully conformant with WCAG 2.1 AA or RGAA. We have established automated accessibility testing and are progressively addressing issues, but a full manual audit has not yet been completed. This statement will be updated as that work progresses.

What we have done

• Automated testing in the development pipeline. We run axe-core (the W3C-ACT-recognized accessibility engine) against WCAG 2.1 A and AA on representative user journeys, covering authentication, dashboards, data tables, detail views, create/edit forms and dialogs, and specialized analysis views.
• Component-level fixes. We have resolved labeling, accessible-name, and document-structure issues in shared form, table, navigation, and dialog components. Because these are shared building blocks, the improvements apply consistently across the application.
• Current automated result. The tested screens report no outstanding automated violations at the WCAG 2.1 AA level, in both the light and dark themes.

Known limitations

Automated testing validates only part of the applicable criteria (roughly a third of WCAG success criteria can be fully checked automatically). The following areas have not yet been fully evaluated and may contain accessibility barriers:

• Keyboard-only navigation and visible focus order in some interactive components (dialogs, menus, command palette).
• Screen-reader behavior for dynamically updated content (notifications, live status, focus handling in modals).
• Content reflow at very narrow widths / high zoom (WCAG 1.4.10). The application is designed for desktop and laptop screens and is optimized for a viewport of at least 1024px wide. It does not currently reflow without horizontal scrolling down to 320px (equivalent to 400% zoom on a small screen). Within the supported range, tested screens do not introduce horizontal overflow.
• Some complex views (risk matrix grid, assessment tree editor, guided workshops) and embedded data visualizations, in either theme.
• Generated documents (e.g. exported PDF reports).

We are prioritizing a manual audit to evaluate these areas against the full set of WCAG 2.1 AA / RGAA criteria.

Scope

This statement covers the CISO Assistant web application (Community edition), which is designed for desktop and laptop use (viewport width ≥ 1024px). It does not cover this marketing website (intuitem.com), which is a separate property. Functionality specific to other editions, third-party embedded content, and user-uploaded files are also not covered.

Feedback and contact

If you encounter an accessibility barrier, or need information in an alternative format, please tell us — your feedback helps us prioritize:

• Email: contact@intuitem.com
• Issue tracker: https://github.com/intuitem/ciso-assistant-community/issues

We aim to respond within 5 business days.

Assessment method

The current status is based on automated evaluation using axe-core against WCAG 2.1 levels A and AA, run against representative screens of the application in both light and dark themes, plus a horizontal-overflow check at the minimum supported width (1024px). A full manual evaluation is planned and will be reflected here once completed.

Automated test evidence

Snapshot: 2026-06-25. Tool: axe-core (WCAG 2.1 A & AA), light and dark themes. Horizontal overflow checked at the 1024px minimum supported width.

Result: 20/20 screens passed automated checks with no critical or serious violations.

axe-core, cumulative across screens: 574 checks passed, 0 failed, 21 flagged for manual review.

Results by screen