Accessibility statement
Schmatz aspires to meet WCAG 2.1 Level AA. We are not there yet, and we'll tell you exactly where the gaps are.
Commitment
Schmatz is committed to making its product accessible to people with a wide range of disabilities. We target the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, as published by the World Wide Web Consortium (W3C). The full guidelines are at w3.org/WAI/standards-guidelines/wcag.
What's accessible today
- Semantic HTML: pages use appropriate heading hierarchy, landmark elements, and semantic tags
- Keyboard navigation: standard interactive elements (links, buttons, form fields) are reachable and operable via keyboard
- Text legibility: body text is set in sizeable, well-spaced fonts; the editorial typography uses generous line-height and measure
- Editorial color palette: ink-on-paper contrast on body text exceeds 7:1 — well above the AAA threshold
- Magnification: pages render correctly at up to 200% zoom in standard browsers
Known limitations
Honest accounting of where we know we're below AA today:
- Cinematic gradient on the landing page: the scroll-driven color-mix interpolation produces brief transition zones where text-to-background contrast can dip below the 4.5:1 AA threshold. The <body> text remains readable but a colorimeter check would flag specific scroll positions.
- Data tables in the dashboard: the "Today" decision queue and the "Book" positions table use dense numerical layouts. Screen-reader navigation through these tables is functional but not optimal; cell-level row/column headers are present but not yet labelled with ARIA properties that would improve the read-out.
- SVG visualisations: the equity-curve chart and shock-scatter plots have descriptive titles but do not yet expose tabular underlying data to assistive technology. A "view data" toggle is on the roadmap.
- Color-only meaning: positive/negative polarity indicators on cards use both color (red/olive) and supplementary text labels (signed numbers). One known exception is the red-thread visualisation, where line-color alone conveys polarity — text labels nearby convey the same information.
How to report an accessibility issue
If something on Schmatz prevents you from accomplishing what you came here to do, please tell us. Email through the beta channel by which you received your invitation, with "ACCESSIBILITY" in the subject. Tell us:
- The URL where the issue appears
- What you were trying to do
- What happened instead
- What assistive technology, if any, you were using
We will acknowledge accessibility reports within 5 business days and follow up with either a fix or a clear plan + ETA.
Continuous improvement
Accessibility is a moving target. We will revisit this statement as the product evolves and update the "Last updated" date when material changes are made. Items called out as "known limitations" above will be addressed and moved out of that list as we ship fixes.
Reference standards
This statement is informed by:
- WCAG 2.1 (W3C Recommendation)
- Section 508 of the Rehabilitation Act — applicable to federal agencies, used here as best practice
- ADA web accessibility guidance (U.S. DOJ)