TelegramMessenger / TelegramMessenger/Telegram-iOS
Accessibility problems that make Telegram unusable
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 9k
- Forks
- 2.9k
- PR merge metrics
- No merged PRs in 30d
Description
The problems I've listed make Telegram very useless.
We cannot use the application efficiently.
-
On the screens with more than 4-5 chat lists, the next items cannot be accessed with VoiceOver.
-
Telegram In all chat types supported by IOS, very few messages can be navigated.
Messages on the display remain constant.
For example, we cannot access past messages. -
VoiceOver responds very late (2-3 seconds) to all interactive items except buttons such as "edit".
This may be due to the interface kit used by Telegram. -
VoiceOver repeatedly says "access available" on screens with more than one item type.
Deactivating this feature will provide a healthier use. -
There is an unlabeled button next to the "Send media" button. Button is not available with VoiceOver.
-
heads can sometimes be accessed, sometimes not, in settings and many screens.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported VoiceOver behavior in chat lists, chat messages, settings, and the Send media area on iOS. Compare navigation, labels, response delays, and item access across the listed screens, then verify each reported accessibility problem with VoiceOver; no source file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- accessibility, mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100