With our local SM-T350 (Samsung Galaxy Tab A) test device, if I set font-size accessibility to the maximum ("Extra huge 4")...
With no keys pressed:
With the 'F' key held down...
Note how the 'F' is not properly aligned with the other keys.
Furthermore, if we go for a full down-flick...
The alignment here is considerably worse - it's as if the flick is scrolling an extra 25% of the key's height!
Note that Android accessibility text size: "small" seems to work perfectly.
For comparison, doing this via Chrome emulation in iOS, the 'F' key held down is also similarly not vertically centered correctly, but the other case with a down-flick at 100% is fine. iOS system accessibility does not appear to affect the keyboard at all.
According to what I've seen, iOS has a special CSS style selector that can be used to opt-in to accessibility adjustments.
I noticed this while investigating https://community.software.sil.org/t/android-font-size-inside-of-keyboard/8689 using 17.0.311-beta. (See also: #11279, which came out of the same posting)
With our local SM-T350 (Samsung Galaxy Tab A) test device, if I set font-size accessibility to the maximum ("Extra huge 4")...
With no keys pressed:
With the 'F' key held down...
Note how the 'F' is not properly aligned with the other keys.
Furthermore, if we go for a full down-flick...
The alignment here is considerably worse - it's as if the flick is scrolling an extra 25% of the key's height!
Note that Android accessibility text size: "small" seems to work perfectly.
For comparison, doing this via Chrome emulation in iOS, the 'F' key held down is also similarly not vertically centered correctly, but the other case with a down-flick at 100% is fine. iOS system accessibility does not appear to affect the keyboard at all.