Effective Date: September 28, 2026

Applies to: ExactDisk 1.0.x for macOS

<aside> ♿

Accessibility position: ExactDisk treats accessibility as part of the product and release contract, not as final-stage polish. The current Mac App Store accessibility declarations supported by implementation and recorded QA are VoiceOver, Dark Interface, and Differentiate Without Color Alone. Additional labels should be added only after the relevant common-task workflow has been explicitly validated in the shipping build.

</aside>

1. Purpose

This framework defines how ExactDisk, developed by Mrdzyn Studio, designs, implements, tests, documents, and declares accessibility support on macOS.

It is intended to serve as:

• The product accessibility standard for ExactDisk.
• The release acceptance framework for accessibility-sensitive changes.
• The evidence model behind Apple Accessibility Nutrition Labels.
• A QA checklist for common ExactDisk workflows.
• A reference for future macOS and cross-platform development.
• A public accessibility statement if this page is later published.

This framework supplements the product's privacy, safety, and legal documentation and should be reassessed whenever ExactDisk introduces a material UI, workflow, platform, or interaction change.

2. Accessibility Principles

ExactDisk follows these principles:

1. Common tasks must be accessible, not just isolated screens. A feature should not be declared supported merely because some controls work with an accessibility technology.
2. Prefer native macOS behavior. SwiftUI and AppKit semantics, standard controls, keyboard conventions, focus behavior, system appearance settings, and accessibility APIs should be used where practical.
3. Safety information must never depend on color alone. ExactDisk's reclaim model includes consequential actions, so risk and protection states must remain understandable without color perception.
4. Destructive and safety-sensitive actions require explicit meaning. Reclaim controls, confirmations, blocked states, stale plans, warnings, and results must be understandable visually and through assistive technology.
5. Accessibility is part of release evidence. Design intent alone is insufficient; material UI changes require appropriate validation.