Accessibility

Effective date: August 18, 2026

This statement describes how Heirloom Vine Institute ("we", "us") approaches accessibility in HeirloomOS (the "Service").

1. Our commitment

Accessibility is a design requirement of the Service, not a settings page or an afterthought. Our automated test suite tolerates zero axe violations: a build that introduces even one accessibility violation does not ship. Motion in the interface respects the prefers-reduced-motion setting of your operating system, and color never carries meaning alone. Anywhere color signals a state, a label or icon signals it too.

2. What we test

Every public page and every app workspace is audited with the axe engine in a real browser, not with static analysis alone. We also test keyboard navigation, so the Service can be operated without a mouse, and focus visibility, so you can always see where you are on the page.

3. Known limitations

The product is new, and we would rather be honest than tidy. Some studio workspaces are still receiving deeper keyboard passes. Where we know a workflow falls short, it is on our list, and the sections above describe the bar it must meet before we consider it done.

4. Contact

If anything in the Service is hard for you to perceive, navigate, or operate, tell us. We treat access barriers as defects, not feature requests: they are triaged and fixed the same way a broken page would be.

Heirloom Vine Institute · subscriptions@heirloomvineinstitute.com