Skip to main content
Zeitgeist Confidential

Accessibility Statement

A whistleblower platform only works if everyone can use it — including reporters using screen readers, keyboard-only navigation, or low-contrast-tolerant displays under stress. Accessibility is therefore a core requirement for us, not decoration. This statement follows the honest-disclosure approach we apply to security claims: we state what is implemented, what is targeted, and what we still have to improve.

Conformance target

Our engineering target is WCAG 2.1 Level AA. We have implemented the measures listed below in code and design, and we continuously verify them during development. We do not yet hold an independent accessibility audit certificate, so we state our posture as “designed and built to meet WCAG 2.1 AA” rather than claiming certified conformance. When we commission an independent audit, its results and date will be published here.

What is implemented today

  • Skip-to-main-content link as the first focusable element on every page (WCAG 2.4.1 Bypass Blocks).
  • Visible, high-contrast keyboard focus indicators on all interactive elements, enforced globally in CSS (2.4.7 Focus Visible).
  • Programmatic labels on form fields, with aria-required and descriptive hints on critical inputs like report content and passwords (1.3.1, 3.3.2).
  • Icon-only controls (send, attach, show/hide password, copy) expose accessible names via aria-label (1.1.1 Non-text Content).
  • Semantic landmarks (header, main, nav, footer) and a single h1 per page for screen-reader orientation (1.3.1, 2.4.2).
  • Status and error messages announced via role="alert" and role="status" so they reach assistive technology without a page reload (4.1.3 Status Messages).
  • Motion-sensitive design: animations and transitions are effectively disabled when the operating system requests reduced motion (2.3.3).
  • Full keyboard operability for the report submission flow, reporter check-in, and admin dashboard; dialogs trap and restore focus via accessible primitives (2.1.1, 2.1.2).
  • Language of page declared (lang="en") so screen readers select correct pronunciation (3.1.1).

Known limitations

Stated plainly

  • Some color pairings in dense dashboard charts rely on position and tooltips as well as color; we are progressively adding patterns and text labels so that color is never the only means of conveying information (1.4.1).
  • Third-party embedded content (for example, hosted status-page widgets) is outside our direct control; we choose vendors with published accessibility commitments and review them when we add any widget.
  • We have not yet completed user testing with assistive-technology users; we plan to include paid AT-user testing as part of our first independent audit.

Report an accessibility barrier

If any part of this platform — especially the anonymous report submission or check-in flow — creates a barrier for you, we want to know and we will fix it. Contact support@zeitgeistbusiness.comwith the page, the assistive technology you use, and what happened. We aim to acknowledge accessibility reports within 72 hours and to provide content in an alternative accessible format on request.