Repository navigation
|
How can a team catch Font scaling disabled due to dp text sizing automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. python3 scripts/accessibility-audit.py . --rule ANDROID-ACCESSIBILITY-FONTSCALINGRead the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. Hardcoded text sizes specified in dp instead of sp in Android XML layouts or Jetpack Compose files. The fix. Always define text sizes in sp (scale-independent pixels) rather than dp to allow the system font scaling to work correctly. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
python3 scripts/accessibility-audit.py . --rule ANDROID-ACCESSIBILITY-FONTSCALINGRead the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
ANDROID-ACCESSIBILITY-FONTSCALINGwith a coverage line and a proper exit code.What the hit means. Hardcoded text sizes specified in dp instead of sp in Android XML layouts or Jetpack Compose files.
The fix. Always define text sizes in sp (scale-independent pixels) rather than dp to allow the system font scal…