Hey, I've talked before about the major thing slowing down Android screen readers: double taps! Just to recap: when you tap the screen, the screen reader waits for some time, just to see if you'll tap again to register a double tap. Only after that time does it register a single tap and tell you what's under your finger. This makes tapping slow! And in normal navigation, it's fine. But in typing, it slows us down a lot! Not only because we have to wait for a fraction of a second for it to register a single tap instead of a double tap, but we also can't touch type so fast because then it will start registering double taps!
The fix for that is really easy. Just make screen readers ignore the double-tap logic in the keyboard area when the keyboard is up (if you selected any typing mode other than double-tap typing). Because it doesn't need to handle double taps in that area; you just put your finger, and it instantly registers a single tap and tells you what's under your finger. When you lift, it types. That would be great, and I'm very sure it's easy to implement (Oh, how I wish I knew enough Java and Android API to implement that into TalkBack...)
Because Android itself is not slow at all! In fact, it's instant for all I can notice. And you can test that, even with your screen reader (just so you can notice the reader is artificially slowing itself down).
First, focus on an item. Now, double-tap. But you need to make your second tap pretty late, just before the timer ends but not much before it, nor after it. You will notice the double tap registers right after your second tap, instantly if you get the timing right, and this is frustrating. The screen reader is intentionally slowing itself down, without giving us an option to change the preset timer or implementing the easy fix for the keyboard to make touch typing possible and fast! #Android#AndroidAccessibility#ScreenReader#UserExperience#AccessibilityIssues#Accessibility#Talkback
@evilcookies98 I have no idea what you're refering to. But if you meant turning off explore by touch, then no. Because that turns it off for the intire screan, and unless you're direct-touch typing, it wouldn't help. If you're using the lift to type mode, it wouldn't work with explore by touch disabled.
@meatbag and your talkback settings, under advanced, then developer settings, there’s an option that says handle gestures in talkback or something similar. You’ll want to kill that if you want it to be more responsive.
@evilcookies98@meatbag Never thought of trying with that off, but yep definitely faster, also keep anything related to refresh rate on because that impacts how fast touch is registered. If you can handle the battery hit, which is minimal if you use curtain like I do forcing peak refresh in dev options really makes a difference.
Add comment