Accessibility

Accessibility Statement

Last updated

Gematria.Today aims to be usable by the broadest possible audience, including people using assistive technology. This statement records what we test, what we know is not yet conformant, and how to report a barrier you hit.

Standard we target

We target WCAG 2.1 Level AA as our minimum conformance level, with selected Level AAA enhancements (such as a 70-character line-length cap on long-form prose and a 24×24 CSS-pixel minimum on touch targets, going beyond WCAG 2.5.5 Target Size).

What we’ve audited

The following pages have been reviewed against WCAG 2.1 AA and the team’s touch-target audit:

Auditing is a static-code review by the editorial team. We have not yet completed a runtime screen-reader pass with NVDA or VoiceOver on the full set; that work is tracked as ongoing.

Methodology: our most recent WCAG 2.5.5 (Target Size) audit and the per-pattern fixes are recorded in the accessibility audit report.

Known gaps

We are openly tracking these areas as not-yet-conformant:

  • Calculator dynamic results. Result regions announce updates, but error and validation messaging is being expanded with inline help and aria-invalid coverage.
  • Forum. Empty states, character counters on compose/reply, and skeleton loaders are in progress; today the thread list paints blank during initial fetch.
  • Admin tooling. The admin dashboard and editorial tools are role-gated and have not been audited to AA. They are not part of the public conformance claim.
  • Member dashboard first paint. Auth state is now set before first paint via a synchronous bootstrap script, but full skeleton loaders for member content are still rolling out.
  • Cookie consent banner. Equal-weight Accept/Decline is implemented; granular per-category controls are not yet exposed.

Compatibility

  • Current major versions of Chrome, Edge, Firefox, and Safari on desktop and mobile.
  • iOS VoiceOver and Android TalkBack on touch devices.
  • NVDA and JAWS with Chrome or Firefox on Windows.
  • Keyboard-only navigation throughout the public site.

Reporting a barrier

If you encounter an accessibility barrier, please contact us through the contact page with:

  • The page URL where the barrier occurred.
  • A description of what you tried to do and what happened.
  • The assistive technology, browser, and operating system you used.

We aim to acknowledge accessibility reports within 5 business days and to provide a remediation plan (or a documented workaround) within 20 business days. We will follow up in writing through your preferred contact channel.