Scrolling lists not propperly interpretted by screen reading services

[CiprianDinca9]

Please check before submitting an issue

• I have searched the issues and haven't found anything relevant
• I will upload bugreport file in KernelSU Manager - Settings - Report log
• I know how to reproduce the issue which may not be specific to my device

Describe the bug

For us blind people, getting the right experience with screen readers is a good thing to have. The app works wonders with a screen reader. The back buttons aren't text labeled, but that is not such a big solution, as those who pay for screen readers get OCR and AI image descriptions, which can be used for the currently focused control. The other issue that's more important is that the scrolling bars aren't communicated to screen readers.
How does a screen reader behave when scrolling? A screen reader, if it has sound feedback enabled along with TTS(Text To Speech) feedback, the sounds report a number of useful things to the user: Clickable or none clickable elements, lists, tables, containers, etc. One of the things it also detects is how far you've scrolled in a list. If you're, say, at the beginning of a list and you scroll (2fingers instead of 1), a sound will ascend as you scroll towards the end and descend when you scroll towards the top back.
Why is this useful? Us blind people will use this to our advantage, as we can stop scrolling without touching the screen or having the TTS voice speak one of the elements in order for us to know where we should stop. If we want to reach a certain element on the list, we can just scroll. Having already learned the pitch of the scroll bar when it's in a certain position, we can easilly know where we are in a list. In KSU manager, the scrollbar doesn't propperly work: With TalkBack it just makes a sound indicating that the progress bar couldn't be propperly detected, while with the Chinese Jieshuo, the paid and most enhanced screen reader on Android, it doesn't do anything. Yes, the list does scroll, but is not announced or repported in any way to screen readers.
How to reproduce the bug: 1. Enable a screen reader and go through the tutorial, if it's for the first time. 2. If you're using a vertical app drawer like Nova launcher or any other AOSP launcher, you can go to your apps screen. Slowly drag 2fingers towards the top of your screen, starting from the very bottom. Drag slowly and notice how the sound increases in pitch as you go deeper in the list. 3. Now that you know how the behaviour should be working, open KSU manager. It's recommended to have over 30 or 40 user apps installed. If not, check show system apps so that the list isn't short. Drag the same way, with 2fingers from the bottom of the screen towards the top. Notice how the sound doesn't move an inch?
This is how to reproduce the bug and everything about it. I hope you'll be able to fix this. If not, though, I'll talk to the screen reader's developer to do something about it. This means, however, that TalkBack users will be left behind, as Google's not responding to any feedback and suggestions unfortunately.
P.S. I hope you'll be able to fix this. If not, don't beat yourselves too hard over it, it's totally ok. If possible though, text label the back buttons, as that's easilly done and not too much work.

To Reproduce

1. Turn a screen reader on. 2. Go through it's tutorial to finish. 3. Practice scrolling on a vertical app drawer launcher, the easiest to reach. 4. Hear how scrolling makes no sound in KSU's superuser apps list?

Expected behavior

Scrolling sounds propperly supported

Screenshots

No response

Logs

No response

Device info

• Device: Any device, manager issue
• OS Version:Any
• KernelSU Version:1.0
• Kernel Version:Any

Additional context

No response