Skip to main content
azothos
← Back to home

Accessibility

Accessibility Statement

Last updated: 13 November 2026

Our commitment

Beweird SAS is committed to making Azoth OS usable by everyone, including people who rely on assistive technologies. We design and build against the Web Content Accessibility Guidelines (WCAG) and the EN 301 549 standard.

Conformance status

Azoth OS is partially conformant with WCAG 2.1 Level AA. “Partially conformant” means most of the standard is met, but some content does not yet fully conform. A formal assessment against the newer WCAG 2.2 Level AA criteria, and an independent third-party audit (VPAT), are not yet done.

We do not claim WCAG 2.2 AA conformance until that independent audit and a live assistive-technology pass are finished. This statement reflects the honest current state.

What is in place today

  • Keyboard — controls are native buttons, links and inputs, operable from the keyboard, with a visible focus indicator from one shared style; a “Skip to main content” link on every page. Choices such as On / Off are toggle buttons that say which one is selected.
  • Dialogs, panels and menus — dialogs and drawers keep focus inside them while open; dialogs, drawers, the side panel, the command palette and the pop-up menus close on Escape — the topmost one only — and give focus back to the control that opened them.
  • Names — every form field and every icon-only button has an accessible name; the shared controls name themselves in the interface’s language.
  • Structure — semantic landmarks (header, nav, main) and one main heading per page.
  • Contrast — the colour tokens of both themes, light and dark, meet the AA contrast ratios for text and for the boundaries of fields and controls.
  • Announcements — status and error messages use ARIA live regions (polite / assertive).
  • Languages — five UI languages including right-to-left (Arabic), with the correct lang and dir; icons that point along the reading direction turn round in Arabic.
  • Testing — checks in our automated test suite, run on every change, hold the points above: names of fields and buttons, no mouse-only controls, landmarks, contrast of the colour tokens, right-to-left layout. Automated axe-core checks run in end-to-end jobs against a sample of pages (the public site in English and Arabic, sign-in, the dashboard’s main screens) when those jobs are enabled; they do not yet gate every deployment.

Known limitations

We are aware of, and working on, the following:

  • The axe-core checks cover a sample of pages and do not run on every change; the other screens rely on the source checks above and on manual keyboard checks.
  • The WCAG 2.2-specific criteria (e.g. Focus Not Obscured, Target Size Minimum, Accessible Authentication, Redundant Entry) have not yet been formally verified with assistive technology.
  • Some data visualisations (sparklines, trend charts) convey their meaning through an adjacent numeric value rather than an equivalent data table.
  • The scripted governance demo is written in English in every language; its player controls are translated.
  • An independent audit and a published VPAT are pending.

Feedback

If you encounter an accessibility barrier, please tell us — we treat accessibility reports as a priority and aim to respond within five business days.

Email: support@azothos.ai

Please include the page, what you were trying to do, and the assistive technology and browser you were using.

Assessment method

This statement is based on a self-assessment combining code review, the automated checks described above, and manual keyboard checks. It will be updated when the independent audit completes.

© 2026 Beweird SAS
Mentions légalesPrivacyCookiesTermsSecurityAccessibilityDPA