Dear Shankar, You are right about that.
The reality is that the actual effort—the hours spent digging into these applications, filing bug reports, and managing the constant follow-ups—is falling squarely on my shoulders, not the group's. I have reached a point of deep frustration. It feels like the only way to get our voices heard is to spam their support channels with our requests until they acknowledge us, as I simply do not see any other effective path forward. Life is far too busy to be constantly following up with the CCPD and filing formal complaints on their portal. While I know they do their best, this entire process requires a level of effort that must be put in outside of regular work hours. This leaves me with almost no time to actually indulge socially; even on weekends, I am tied to my computer checking and replying to mails, filing bugs, and reporting them to various companies. I do have a social life, but I cannot fully participate in it because of this. I could easily tell myself that it is not my job and leave it for someone else to address accessibility, but how can I say that when my own life is directly affected by these inaccessible digital products that are supposed to make life convenient? Until then, SPAM ON! P.S. Zoher, who is this Mujtaba? I think the mail you received was from Mister Kayne. So you should be replying to Mister Kayne and avoid addressing someone else in your reply. I just noticed this today. From: [email protected] <[email protected]> On Behalf Of Shankar C Sent: Monday, June 1, 2026 10:27 AM To: [email protected] Subject: Re: [AI] Forward as is: Urgent: Accessibility Non-Compliance with WCAG 2.2 – Blinkit Web & iOS Applications Based on my recent observations, it appears that companies such as Swiggy, Zomato, Blinkit, and Rapido are failing to adequately support screen reader users. Often, these organizations seem to prioritize paying fines over implementing meaningful, long-term accessibility improvements. Rather than addressing issues comprehensively in major updates, they tend to resolve only one or two minor items at a time, resulting in prolonged delays even after regulatory penalties are imposed. Furthermore, these companies frequently fail to employ qualified accessibility testers, which prevents them from achieving clear, sustainable results. It is concerning that these platforms continue to neglect the needs of their visually impaired user base, rather than integrating inclusive design as a standard practice for all customers. On Fri, May 29, 2026 at 6:29 PM Mister Kayne <[email protected]<mailto:[email protected]>> wrote: Noted, thank you for mentioning that correction, can you make the change and send the mail please 😊 From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Zoher Kheriwala Sent: Thursday, May 28, 2026 10:38 AM To: [email protected]<mailto:[email protected]> Cc: AccessIndia Group <[email protected]<mailto:[email protected]>> Subject: Re: [AI] Forward as is: Urgent: Accessibility Non-Compliance with WCAG 2.2 – Blinkit Web & iOS Applications Dear Mujtaba, Your draft seems okay, but there is one error that you cannot make Any app developer to follow 2.2 that is You cannot use the word Wcag CAG 2.2 compliant you have to use WCAG 2.2 conformance. The compliance means you have to follow a particular rule or regulation or act provided by the government. Sent from my iPhone On 28 May 2026, at 9:31 AM, Mister Kayne <[email protected]<mailto:[email protected]>> wrote: Dear Group, Please send individual mails to this ID, subject and content provided. To: [email protected]<mailto:[email protected]> Subject: Urgent: Accessibility Non-Compliance with WCAG 2.2 – Blinkit Web & iOS Applications Importance: High Dear Blinkit Technical Team, I am writing to formally bring to your attention significant accessibility issues observed across both the Blinkit web platform and iOS application. Based on my assessment, these platforms currently demonstrate substantial non-compliance with established Web Content Accessibility Guidelines (WCAG) 2.2. These gaps create meaningful barriers for users with disabilities and are not aligned with inclusive design principles. More importantly, such non-compliance constitutes a violation of the Rights of Persons with Disabilities (RPWD) Act, 2016, which mandates accessible digital services. Continued non-adherence may attract regulatory scrutiny and potential legal consequences. Given the seriousness of this matter, I strongly request your team to: • Conduct a comprehensive accessibility audit against WCAG 2.2 standards • Define and initiate a structured remediation plan • Achieve substantial compliance within the next 90 days I urge your organization to prioritise remediation efforts and address critical accessibility gaps at the earliest. Please note that in the absence of appropriate action or demonstrated progress within the stated timeline, I will be required to escalate this matter formally by filing a complaint with the Chief Commissioner for Persons with Disabilities (CCPD) regarding your non-compliance. -- -- 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 visit https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/TYZPR02MB9171888ECC7ABCBAA018486F9D152%40TYZPR02MB9171.apcprd02.prod.outlook.com.
