Accessibility

Last updated July 26, 2026

Core is built for public-sector and international institutions, many of which are legally bound by accessibility requirements. We treat accessibility as a design constraint, not an afterthought.

Conformance target

Core targets WCAG 2.2 Level AA conformance. This includes sufficient colour contrast, text resizing, non-reliance on colour alone to convey information, and resizable, reflowable layouts that function at 200% zoom without horizontal scrolling.

Keyboard operation

Every interactive element — navigation, chat composer, canvas controls, map and chart interactions, evidence views — is operable by keyboard alone. Focus order is logical, focus indicators are visible, and no interface requires a pointing device to complete a task.

Screen reader support

Core uses semantic HTML and ARIA where appropriate. Charts and maps include accessible text alternatives and equivalent table views, so that data is not locked behind a visual representation. Artifact content and evidence chains are structured for assistive technology navigation.

Adjustable typography

Core supports a per-user base font size preference, adjustable in settings. The interface scales proportionally from the selected base size, so increasing type size enlarges all text — not just body copy — without breaking layout.

Visual clarity

Confidence, missingness, and uncertainty are conveyed using labels and patterns in addition to colour, so that information is legible to users with colour vision differences. Interactive states (hover, focus, selection) are distinct and high-contrast.

Feedback

If you encounter an accessibility barrier, report it to the platform administrator. Accessibility issues are treated as defects and prioritized accordingly.