Edited email: I have given so much hide meaning in the above email. Kindly read at least two times.
On Sun, 28 Jan 2024 at 21:29, Ashutosh Singhal <[email protected]> wrote: > I have given so much hide content in the above email, Kindly read at > least two times. > > On Sun, 28 Jan 2024 at 21:25, Ashutosh Singhal < > [email protected]> wrote: > >> I have mainly 3 following points regarding it: >> * Google Accessibility Scanner App: From this App developer can know the >> basic accessibility issues of his/her Android app. It does not have all the >> required features for us that's why I have already given feedback to Google >> Disability Answer Desk to make it easier, advanced accessibility issue >> detector, user friendly for Disabled, availability for PC and much more. >> You should also give your feature requests or report any bug regarding >> any Google Product like Google Lookout, TalkBack, TTS, Voice Access and >> YouTube etc to them as I always say When companies get a lot of feedback on >> the same feature or bug that time companies work faster. I am giving below >> the Google Disability Answer Desk contact link. you can Call, Chat, Email, >> Be My Eyes Call and SignLanguage according to your requirement. >> >> https://support.google.com/accessibility/answer/7641084?hl=en&ref_topic=9071908&sjid=199523313426904780-AP#zippy=%2Chours-languages-for-google-disability-support-team >> >> * Service Provider Accessibility Team: I read somewhere that every >> service, especially Digital service should be Accessible for Persons With >> Disabilities in India regardless Private or Government. For it they should >> have an Accessibility Answer Desk for their Disabled Users so any >> accessibility issue regarding their service can be notified and fixed >> easily. >> >> * Service Provider own Accessibility Features: I believe that some big >> tech companies like Meta: Facebook, WhatsApp and Instagram, Twitter/X App >> and Telegram etc should have their own Screen Reader, OCR, Magnifier, >> Colour contrast, Live Transcribe and others Accessibility Features for all >> the 21 Disabilities. These companies can provide these features because >> they have enough resources. If they provide their own Accessibility >> Features, Accessibility issues may not come frequently like now, that time >> they can not play blame game on the behalf of third party Screen Reader or >> Accessibility service and if we face any accessibility issue by using any >> third party software that time we can use their own accessibility feature >> may be we will not get any issue to use that even though if we face any >> issue so we can directly point out to them because that time their >> accessibility features are also not working. >> Sorry my english is bad. I hope I made some sense. >> Regards, >> Ashutosh Singhal >> +91 8076798104 >> >> On Sat, 27 Jan 2024 at 14:28, Yamuna Jivana Dasa <[email protected]> >> wrote: >> >>> Dear Yatin, and anyone interested in software accessibility in general, >>> >>> Yatin, You’ve written a nice letter. Others on this list have done this >>> and shared also here. We are always greatful when some of us make the >>> effort to liaise with companies for accessibility, although we know well >>> usually they will not take seriously. The attempt is what counts. I thank >>> you and all who do this. >>> >>> >>> >>> Now to address the technically inclined on this list: I would like to >>> brainstorm. Often, the problem could be fixed from the screen-reader side. >>> At other times, the App developer may need specific information about >>> technical aspects that break accessibility in their apps, such as Window >>> names, handles and class, or the off-screen models and how they are >>> interacted with by the screen-reader, or fail to do so when they break >>> accessibility. >>> >>> The problem is that when end-users like us who are not too technically >>> clued up, we are unable to present those details in our letters to >>> developers. >>> >>> Take for example this statement in Yatin’s letter: >>> >>> >>> >>> “Crippled reading control: Navigating long messages in channels, >>> groups, and personal chats is incredibly challenging due to the absence of >>> character-by-character, word-by-word, line-by-line, or >>> paragraph-by-paragraph reading options. This bug, introduced in November >>> 2021 and despite repeated reports, remains unaddressed, severely impacting >>> the user experience for individuals who rely on screen readers.” >>> >>> >>> >>> At first glance, it may appear to the developer from Yatin’s letter that >>> this is a function of the screen-reader, not of the app. Yet something in >>> the app has broken the screen-reader’s ability to read text by the various >>> reading mode granularity. >>> >>> >>> >>> It may be a nice idea if we could start some sort of forum where letters >>> detailing problems in Apps accessibility by end-users can be first referred >>> to a technically inclined tester, who could then modify the end-user’s >>> letter to include possible app coding adjustments that could fix >>> accessibility. >>> >>> Or perhaps the tester could ascertain that the problem is better written >>> for from the screen-reader’s capability. This is true more so when new >>> features become more widely used so that screen-readers might be trained >>> for such functionality in general, opening up accessibility for more Apps >>> that use such features or functions in their coding. >>> >>> >>> >>> Any thoughts? >>> >>> >>> >>> Kind regards >>> >>> >>> >>> Yamuna Jivana dasa >>> >>> >>> >>> *From:* [email protected] [mailto: >>> [email protected]] *On Behalf Of *yatin panchal >>> *Sent:* Saturday, January 27, 2024 12:58 PM >>> *To:* [email protected] >>> *Subject:* [AI] Urgent accessibility concerns in telegram from visually >>> impaired user >>> >>> >>> >>> Dear Telegram Team, >>> >>> >>> >>> My name is Yatin Panchal, and I am writing to express my deep concern >>> about the declining accessibility of the Telegram platform for users who >>> rely on screen readers, like myself. As a visually impaired individual, I >>> heavily utilize assistive technologies like TalkBack for Android, VoiceOver >>> for iOS, NVDA, and JAWS for Windows to navigate and interact with digital >>> platforms. Unfortunately, Telegram's recent decline in accessibility >>> features has created significant hurdles in my ability to use the platform >>> effectively. >>> >>> >>> >>> Specifically, the lack of comprehensive screen reader support presents >>> several critical challenges: >>> >>> Limited chat window accessibility: Compared to apps like WhatsApp, >>> clicking the file sharing button in Telegram does not provide sufficient >>> information for screen readers. This makes it difficult for me to >>> understand and access shared files accurately. >>> >>> Crippled reading control: Navigating long messages in channels, groups, >>> and personal chats is incredibly challenging due to the absence of >>> character-by-character, word-by-word, line-by-line, or >>> paragraph-by-paragraph reading options. This bug, introduced in November >>> 2021 and despite repeated reports, remains unaddressed, severely impacting >>> the user experience for individuals who rely on screen readers. >>> >>> >>> >>> It is important to note that I am not solely focusing on Telegram. I >>> have also actively reported similar accessibility issues to Google in hopes >>> of improving TalkBack's functionality. My goal is not to pinpoint blame, >>> but rather to emphasize the collaborative effort needed to address these >>> challenges and ensure everyone can enjoy a truly inclusive digital >>> experience. >>> >>> >>> >>> Therefore, I urge you to prioritize and implement the following changes: >>> >>> Enhanced screen reader compatibility: Ensure all buttons, functions, and >>> menus are readily accessible and consistently announced by screen readers >>> like TalkBack, VoiceOver, NVDA, and JAWS. This will allow for seamless >>> navigation and interaction for users with diverse needs. >>> >>> Urgent resolution of the reading control bug: Fix the critical bug >>> impacting message navigation for screen readers as soon as possible. This >>> will significantly improve the usability and experience for countless >>> visually impaired users who rely on these features. >>> >>> >>> >>> Beyond these changes, I propose two additional actions to further >>> enhance accessibility and inclusivity within Telegram: >>> >>> Create a dedicated accessibility channel: This channel would serve as a >>> safe space for individuals with disabilities to report accessibility issues >>> directly to the Telegram team. This would streamline communication and >>> facilitate immediate feedback for ongoing improvement. >>> >>> Embrace diversity in your recruitment: Consider seeking input and hiring >>> talented individuals with disabilities, such as myself, to contribute to >>> your development team. This firsthand perspective would be invaluable in >>> identifying and addressing accessibility challenges, ultimately leading to >>> a more user-friendly and inclusive platform for everyone. >>> >>> >>> >>> Improving accessibility is not just a technical issue; it is a matter of >>> inclusivity and ensuring all users, regardless of their abilities, feel >>> welcome and valued within the Telegram community. I believe in Telegram's >>> potential and sincerely hope you will join hands with other platforms like >>> Google to address these critical concerns and promote a more accessible >>> digital landscape for everyone. By creating a dedicated accessibility >>> channel and embracing diversity in your workforce, you can open doors for >>> individuals like me and unlock new possibilities for enhanced accessibility >>> on Telegram. >>> >>> >>> >>> Thank you for your time and consideration. >>> >>> >>> >>> Sincerely, >>> >>> >>> >>> Yatin Panchal. >>> >>> -- >>> Disclaimer: >>> 1. Contents of the mails, factual, or otherwise, reflect the thinking of >>> the person sending the mail and AI in no way relates itself to its veracity; >>> >>> 2. AI cannot be held liable for any commission/omission based on the >>> mails sent through this mailing list.. >>> >>> >>> Search for old postings at: >>> http://www.mail-archive.com/[email protected]/ >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "AccessIndia" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/CALN9kY%2BcxqtArofkhHPB2RJ_ZNv_GQX9F-U71fMkC9tYS8zzGA%40mail.gmail.com >>> <https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/CALN9kY%2BcxqtArofkhHPB2RJ_ZNv_GQX9F-U71fMkC9tYS8zzGA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> -- >>> Disclaimer: >>> 1. Contents of the mails, factual, or otherwise, reflect the thinking of >>> the person sending the mail and AI in no way relates itself to its veracity; >>> >>> 2. AI cannot be held liable for any commission/omission based on the >>> mails sent through this mailing list.. >>> >>> >>> Search for old postings at: >>> http://www.mail-archive.com/[email protected]/ >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "AccessIndia" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/001301da50fe%24f68a1250%24e39e36f0%24%40gmail.com >>> <https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/001301da50fe%24f68a1250%24e39e36f0%24%40gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- Disclaimer: 1. Contents of the mails, factual, or otherwise, reflect the thinking of the person sending the mail and AI in no way relates itself to its veracity; 2. AI cannot be held liable for any commission/omission based on the mails sent through this mailing list.. Search for old postings at: http://www.mail-archive.com/[email protected]/ --- You received this message because you are subscribed to the Google Groups "AccessIndia" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/CAFL6VgLGCGruFTr4ZCp5kG%2B5TAK0aFLwkaSGqudc3M3jtYggRw%40mail.gmail.com.
