Hi everyone,
I am writing to the group to highlight the significant accessibility challenges many of us are facing with the latest WhatsApp Desktop interface update for Windows. As many of you have noticed, Meta has transitioned the desktop application to a web-based wrapper (WebView2), which has unfortunately broken many established screen reader workflows, keyboard shortcuts, and overall stability. Where to report the issue: Please take a moment to file a formal ticket with Meta. Even if you feel it is a drop in the bucket, volume matters for their accessibility metrics. You can report the technical challenges here: WhatsApp Accessibility Support Form <https://www.whatsapp.com/contact/?eea=1&subject=messenger&form_type=accessi bility> A Note of Caution (Managing the AI Response): When you submit your ticket, please be prepared: you will almost certainly receive an automated, AI-generated reply. This is currently typical behavior for Meta's support teams. Do not let this discourage you or make you feel that your report has been ignored. How to effectively "Mark" your feedback: To ensure our voices are actually heard and recorded as a failure in their system, please follow this strategy: 1. Prepare in Advance: Before you even open the support link, write down all the details of your issue in a Notepad file. Include your OS version, the Screen Reader you use (NVDA, JAWS, etc.), the steps to reproduce the bug, and a detailed description of the challenge. 2. The Survey is the Key: Once the ticket is "closed" or you receive that initial AI response, you will eventually be sent a survey asking how they did. Mark them as negative on every single parameter. 3. Use the Edit Box: At the end of the survey, if there is a text box asking for additional comments, paste your entire challenge from your notepad into that box. 4. The Checkbox Rule: Anywhere else you encounter a text box that is triggered by a checkbox, ignore their prompt and instead type: "Support did not address my accessibility challenge". By marking them negatively across the board and re-pasting our technical issues into the survey boxes, we force these failures into their quality-control data, which is harder for them to ignore than a standard support ticket. Let's make sure they understand that "new" shouldn't mean "broken" for the accessibility community. Sincerely, Mujtaba Merchant Bangalore | INDIA Mail: [email protected] Website: The Somebody, Nobody, Anybody <https://www.mister-kayne.com/> & Everybody Blog! Sent from Outlook R for Windows 10 -- 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/000001dc7633%245d33ae70%24179b0b50%24%40gmail.com.
