Improving accessibility of telegram

[AlexandrKozlovskiy]

In this pr i suggest several accessibility fixes and improvements.

1. First of all i partially fixed accessibility bug,when blind users should swipe to scroll alot of times,if message contains alot of text,to go to the next node.
2. Also i fixed moving by characters/words,etc with talkback,so now blind users can select and use diferents granularities with talkback.
3. Also i tryed to fix,if in chat admin or owner write from channel or group name,to screenreader read it. I not tested it yet,but i hope,what it works ok.
4. other fixes and improvements.

known issues.

All issues,which known on this moment,connected with accessibility scrolling of chat.

1. During the scrolling sometimes focus jump to indefinite place or on some view out of list. This issue connected probably with incorrect coordinates,to which i scroll and probably with impossibility to get item for position,which invisible in screen. My idea,what top of node (even virtual view) should be at the top of screen.
2. When we scroll to the end of the list,and after this we scroll back,jump to end button not appear. Probably we should call methods from ChatActivity class.
3. Sometimes back scrolling not scroll to previous node (probably the same problems as in issue one).
   Even with this issues in my opinion accessibility scrolling become more better,when message contains alot of text,so if @xaxtix will merge my pr and fix issues,about which i wrote,blind users shouldn't swipe alot of times,if message have alot of text,because for now in official telegram for large messages we,blind users,should swipe sometimes ten,twenty or more times,to go to the next node,if message contains alot of text. Especially it actual,when we swipe right,i.ecall action scroll_forward.

[AlexandrKozlovskiy]

I fixed bug,when percents not announced if user not vote and poll was closed. Also i added announcing during loading of some content.

[b0r1ngx]

👍

[qwq233]

🤔

[qwq233]

reformat code pls

[VallHank07]

version: '2.320.0'mm
Operating System
Runner Image
Runner Image Provisioner
GITHUB_TOKEN Permissions
Secret source: Actions
Prepare workflow directory
Prepare all required actions
Getting action download info
Download action repository 'actions/checkout@v4' (SHA:11bd71901bbe5b1630ceea73d27597364c9af683)
Complete job name: danger-js
2s
Run actions/checkout@v4
Syncing repository: twentyhq/twenty
Getting Git version info
Temporarily overriding HOME='/home/runner/work/_temp/ba5e88dd-2c77-4246-927f-6c28727b290c' before making global git config changes

[AlexandrKozlovskiy]

@qwq233 Now all ok? I updated commit via amend

[Aokromes]

it's bad idea to mix prs (accesibility + mem leak), also, the smaller the prs the higher chance of being merged.

[AlexandrKozlovskiy]

@Aokromes It can be merged partially. I hope get some reply from @dkaraush about future of my pr.

[Aokromes]

partial merges of PRs is a pita, it's better to send one pr for accesibility thing and another for memleak fix.

[Aokromes]

This branch has conflicts that must be resolved
Only those with write access to this repository can merge pull requests.