Accessibility checks for reviewing mobile data usage should test whether a person can find the current period, identify the heaviest-using apps, understand warnings, and change a setting without relying on vision, color, or precise tapping. Run the check on the real screen with assistive features enabled, because an automated scan is useful evidence but not a complete usability test.
Start with the task, not the layout
Write down the outcome a user needs: confirm the billing period, compare app usage, spot roaming or background use, and decide whether to change a warning or limit. Keep the carrier's period and the phone's period visible in the test notes. A technically readable number can still mislead if its date range or units are unclear.
Test the entire path with the platform screen reader. Every app row, chart control, warning, and switch needs a useful spoken label, role, current state, and predictable focus order. Decorative graphics should not create noisy stops. If a chart contains the only copy of a value, provide the same information in text or an accessible table.
Check scale, contrast, and targets
Increase text to 200 percent and repeat the core task. The WCAG guidance for text resizing calls for text to remain usable at that scale without loss of content or functionality. Look for clipped app names, hidden units, overlapping buttons, and controls that move off screen.
Check text and meaningful visual indicators against their backgrounds. WCAG's minimum contrast guidance sets 4.5:1 for ordinary text and 3:1 for large text. Do not use green, amber, or red as the only signal for usage status; add words, icons with labels, or both. Check focus indicators and chart legends in light and dark appearance.
Tap every control one-handed and with magnification active. Small icons may be visible yet difficult to operate. Google's Accessibility Scanner specifically checks content labels, touch-target size, clickable items, and text or image contrast, making it a useful first pass for Android interfaces.
Run a manual evidence check
Use at least two scenarios: low usage with no warning and usage near or above a limit. Confirm that the screen reader announces the important difference and that a person can reach the action without guessing. Rotate the device, enable large text, and test at least one older or smaller phone if the service supports it.
Record each issue with the device, operating-system version, assistive feature, exact route, expected result, observed result, and a screenshot or short recording that does not expose personal account data. Retest after a fix with the same scenario. Google's own scanner documentation says automated results do not replace manual accessibility testing, so close the review only after a person has completed the task.
A short acceptance checklist
The review passes when the period, units, app name, amount, warning state, and available action are understandable without color; text remains usable at 200 percent; interactive controls have clear names and states; focus order matches the workflow; and the main task works with a screen reader and touch alternatives. Keep any carrier-versus-device measurement difference in plain language near the totals rather than hiding it in a help page.
Sources
- Frequently asked questions about Accessibility Scanner — Google Accessibility Help
- Understanding Success Criterion 1.4.3: Contrast (Minimum) — World Wide Web Consortium
- Understanding Success Criterion 1.4.4: Resize Text — World Wide Web Consortium