Last updated · 2026-07-13

Accessibility statement

Schmatz aims to make its research usable with keyboards, assistive technology, zoom, reduced motion, and different display preferences. The product has not completed a formal accessibility audit and does not currently claim full WCAG conformance.

Plain-English SummaryCore pages use semantic HTML and keyboard-operable controls, and the app includes reduced-motion, density, and theme settings. Dense data views and custom SVG charts still need deeper screen-reader and contrast testing. If a barrier blocks you, tell us what happened and we will prioritize a practical fix.

Goal

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That is a development goal, not a certification. The current product is an early-access release built by one operator, and testing coverage is still growing.

Features currently provided

Semantic headings, landmarks, links, buttons, labels, and form controls on core routes
Keyboard access for standard navigation and interactive controls
Visible focus styling on shared controls
Dark and light themes, adjustable accent, and comfortable or compact density
A reduced-motion setting plus support for browser reduced-motion preferences on many animations
Responsive layouts intended to support browser zoom and narrow screens
Text alternatives for meaningful images where they are part of the current interface

Known limitations

Charts and visual research: custom SVG charts provide labels and summaries, but not every chart exposes a full equivalent data table or optimal screen-reader navigation.
Dense tables and comparison views: keyboard and screen-reader behavior has not been comprehensively tested across all browsers and assistive-technology combinations.
Color and custom appearance: the default palettes are designed for contrast, but every chart state, hover state, and user-selected accent has not been independently measured.
Motion: reduced-motion support exists, but some older or route-specific transitions may still animate.
Generated content: AI-assisted prose and dynamic research cards may contain heading, table, or link structures that are less predictable than hand-authored pages.

Report a barrier

Use the Support contact form or email [email protected] with “ACCESSIBILITY” in the subject. If possible, include:

The URL or feature where the barrier occurred
What you were trying to accomplish
What happened instead
Your browser, device, and assistive technology
Any workaround or format that would help immediately

We aim to acknowledge accessibility reports within five business days. Resolution time depends on severity and complexity, but an urgent blocker to a core account function will be prioritized.

Reference

Our target is based on the WCAG 2.2 Recommendation. We will update this statement when a formal audit or material accessibility change is completed.