Accessibility Statement

1. Commitment

TARK Learn aims to make the product usable by students and parents with a range of abilities. For the private pilot, we use WCAG 2.2 AA as the practical target where it applies to the web product and learning surfaces.

2. Current Supports

• Responsive pages that work on common desktop and mobile screen sizes.
• Keyboard-visible focus styles and skip navigation on the student shell.
• Light and dark student themes with ongoing contrast checks.
• Reduced-motion handling where animations are used.
• Semantic page structure, labels, and status text for important controls.
• Code snippets rendered as code blocks when the content is structured or detected as code.

3. Learning Content

Diagrams, graphs, charts, formulae, and code examples should be rendered in deterministic TARK components rather than unreviewed images whenever they are used for scored student work. Validated visual assets should include text alternatives and avoid relying on color alone.

4. Known Limitations

TARK Learn is changing quickly during the private pilot. Some imported, generated, or admin-curated content may need additional review before it meets the accessibility standard we want for public launch. Please report any barrier so we can fix it.

5. Accommodations

Some student needs may require an individual support plan, such as extra time, an accessible alternative to a visual question, or a simplified testing surface. See Accommodations for the current private-pilot process.

6. Reference

We use the W3C Web Content Accessibility Guidelines as a practical reference for product review:

• W3C Web Content Accessibility Guidelines 2.2

7. Contact

Questions or requests can be sent to privacy@tarklearn.com. Product support can be sent to support@tarklearn.com.