Single-Case InformaticsSign in

Accessibility Statement — Single-Case Informatics (SCI)

Prepared by: Carson Russo · Prepared date: 2026-07-22 · SCI version/commit: 489c66a1 · Applies to: the Single-Case Informatics web application at https://alpha.singlecase.ai.

Our commitment

Single-Case Informatics is committed to making its web application usable by everyone, including people who use assistive technologies such as screen readers, screen magnification, speech input, and keyboard-only navigation. We treat accessibility as ongoing work and publish this statement honestly, including where we fall short.

Conformance status

The Web Content Accessibility Guidelines (WCAG) 2.2 define requirements to improve accessibility for people with disabilities at three levels: A, AA, and AAA.

SCI is partially conformant with WCAG 2.2 Level A and AA. "Partially conformant" means some parts of the content do not yet fully conform to the standard. WCAG 2.2 is backward-compatible with WCAG 2.1, so this target also meets the WCAG 2.1 A/AA floor.

We are not claiming full WCAG conformance, ADA compliance, or third-party certification. The known gaps, and the alternative ways to accomplish the same tasks, are listed under "Known limitations" below and tracked in our Accessibility Roadmap.

Measures we have taken

Recent remediation across the application includes:

  • Names and labels — form fields, data-entry grid cells, table headers, dialogs, and ~170 dropdown (Select) controls now expose programmatic accessible names; visible labels are associated with their controls.
  • Structure and navigation — a skip-to-content link, main/nav/banner landmarks, descriptive per-page titles, and focus movement on navigation; authenticated list views expose table semantics.
  • Graphs (single-case results) — every results graph is exposed as a single named image and ships an accessible text summary + data-table equivalent of the plotted values, so results are available without relying on the visual chart.
  • Status and errors — sign-in, invitations, onboarding, autosave, AI-review, and export progress are announced to assistive technology through live regions (without flooding); form errors are identified, tied to their field, and explain how to fix the problem.
  • Contrast and color — text, status chips, and focus indicators were measured and adjusted to meet the applicable contrast minimums in light and dark themes (including the alternative color themes); information is not conveyed by color alone in the remediated areas.
  • Keyboard operation — visible focus indicators; a documented data-grid keyboard model; keyboard operation of the graph editor's controls, panels, and resize handle; keyboard-operable crop inputs and scrollable data regions.
  • Exports — posters and graphs offer an accessible HTML / text-and-table alternative to image-only output, and generated documents declare their language.

Known limitations

Despite our efforts, the following are not yet fully accessible. For each, we describe the barrier and the alternative way to accomplish the task ("workaround"), and we are working to remove them (see the Roadmap for target dates). If you need an alternative that is not listed, please contact us (below).

  1. Distinguishing graph series by color (WCAG 1.4.1). Default graph styling can rely on color to tell data series apart. Alternative: the accessible data table + text summary attached to every graph conveys each series without color, and series markers/line styles can be configured. Planned: color-independent default styling.
  2. "Download SVG" graph export (WCAG 1.1.1). The plain SVG download does not embed a text/data equivalent. Alternative: export the underlying data as CSV/JSON, use the in-app graph data table, or use the graph crop/download dialog, which includes the text+table equivalent. Planned: bundle the equivalent into the SVG download.
  3. Advanced graph authoring — per-point styling and annotations (WCAG 2.1.1, 2.5.7). Styling an individual data point, and placing/moving annotation shapes, currently require a mouse. Alternative: series- and dataset-level styling is fully keyboard-operable, and the graph's data and analysis are fully available through the keyboard/AT-accessible text summary + data table; annotations are decorative overlays. Planned: a keyboard point-picker and a keyboard annotation geometry editor.
  4. Generated PDF/PNG exports (posters, reports) (WCAG 1.1.1, 1.3.1, 1.3.2). Raster PDF/PNG output is not tagged, and per-image author alt text is not yet captured. Alternative: the "Accessible view / Download accessible HTML" option produces a structured, screen-reader-friendly version of the same content. Planned: tagged (PDF/UA) export and per-image alt text.
  5. Minor items. A shared tab component deviates from the standard keyboard pattern (content remains reachable); the resting form-field border is low-contrast (fields carry labels and a high-contrast focus indicator); some AI-review severity labels are worded inconsistently; a few compact indicators are below the target-size minimum (the same values appear in the data grid/table). Each is tracked in the Roadmap.

Verification status. In addition to automated testing, code/structural review, and computed contrast measurement, a recorded human verification pass was completed on 2026-07-22: a keyboard-only walkthrough of the ten primary user journeys (sign-in through data entry, graphs, exports, and settings), an NVDA screen-reader pass of the SCI-specific surfaces (results graphs and their text/table equivalents, the data-entry grid, AI feedback, form validation, and dialogs), and a Windows High Contrast (forced-colors) spot check — all passed, with no blockers found. Broader assistive-technology coverage is still ongoing and not yet complete: JAWS and VoiceOver, additional browsers, 200–400% zoom and reflow, comprehensive forced-colors and reduced-motion passes, and PDF/UA reader checks of generated documents. One recently-completed fix (AI-review dismiss/reopen focus handling) is pending a final live confirmation.

Feedback and how to report a problem

We welcome your feedback on the accessibility of SCI. If you encounter a barrier, please tell us:

Email: [email protected]

Please include, where you can: the page or feature, what you were trying to do, the barrier you hit, your assistive technology + browser/operating system (if relevant), and how to reach you. We aim to acknowledge reports within 5 business days and will give you a target for a fix or an equally-effective alternative. We follow a documented internal process for logging, triaging, and resolving every accessibility report we receive.

Assessment approach

This statement is based on a self-evaluation by Single-Case Informatics. Methods used: automated testing (axe-core via Playwright), manual code and structural review, computed sRGB contrast measurement, and a recorded keyboard-only walkthrough, NVDA screen-reader pass, and Windows High Contrast check (completed 2026-07-22). We maintain internal records of this work — audit reports, verification records for each round of fixes, the manual verification run described above, our remediation roadmap, and a register of known exceptions. Automated and self-conducted testing do not by themselves establish conformance; see the "Verification status" note above.

Technical information

SCI's accessibility relies on the following technologies to work with your browser and any assistive technologies: HTML, CSS, JavaScript (React), WAI-ARIA, and SVG. These are relied upon for conformance with the standards above.

Formal approval

  • Prepared by: Carson Russo — 2026-07-22
  • Reviewed/approved by: Carson Russo (statement owner) — 2026-07-22
  • Next review: on each significant release, or at least quarterly (see the Roadmap review cadence).