Fix large font size accessibility issue on migration screens by making the content scrollable #17474
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.


Fixes #17467
This PR fixes the accessibility issues on the WordPress to Jetpack Migration Flow UI namely:
It accomplishes this by making the content of the Notifications and Success screens scrollable.
To test:
1️⃣ Test with largest font size
Me→App Settings→Debug SettingsJetpackMigrationFlowFeatureConfig& restart the appa. Open the device
Settingsapp, go toAccessibility→Display size and textb. Set
Font sizeto the maxContinueon the Welcome StepContinueon the Notifications step2️⃣ Regression Testing - with default font size
a. Open the device
Settingsapp, go toAccessibility→Display size and textb. Tap
Reset settingsat the bottom, or restore the initial font sizeContinueon the Welcome StepContinueon the Notifications stepPreview
Note that I've also set
Display Sizeto max via Accessibility Settings, otherwise the text would fit on one screen on the Pixel 6 Emulator.largeTexts_preview.mp4
Regression Notes
Potential unintended areas of impact
Migration screens behind the feature flag.
What I did to test those areas of impact (or what existing automated tests I relied on)
Manually tested.
What automated tests I added (or what prevented me from doing so)
N/a.
PR submission checklist:
RELEASE-NOTES.txtif necessary.