Phone-storage work often happens under pressure: an update will not install, the camera stops saving photos, or an app reports that space is low. An accessibility review should therefore test the entire task, not only whether individual buttons have labels. The goal is to confirm that a person can understand what occupies space, choose a safe action, hear or see the result, and recover from a mistake.
Start with the real task
On iPhone, Settings > General > iPhone Storage shows available space and recommendations; Apple also documents that offloading an app removes the app while retaining its documents and data (Apple iPhone Storage guide). Android's storage guidance distinguishes storage from memory and warns that clearing an app's storage permanently deletes its app data, while clearing cache removes temporary data (Google Android storage guide). Use these distinctions as test cases: can the user tell which action is reversible before activating it?
Run four accessibility passes
- Screen reader: Navigate the storage summary, category list, app list, confirmation dialog, progress state, and completion message without sight. Android recommends testing with TalkBack and checking that alerts and temporary messages are read aloud (Android accessibility testing). Apple recommends completing representative tasks with VoiceOver (Apple accessibility testing). Confirm that labels include both the item and its storage amount, focus moves into confirmation dialogs, and a result is announced.
- Large text and zoom: Increase text size and display scaling. Apple specifically calls for checking that Dynamic Type reflows without truncation or overlap. Make sure file names, sizes, warnings, and action labels remain readable rather than being clipped into ambiguous fragments.
- Alternative input: Test keyboard, switch, or voice navigation. Android recommends Switch Access testing, while Apple includes Voice Control. Focus order should follow the visual order, and every action must be reachable without a precision swipe.
- Meaning and recovery: Do not rely on color alone for low-space warnings or selected categories. Pair icons and colors with text. A destructive confirmation should name what will be removed, whether recovery is possible, and what stays intact.
Check deletion paths separately
Different cleanup routes have different recovery behavior. Files by Google says items moved to Trash remain there for 30 days, but files deleted from its junk-files card bypass Trash and are permanently deleted (Files by Google Trash). Test both paths, including the wording before deletion and the status afterward. A generic “clean” button is not enough if it hides that distinction.
The W3C's WCAG2ICT guidance explains how WCAG 2 success criteria can be applied to non-web software, including mobile software (WCAG2ICT). Use it as a framework, then validate on actual devices. Record device, operating-system version, assistive technology, text-size setting, task attempted, expected result, actual result, and evidence such as a screenshot or short recording. Retest after the storage layout or deletion flow changes.
A review passes only when the full storage task is understandable and operable, warnings arrive before the action, and the user can independently confirm what happened.
Sources
- Check iPhone storage — Apple
- Free up space — Google
- Test your app's accessibility — Android Developers
- Performing accessibility testing for your app — Apple Developer
- Move files to Trash and restore files from Trash — Google
- Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies — World Wide Web Consortium, Oct. 8, 2024