accessibility related bugs with voiceover

abdullah5490 commented 4 years ago

Checklist

[x] I am reporting an issue in existing functionality that does not work as intended
[x] I've searched for existing GitHub issues

Description

In the issue #14 the voiceover accessibility was provided and that issue was closed, but unfortunately, the accessibility is still requiring too many adjustments in the iOS client.

Voiceover does not speak proper labels for many buttons in the interface, such as the "call" button, doesn't have any label and voiceover just said "button". A user could not identify the function of this button by this behaviour. Moreover, When we select the chats, the actions bar containing functions of "read, archive, delete" etc. are not readable. We cannot perform these functions on selected chats while using voiceover. These are just a few example of this kind of bugs with voiceover.
In a group conversation, we cannot open the group info screen to view it's members, or files, or set other options on a group.
When we select a chat in the main view, the voiceover does not indicate which chat is selected and which is not. It should speak "selected" with the marked items.
When we send a message, voiceover does not tell the status of the message whether is it being send, or its sent, or its delivered, or read/play by recipient. This information is very critical and should be presented to the voiceover users as it is for the sighted users.
lots of other focus related bugs are present, where the screen changes after pressing certain control, but voiceover curser does not render the newly appear content in gesture navigation. For example, if we want to change the notification tone, we couldn't focus to the available tones after selecting the responded option in the settings to choose from. Similarly, if we click on "compose" in the main windows, the newly popped up screen is not focused and rendered by accessibility service from where we can search for contact to start a new chat.
The share menu is not at all accessible when we try to share a link/file from other app like youtube.
Do read Comment1 By Simon818, Comment By Nick6489 and Comment2 By Simon818 for few more major accessibility bugs.

Expected Behavior

I've mentioned this along with the problems in above stated 4 points.

Steps to Reproduce

Install the latest client from apps store.
turn on voiceover and open telegram.
now, navigate around the program, the main view of conversation list, press "edit" button and select the chats, it will not tell you that it is now selected or not.
Then try to delete chats after selection, you'll not be able to focus to the action bar at bottum.
Open any conversation and try to find "call" button, you will not.
Open any group conversation and try to open "group info", you will not, with voiceover.
in the "chat info screen", try to navigate between "files, members, links or voice messages" view with voiceover, you can't do this.
in the main windows, simply try to start a new chat with "compose" button. You'll not be able to select/search contacts on that screen.
go to youtube, open a video, click "share" and choose telegram. You'll not be able to navigate within the telegram sharing screen here.

Environment

Device: iPhone/iPad X

iOS version: 13.X

App version: 7.X

marrie commented 3 years ago

Thanks for that. I might need to reinstall and test, if I can remember my information. If I can, I’ll be providing my not so loved bug reports. They can get a bit long in length if I’m not careful.

Thanks for the heads up. I’ll look at this after work.

marrie commented 3 years ago

Here are my findings so far. I hope the attached screen cap comes through aligned with the message, I’m using ios 14.4 on an iphone 10R.

when in the contacts tab (it is still labeled as button here) I hear the fast tapping sound as if the icons are rapidly changing when I'm close to the top. I don't know why I would hear this. I'm exploring by touch here not swiping. This also can happen near the bottom of the contacts tab as well.
I cannot find the playback button by exploring by touch. I have to swipe. this is when I'm listening to a message.3. there is an unlabeled button at the upper right hand corner of the chat. There are also unlabeled buttons in almost the same places under the contacts tab (not button) and settings tab (not button)
It seems as though the back button in a bio is quite small. I had a hard time finding it with explore by touch. I had to swipe to this one. note, I cannot show screen caps here as I don't want to reveal any personal info such as phone numbers.
in the contacts tab there is an area when you explore by touch and ignore the fast scrolling sound, actually it's the sound you get when you do a say all and speech is turned off, the fast tapping like sound as the curser changes, there is an icon with no label with the hint"swipe up and down for to hear action." I do have a screen cap of this area, at least I Hope so. You can find it by turning voiceover on and touching near the top of the screen just below the search field. You must tap the unlabeled button first, though.
when scrolling with 3 fingers, I hear not the scrolling sound but the end of boundary sound, which makes me think scrolling does not work, when in fact it might be.
when in the auto download section of settings, you cannot scrub back wit the voiceover gesture. You must touch with 4 fingers at the top of the screen and tap the back button. In fact, I cannot find the back button neither with exploring by touch nor swiping.
in the same settings tab if you do a 4 finger touch at the top of the screen, you hear an icon, however voiceover does not voice it.

That should be enough for now. It looks good so far.

as I’m sending this by email. I just don’t want to write the markdown code right now.

Deon588 commented 3 years ago

Another issue:

When you start a secret chat the button that lets you set the time before a message disappears is not read by voiceover at all.

Sent from my iPhone

On 29 Jan 2021, at 19:06, Sarah Alawami notifications@github.com wrote:

Here are my findings so far. I hope the attached screen cap comes through aligned with the message, I’m using ios 14.4 on an iphone 10R.

when in the contacts tab (it is still labeled as button here) I hear the fast tapping sound as if the icons are rapidly changing when I'm close to the top. I don't know why I would hear this. I'm exploring by touch here not swiping. This also can happen near the bottom of the contacts tab as well.

I cannot find the playback button by exploring by touch. I have to swipe. this is when I'm listening to a message.3. there is an unlabeled button at the upper right hand corner of the chat. There are also unlabeled buttons in almost the same places under the contacts tab (not button) and settings tab (not button)

It seems as though the back button in a bio is quite small. I had a hard time finding it with explore by touch. I had to swipe to this one. note, I cannot show screen caps here as I don't want to reveal any personal info such as phone numbers.

in the contacts tab there is an area when you explore by touch and ignore the fast scrolling sound, actually it's the sound you get when you do a say all and speech is turned off, the fast tapping like sound as the curser changes, there is an icon with no label with the hint"swipe up and down for to hear action." I do have a screen cap of this area, at least I Hope so. You can find it by turning voiceover on and touching near the top of the screen just below the search field. You must tap the unlabeled button first, though.

when scrolling with 3 fingers, I hear not the scrolling sound but the end of boundary sound, which makes me think scrolling does not work, when in fact it might be.

when in the auto download section of settings, you cannot scrub back wit the voiceover gesture. You must touch with 4 fingers at the top of the screen and tap the back button. In fact, I cannot find the back button neither with exploring by touch nor swiping.

in the same settings tab if you do a 4 finger touch at the top of the screen, you hear an icon, however voiceover does not voice it.

That should be enough for now. It looks good so far.

as I’m sending this by email. I just don’t want to write the markdown code right now.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

MarcoZehe commented 3 years ago

Hi all! Great to see some improvements! After nothing had happened for 1.5 years, and my issues #144 #145 and #146 hadn't received any reactions, I had given up on Telegram for a while. I just reinstalled it. Some of the issues seem to have been fixed, but others still remain. Adding my voice to those who would love to see, and be available to test, more fixes. Keep the momentum going! :-)

Simon818 commented 3 years ago

I accepted my first call on Telegram for iOS a few days ago, and wow, it's bad. Not a single call control is labelled. I'm glad I didn't need to mute myself because I would have had no idea where to start, and when it was time to end the call I just closed the app. Just adding this to the list because I don't think anyone has mentioned it yet; I certainly didn't remember or expect it.

jadesharp1992 commented 3 years ago

Hi, Another huge thing I have noticed recently with telegram, I was added into a group the other day and it is very trafficcy. When reading through the messages, VoiceOver will read about 10 at a time and then it will stop. You have to swipe up with 3 fingers to get more there, but it doesn’t always work. I really hope this can be fixed soon as it’s very frustrating not having a constant reading experience with messages.

On 21 Feb 2021, at 19:41, Simon Jaeger notifications@github.com wrote:

I accepted my first call on Telegram for iOS a few days ago, and wow, it's bad. Not a single call control is labelled. I'm glad I didn't need to mute myself because I would have had no idea where to start, and when it was time to end the call I just closed the app. Just adding this to the list because I don't think anyone has mentioned it yet; I certainly didn't remember or expect it.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/TelegramMessenger/Telegram-iOS/issues/267#issuecomment-782913558, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGHKOCV2E33L2P4KNS6OVE3TAFOXLANCNFSM4LW2ORXA.

beqabeqa473 commented 3 years ago

it was identified also, that if reply message is voice message, it won't play.

i don't know if this issue was already reported.

On 2/22/21, jadesharp1992 notifications@github.com wrote:

Hi,

Another huge thing I have noticed recently with telegram, I was added into a group the other day and it is very trafficcy. When reading through the messages, VoiceOver will read about 10 at a time and then it will stop. You have to swipe up with 3 fingers to get more there, but it doesn’t always work. I really hope this can be fixed soon as it’s very frustrating not having a constant reading experience with messages.

On 21 Feb 2021, at 19:41, Simon Jaeger notifications@github.com wrote:

I accepted my first call on Telegram for iOS a few days ago, and wow, it's bad. Not a single call control is labelled. I'm glad I didn't need to mute myself because I would have had no idea where to start, and when it was time to end the call I just closed the app. Just adding this to the list because I don't think anyone has mentioned it yet; I certainly didn't remember or expect it.

—

You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/TelegramMessenger/Telegram-iOS/issues/267#issuecomment-782913558, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGHKOCV2E33L2P4KNS6OVE3TAFOXLANCNFSM4LW2ORXA.

--

You are receiving this because you commented.

Reply to this email directly or view it on GitHub:

https://github.com/TelegramMessenger/Telegram-iOS/issues/267#issuecomment-782918675

-- with best regards Beqa Gozalishvili Tell: +995593454005 Email: beqaprogger@gmail.com Web: https://gozaltech.org Skype: beqabeqa473 Telegram: https://t.me/gozaltech facebook: https://facebook.com/gozaltech twitter: https://twitter.com/beqabeqa473 Instagram: https://instagram.com/beqa.gozalishvili

abdullah5490 commented 3 years ago

Hello. Today i've started to post all of above issues on official bugs tracker. As per now, I created cards for 5 major issues where I need a support from you people via Votes/comments. Kindly visit each link one by one and play your role. I'll share more in next comments by the time.

Unlabeled buttons in the interface: https://bugs.telegram.org/c/3030

No sent/delivered/read/played status on outgoing messages: https://bugs.telegram.org/c/3031

Inaccessible share menu if launched via other apps: https://bugs.telegram.org/c/3032

Don't read message if it contains an animated gift/large emoji: https://bugs.telegram.org/c/3034

Can't play voice message if its in reply to a previous voice message: https://bugs.telegram.org/c/3036

Note: if someone else create any new issue, please do share here so i'll not make a duplicate. Thanks.

Simon818 commented 3 years ago

The accessibility of the bug tracker is about as good as the accessibility of Telegram. Abysmal HTML markup and I have no idea how to vote on issues. I also don't want to play the vote game. Either you care about accessibility or you don't. We're not going to compete with nice-to-haves, nor should we have to. Accessibility is not a nice-to-have.

jadesharp1992 commented 3 years ago

Here here! Completely agree with this! On another note, there's a new beta out on testflight now, and in groups, the open profile button is now labelled, and voiceover seems to be reading replies to messages differently. The big frustration for me still though, is voiceover will only read 10 messages at a time. We should be able to scroll through all of them, and it not be a problem. If I have loads of messages to read, I am having to use Unigram on windows, and this shouldn't have to be the case.

Sent from my iPhone

On 13 Mar 2021, at 21:40, Simon Jaeger @.***> wrote:

The accessibility of the bug tracker is about as good as the accessibility of Telegram. Abysmal HTML markup and I have no idea how to comment or vote on things. I also don't want to play the vote game. Either you care about accessibility or you don't. We're not going to compete with nice-to-haves, nor should we have to. Accessibility is not a nice-to-have.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

burakyuksek commented 3 years ago

The accessibility of the bug tracker is about as good as the accessibility of Telegram. Abysmal HTML markup and I have no idea how to comment or vote on things. I also don't want to play the vote game. Either you care about accessibility or you don't. We're not going to compete with nice-to-haves, nor should we have to. Accessibility is not a nice-to-have.

You can comment on an issue in the bug tracker by clicking on the "add more information about this issue" link, after you sign in.

Simon818 commented 3 years ago

@jadesharp1992 I noticed the replies thing, and definitely have mixed feelings on it. Imagine listening through a giant novel of a message just to hear the reply to that message. Having a way to jump back to the original message--or better yet, a UI design that opens up the thread the way iMessage does--would honestly be a lot better. But I'm glad we can see which message is being replied to.

@burakyuksek Thanks, I updated my comment. For some reason I assumed that button was different from commenting.

jadesharp1992 commented 3 years ago

Yeah, the replies thing looks like the bright guide app that's out there that's designed for voiceover users, that does the same thing with replies. Even that's not great with keeping up with messages though, it will only show you about 10 at a time with voiceover, and there's no way on there to clear group chats either.

Sent from my iPhone

On 13 Mar 2021, at 23:45, Simon Jaeger @.***> wrote:

@jadesharp1992 I noticed the replies thing, and definitely have mixed feelings on it. Imagine listening through a giant novel of a message just to hear the reply to that message. Having a way to jump back to the original message--or better yet, a UI design that opens up the thread the way iMessage does--would honestly be a lot better. But I'm glad we can see which message is being replied to.

@burakyuksek Thanks, I updated my comment. For some reason I assumed that button was different from commenting.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Simon818 commented 3 years ago

I noticed that VoiceOver issues are silently being fixed. It would be great to have reports somewhere, but at least it's happening. One example is that we can now read messages with stickers or animated emoji, where they were previously just excluded from VoiceOver order altogether.

abdullah5490 commented 3 years ago

Yes i did create a card for 5 issues not long ago. Out of those, 2 has been fixed in v7.5 release. One is this related to stickers another is about voice message playback when replied to a previous message. i have a plan to create more cards there.

On Tue, Mar 30, 2021, 2:25 AM Simon Jaeger @.***> wrote:

I noticed that VoiceOver issues are silently being fixed. It would be great to have reports somewhere, but at least it's happening. One example is that we can now read messages with stickers or animated emoji, where they were previously just excluded from VoiceOver order altogether.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/TelegramMessenger/Telegram-iOS/issues/267#issuecomment-809725077, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADYWUUSO334Z2WG7FZQRMN3TGDV55ANCNFSM4LW2ORXA .

alexarnaud commented 3 years ago

I tried to contact the Telegram iOS team about VoiceOver support without luck. The Twitter account of Telegram suggested to me to create a suggestion on the suggestion too of Telegram.

Unfortunatly, the Telegram suggestion tool is not accessible with a screen reader. You'll need the help of a sighted person to support it. Please support the below suggestion and broadcast it to make sure we could have Telegram usable for the blind under iOS.

Here the link of the suggestion : https://bugs.telegram.org/c/5164

Thanks in advance.

marrie commented 3 years ago

Here's an issue I just found this morning.

highlight a message
swipe down to delete
tap delete for everyone, that being you and the user(s)
notice the yes and no icons don't read.

This same set of steps can apply in regard to conversations you want to delete as well in the main interface.

sevapopov2 commented 3 years ago

Hello, here is the telegram issue I have reported in the bug tracker that was found in telegram 7.8 Beta and that isn't fixed in telegram 7.9. The issue is that now we aren't able to find a player for controlling the playback of the voice message with VoiceOver. We cannot pause, speed up, stop voice messages while they are playing. So to stop them we have to close telegram from an app switcher. It is super inconvinient! https://bugs.telegram.org/c/6775

Simon818 commented 3 years ago

Has any progress been made on these since the update at the beginning of the year? There's still a ton of super frustrating bugs, the passcode screen is still broken, and new things keep happening. I don't want to turn this into a complaint thread, but I wonder if there's any point in continuing to report these. Even if a developer came out here and said "Hey, we appreciate the feedback and we're working with very limited resources, but we hear you", I'd feel a lot better about it. But the only person who has done that is not even an official Telegram developer. Frankly, I don't know if they're hearing the feedback or they just happen to be fixing things that are reported in some other way, because nobody from the team has commented on any issues as far as I know. At least when we started a discussion in the desktop client repository, we got some actual feedback about why accessibility was difficult at the time.

There's a fork of Telegram called Nicegram, I wonder if they would be more receptive to feedback.

Edited for clarity.

sevapopov2 commented 3 years ago

As far as I can tell nothing is changing. Well, at least in a better way. Only in worse. I am a member of a telegram Beta program for iOS and as I reported earlier the player is unusable now at all. You have to close telegram to be able to operate the app, enter the text in the message creating feeld after using the player. It is really frustraighting, I agree with you completely. I think we cannot do anything in this situation.

marrie commented 3 years ago

I thought the person in charge of this bug report was working on stuff? Any word from them? I also feel that this cycle has gone down hill.

sevapopov2 commented 3 years ago

Yes, it is silent. Telegram for android has got some accessibility issues also and they aren't fixed. I noticed that the developers don't care much about iOS app in general because Pavel Durov said that iOS is an awful platform blah blah. Even sighted people told me that iOS app isn't intuitive. If android were as comfortable in case of accessibility as iOS is, I wouldn't argue with that. But we are left in the situation when the iOS platform is less apreciated by devs of telegram in general I believe. So it's difficult to wait for something about accessibility.

ali-fareed commented 3 years ago

The Voiceover-related issues are well known and being worked on. Unfortunately, with the release schedule as tight as Telegram's, and with only two developers, it is not always possible to fix everything in time.

Simon818 commented 3 years ago

I think we could all use the reminder of how small the development team is. I also hear rumblings of accessibility improvements in the latest release, which is excellent. Frankly though, whoever is dictating this release schedule seems somewhat at fault. The relatively fast-paced development of other features just means that the continued accessibility barriers are that much more noticeable. All this cool new stuff got added, but I still can't mute and unmute myself or hang up a call. It all starts to feel a bit like begging for scraps while the sighteds get to sit at the table and have all 7 courses. That being said, I appreciate the perspective and I hope it's clear that we're not holding any one person at fault for this. It's an ongoing and widespread problem and it's unfortunate that there's a mess to clean up at all. I appreciate the work that has been done, and I acknowledge that the app in its current form is miles ahead of how it was when I started trying to make noise about accessibility. If there's some way we can help organize this into a comprehensive list of serious issues and minor ones, I'd be happy to help. I know that every time this thread gets a new comment, it becomes one more thing to look through.

jadesharp1992 commented 3 years ago

Hi everyone, so I am on the beta for telegram. On the latest beta, I can scroll through chats and they now read properly with voiceover and I can access my whole contact list now rather than it reading a few contacts at a time and then getting stuck, but then I was chatting to someone last night who got the update of version 8.0 on the app store, and he can't read his contact list all the way through with voiceover? I wonder if the app store release and the testflight version are different?

Sent from my iPhone

On 1 Sep 2021, at 11:03, Simon Jaeger @.***> wrote:

I think we could all use the reminder of how small the development team is. I also hear rumblings of accessibility improvements in the latest release, which is excellent. Frankly though, whoever is dictating this release schedule seems somewhat at fault. The relatively fast-paced development of other features just means that the continued accessibility barriers are that much more noticeable. All this cool new stuff got added, but I still can't mute and unmute myself or hang up a call. It all starts to feel a bit like begging for scraps while the sighteds get to sit at the table and have all 7 courses. That being said, I appreciate the perspective and I hope it's clear that we're not holding any one person at fault for this. It's an ongoing and widespread problem and it's unfortunate that there's a mess to clean up at all. I appreciate the work that has been done, and I acknowledge that the app in its current form is miles ahead of how it was when I started trying to make noise about accessibility. If there's some way we can help organize this into a comprehensive list of serious issues and minor ones, I'd be happy to help. I know that every time this thread gets a new comment, it becomes one more thing to look through.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

sevapopov2 commented 3 years ago

Hi, I have just checked the case. I am using telegram beta also and I have the same result as your friend has. I can scroll between some contacts and then the focus is stuck. I have to scroll the list manually with 3 fingers. Do you still have issue with scrolling chats?

jadesharp1992 commented 3 years ago

Hi, so I am running IOS 15, beta 8. I can scroll through my contact list absolutely fine, and I can also read through chats without any issues too. Maybe uninstall and reinstall telegram? That could help?

Sent from my iPhone

On 1 Sep 2021, at 12:30, Vsevolod Popov @.***> wrote:

Hi,

I have just checked the case. I am using telegram beta also and I have the same result as your friend has.

I can scroll between some contacts and then the focus is stuck. I have to scroll the list manually with 3 fingers.

Do you still have issue with scrolling chats?

--

Best regards,

Vsevolod

https://github.com/sevapopov2 https://github.com/sevapopov2

From: jadesharp1992 @.> Sent: Wednesday, September 1, 2021 1:41 PM To: TelegramMessenger/Telegram-iOS @.> Cc: Vsevolod Popov @.>; Comment @.> Subject: Re: [TelegramMessenger/Telegram-iOS] accessibility related bugs with voiceover (#267)

Hi everyone, so I am on the beta for telegram. On the latest beta, I can scroll through chats and they now read properly with voiceover and I can access my whole contact list now rather than it reading a few contacts at a time and then getting stuck, but then I was chatting to someone last night who got the update of version 8.0 on the app store, and he can't read his contact list all the way through with voiceover? I wonder if the app store release and the testflight version are different?

Sent from my iPhone

On 1 Sep 2021, at 11:03, Simon Jaeger @. <mailto:@.> > wrote:

I think we could all use the reminder of how small the development team is. I also hear rumblings of accessibility improvements in the latest release, which is excellent. Frankly though, whoever is dictating this release schedule seems somewhat at fault. The relatively fast-paced development of other features just means that the continued accessibility barriers are that much more noticeable. All this cool new stuff got added, but I still can't mute and unmute myself or hang up a call. It all starts to feel a bit like begging for scraps while the sighteds get to sit at the table and have all 7 courses. That being said, I appreciate the perspective and I hope it's clear that we're not holding any one person at fault for this. It's an ongoing and widespread problem and it's unfortunate that there's a mess to clean up at all. I appreciate the work that has been done, and I acknowledge that the app in its current form is miles ahead of how it was when I started trying to make noise about accessibility. If there's some way we can help organize this into a comprehensive list of serious issues and minor ones, I'd be happy to help. I know that every time this thread gets a new comment, it becomes one more thing to look through.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/TelegramMessenger/Telegram-iOS/issues/267#issuecomment-910159115 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ALAPEDG6CJ45HVBSV6SH33TT7X7MDANCNFSM4LW2ORXA . https://github.com/notifications/beacon/ALAPEDFXO2E3CFCLB4DWQQDT7X7MDA5CNFSM4LW2ORXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGY762CY.gif

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

sevapopov2 commented 3 years ago

What I notice is that the issue appears in some versions and disappears also. Before the contacts button there are 2 elements that aren’t announced by VoiceOver. I believe it also happened like that.

pitermach commented 3 years ago

I think this may be related to iOS 15 more than Telegram fixing something, because even before yesterday's telegram update the app started scrolling. It started around iOS 15 beta 5 or 6.

jadesharp1992 commented 3 years ago

This is interesting, the scrolling in ios 15 seems to have fixed telegram then, but when you are in twitter the main ios app, when you scroll down your timeline, voiceover loses focus and jumps to the latest tweets button, so it's very interesting how it's working with telegram, but not with other apps. It broke another app, backpack studio that I use, so I had to talk to the developer and he fixed it in the latest beta build.

Sent from my iPhone

On 1 Sep 2021, at 13:49, pitermach @.***> wrote: I think this may be related to iOS 15 more than Telegram fixing something, because even before yesterday's telegram update the app started scrolling. It started around iOS 15 beta 5 or 6.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

marrie commented 3 years ago

Yes they are in most cases. Or at least the build numbers are, the main version might not be.

sevapopov2 commented 3 years ago

Hello, Today the telegram beta was updated and the bug with reading replied messages was fixed! Now it reads just reply for the message like it was before the bug. I have a suggestion: @ali-fareed Could you please make an option in VoiceOver rotor actions that would allow us to move to a quoted message when we are on replied message? It is made like that in whatsapp. If this option is available, we could quickly jump to original message when we want to check to what message a person is replying. Thank you!

sevapopov2 commented 3 years ago

@abdullah5490 How do you add a tag "accessibility" to cards on bug tracker? I could do it one time accedentaly, but one time it didn't work. How do you add tags to a card? Maybe I don't do that correctly, but first I type accessibility in search field, press enter, type iOS, press enter, and then I start to create a card. I notice that I cannot change tags there. How do you perform it? I would like to edit one of the cards to fix it if it's possible. Thank you!

abdullah5490 commented 3 years ago

@abdullah5490 How do you add a tag "accessibility" to cards on bug tracker? I could do it one time accedentaly, but one time it didn't work. How do you add tags to a card?

Well, I never did any special steps to add tags. As i remember, it assigned tags automatically by subject line.

sevapopov2 commented 3 years ago

Thank you for your answer, also do you know if it is possible to edit the card that was already created? How do you perform that? I cannot find a way to do it running NVDA and chrome on windows. If you know please tell.

zersiax commented 2 years ago

Ok, I spent a week pretty much forced to use Telegram on the phone and unfortunately, the experience was not very pleasant with VoiceOver. While I can do some of the basic interactions I would expect from a chat plagform, some admittedly minor, but very impactful issues hamper the experience to the point of serious frustration:

The often mentioned scrolling issue is by far the main one. In iOS 15, I can scroll through my chats list using standard VoiceOver gestures. I have no idea if that was possible in the past, I didn't need to do it much, but it can at least be done now.
What I cannot do, is scroll through chats. In private chats, this usually means you can see up to 20 or so messages if that. In group chats, this often gets reduced to a handful. Either way, if you want to see more, you are , excuse my French, shit out of luck if you use VoiceOver, at least in my experience. Using three-finger swipes does not work, using a double-tap-and-hold with one finger to then drag the screen up and down usually results in inadvertently opening the context menu for the message in focus rather than scrolling. This requires literally everyone I interact with to ration their messages so they don't get lost in the scroll. I hope I don't need to explain how ridiculous of a notion that is.
When playing voice messages, the voice message player controls are entirely invisible to VoiceOver for as far as I can tell. This iss an issue because you can't properly pause, rewind, speed up or slow down voice messages. In fact, I am stuck in a state where voice messages play at double speed because of a setting I changed when this was still accessible, and now cannot change that back. My sincere thanks.
I like the fact we can see what a message is replying to. What I don't like , is how that feature was implemented. The way it's done now, I have to listen to the ENTIRE message being replied to , all the way through, including all the voiceover verbiage, before I can actually read the message. This is incredibly inefficient, frustrating and it takes ages to get anything done. I already lament the productivity of touch screen devices on a daily basis and this REALLY isn't helping. Either make this information queryable, add it to the end of the message instead of the beginning, or only show an excerpt , and not the entire thing. After the fifth reply in a conversation I was about ready to toss my phone in the nearest paper shredder.

I know this is being worked on. I know this issue exists precisely because it is. But seriously guys ... this issue is 1.5 years old. And most of the issues I just reported are either regressions, or were there for that entire time. We have all the expertise here to make sure this doesn't happen and yet, it happens. Again. And again. And quite honestly, I am done being nice and tentative about this. These issues make the app an absolute garbage ffire to use compared to what's out there, the fact that they remain for this long without being fixed is very, very close to deliberate exclusion if not right on the mark already and I for one would like to see justification for why an entire group of people being excluded like this is not a higher priority issue.

fatihyuksek1 commented 2 years ago

I found a workaround for reading of replies:Switch to lines mode in the voiceover rotor, and then try to red that message line by line. That’s more comfortable imho. Windows için Posta ile gönderildi Kimden: Florian BeijersGönderilme: 23 Eylül 2021 Perşembe 12:54Kime: TelegramMessenger/Telegram-iOSBilgi: Fatih Yüksek; CommentKonu: Re: [TelegramMessenger/Telegram-iOS] accessibility related bugs with voiceover (#267) Ok, I spent a week pretty much forced to use Telegram on the phone and unfortunately, the experience was not very pleasant with VoiceOver.While I can do some of the basic interactions I would expect from a chat plagform, some admittedly minor, but very impactful issues hamper the experience to the point of serious frustration:The often mentioned scrolling issue is by far the main one. In iOS 15, I can scroll through my chats list using standard VoiceOver gestures. I have no idea if that was possible in the past, I didn't need to do it much, but it can at least be done now.What I cannot do, is scroll through chats. In private chats, this usually means you can see up to 20 or so messages if that. In group chats, this often gets reduced to a handful. Either way, if you want to see more, you are , excuse my French, shit out of luck if you use VoiceOver, at least in my experience. Using three-finger swipes does not work, using a double-tap-and-hold with one finger to then drag the screen up and down usually results in inadvertently opening the context menu for the message in focus rather than scrolling. This requires literally everyone I interact with to ration their messages so they don't get lost in the scroll. I hope I don't need to explain how ridiculous of a notion that is.When playing voice messages, the voice message player controls are entirely invisible to VoiceOver for as far as I can tell. This iss an issue because you can't properly pause, rewind, speed up or slow down voice messages. In fact, I am stuck in a state where voice messages play at double speed because of a setting I changed when this was still accessible, and now cannot change that back. My sincere thanks.I like the fact we can see what a message is replying to. What I don't like , is how that feature was implemented. The way it's done now, I have to listen to the ENTIRE message being replied to , all the way through, including all the voiceover verbiage, before I can actually read the message. This is incredibly inefficient, frustrating and it takes ages to get anything done. I already lament the productivity of touch screen devices on a daily basis and this REALLY isn't helping. Either make this information queryable, add it to the end of the message instead of the beginning, or only show an excerpt , and not the entire thing. After the fifth reply in a conversation I was about ready to toss my phone in the nearest paper shredder.I know this is being worked on. I know this issue exists precisely because it is. But seriously guys ... this issue is 1.5 years old. And most of the issues I just reported are either regressions, or were there for that entire time.We have all the expertise here to make sure this doesn't happen and yet, it happens. Again. And again. And quite honestly, I am done being nice and tentative about this.These issues make the app an absolute garbage ffire to use compared to what's out there, the fact that they remain for this long without being fixed is very, very close to deliberate exclusion if not right on the mark already and I for one would like to see justification for why an entire group of people being excluded like this is not a higher priority issue.—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

zersiax commented 2 years ago

@fatihyuksek1 oof :( careful when responding via email, your email client left a BUNCH of garbage around your actual answer.

fatihyuksek1 commented 2 years ago

I cannot control it, sorry.

iPhone’umdan gönderildi

Florian Beijers @.***> şunları yazdı (23 Eyl 2021 16:41):

@fatihyuksek1 oof :( careful when responding via email, your email client left a BUNCH of garbage around your actual answer.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

marrie commented 2 years ago

They fixed this in the latest app store update a few days ago I believe, at least the reply function, so I’ve been told.

sevapopov2 commented 2 years ago

Hello. Yes, fortunately they fixed the reply to message thing, but now it isn't possible to find an original message again. The issue why we are kept from telegram good accessibility is simple and really sad. Pavel Durov, the creator of telegram, always said and says that people with disabilities is not his market, that his apps are not ment to be accessible and even used by people with disabilities. Before telegram, he was the director of a russian social network vkontakte, which is translated as in contact and has a short name vk. When he worked there, we had absolutely the same thing regarding accessibility. 1000 reports were sent, the support agents always answered with really stupid suggestions for help, like to press on a pen sign to edit a post on the wall and other things. Only when Pavel has gone from vk, we could make a petition and vk is now, well, much more accessible than it was. It is not ideal, but it is a lot more usable than in the past when Pavel Durov was a director of it. But what is more strange for me is that telegram for android is practically completely accessible. Yes, it has it's issues with settings page for example, but the issues in telegram for android were always fixed and when accessibility started it's building in telegram, android was the most accessible solution from the beginning. I still hope that issues in iOs client will be fixed. There are also issues in web clients and desktop for windows, mac and linux which are completely inaccessible. This is all the falt of the creator of vk and telegram who has that position.

marrie commented 2 years ago

If this is true, that is sad that the creator does not care about accessibility. That to me is a gross violation of every accessibility law out there. I hope [these issues do get looked into, asi I would love to get telegram working on iOs flawlessly so I don’t have to use third party apps.

Simon818 commented 2 years ago

In 2019 when Telegram X arrived and was completely unusable, he actually took the time to reply to a VoiceOver user on his fairly inactive Twitter account:

I'm not the GitHub police, but I do think keeping this discussion on-track with development--rather than people--is something to keep in mind. If you want to edit your original comment with a source though, I would be interested to see evidence to the contrary directly from him, rather than a support team--not a position typically known for having good accessibility training. Being unaware is one thing; actually stating that accessibility doesn't matter would be a very disastrous thing to do.

sevapopov2 commented 2 years ago

Well, of course I know what github is needed for. The reason why I wrote my comment is to answer to the question that Florian asked about why are we treated like that. I decided to tell the whole story. You attached this response from twitter. Do you see any significantly improved result? I was a beta tester of bright guide, and I noticed that when bright guide was already out, telegram started improving it's accessibility, but they did it only when bright guide got new updates and they were released in appstore.

marrie commented 2 years ago

Do we have a link to the whole thread? I would want to see this with dates.

alekssamos commented 2 years ago

Completely broke the accessibility of the message menu

Attention, urgent! In the latest beta version, it was broken To open the message menu: Reply, Edit, Copy, Forward, Delete, Select. It is completely no longer available for Voiceover in any way. Don't update!

marrie commented 2 years ago

Yep, it’s a bit broken here I think in stable? Not sure. Man I really wish all of these issues could be fixed, and fixed for good. Also the schedular is broken as well, when you hold on send.

sevapopov2 commented 2 years ago

I can also confirm the bug about menu. It's good to know that a schedulerworked before with VoiceOver, I didn't even know that. What do you think, is there any sense to post this bug report about menu on a support bot? Or it is better for someone to create a card on a bug tracker? When I was creating cards, they weren't tagged with right tags and it wasn't possible to edit them. Any thoughts about that? How could we try to move it forward?

marrie commented 2 years ago

I would create a bug on github then reference the issue here via the reference issue button when leaving a comment. The scheduler I think always has been broken. I just didn’t know about it until several weeks ago, as I didn’t know you could schedule messages. We do need to move all of these bugs forward a bit faster though if at all possible. Can anyone else here look at the source and submit pull requests? I’m not one who can, I just brake things.

Simon818 commented 2 years ago

Has anyone put this in the iOS beta testing group? That's where bugs with the beta should be announced.

TelegramMessenger / Telegram-iOS