Aster Disk

Accessibility statement

Aster Disk is designed for showcase-grade accessibility, not just compliance. Every common task — scan a drive, browse what it found, unlock Pro, review suggestions, see what trophies you've earned — can be completed with VoiceOver, Voice Control, or the keyboard alone.

VoiceOver

Every interactive control has a label. The four visualisations — treemap, sunburst, bubble pack, horizontal bars — are layouts of the same data. For VoiceOver users, for whom layout carries no signal, they collapse to a single ordered list of folders by size, each with named actions for Open and Add to selection. The chart canvas itself is hidden from accessibility so it's never read as "image."

File-browser rows read as a single coherent sentence, e.g. "Library, 32.1 GB, 31.7% of folder, directory. Double-tap to open. Press the plus button to add to selection." Percentages are rendered through a locale-aware number formatter, so French VoiceOver hears "31,7 %", not "31.7%."

Trophy badges read as "Snack, unlocked. Reclaimed 100 MB lifetime." Locked trophies still read so VoiceOver users can discover what's possible.

Voice Control

Every named control responds to its visible label. Say "click Scan Whole Disk", "click Unlock", "open Settings". Sidebar destinations, Settings tabs, Suggestion-card actions, paywall buttons, and Home action cards all carry stable identifiers so Voice Control can target them by name.

Keyboard

Tab cycles through interactive controls in visual order. ⌘O picks a folder, Return runs Scan Whole Disk from Home, Space previews the focused file via Quick Look, Esc stops a scan in progress.

System preferences respected

These are reflected live in Aster Disk's own Settings → Accessibility tab, so users can see at a glance what the app is doing for them right now.

What's not there yet

Honesty about what we haven't shipped is part of an accessibility statement. Open items at the time of writing:

Feedback

If something doesn't work, or works less well than it should, please tell me. The fastest path is to open an issue on GitHub; for private feedback, email accessibility@asterdisk.com. Accessibility regressions are treated as bugs, not "nice-to-fix-later."