Recent updates to WhatsApp Desktop have introduced significant accessibility barriers for users who rely on screen readers like **NVDA** and **JAWS** to communicate independently.

One of the most critical issues is the lack of reliable in-chat audio cues or automatic screen reader announcements for incoming messages when a conversation window is already open. Without this real-time feedback, blind users must constantly switch back to the chat list (often using cumbersome navigation) to manually check for new messages. This breaks the flow of conversations, causes unnecessary delays, and makes real-time chatting far more effort-intensive than it should be.

Additional key concerns include:
- Excessive key presses and tabbing required to reach the reply/input field, due to too many focusable (but often irrelevant or unlabeled) elements cluttering the path between the message list and the text box.
- Erratic and confusing focus shifts during keyboard navigation, which disrupts predictable workflows and increases cognitive load.
- Other screen reader-specific barriers, such as inconsistent handling of dynamic content, poor labeling of controls, and conflicts between browse/focus modes in the web-based wrapper.

These regressions primarily impact users of assistive technologies on the Windows desktop app, which Meta transitioned from a native application to a web-based version (using WebView2/Edge wrapper) starting around late 2025. The switch was implemented without meaningful prior notice—users were often suddenly logged out of the reliable native app, forced to re-pair via their phone, and presented with the new web-based interface that broke established workflows. This abrupt, unannounced forced migration left blind and visually impaired users scrambling, with no fallback option, exacerbating feelings of exclusion and frustration as reported in NVDA/JAWS communities and accessibility forums.

While community add-ons like WhatsApp-Enhancer or WhatsAppNG offer partial workarounds—such as custom shortcuts (e.g., Alt+1 for chats, Alt+2 for messages, Alt+D for input), forcing focus mode, or filtering phone numbers—these are temporary fixes that shouldn't be necessary. The core app should provide native, reliable accessibility out of the box.

Accessibility is a fundamental requirement for equal access to digital communication tools like WhatsApp, which billions rely on daily for personal, professional, and social connections—especially in places like India where it's a primary means of staying connected. Excluding blind and visually impaired users through avoidable design choices and unannounced forced migrations is unacceptable and contrary to global standards like WCAG.

We respectfully urge the WhatsApp team (Meta Platforms, Inc.) to prioritize these fixes with the same urgency as security or core functionality issues:

1. Implement reliable, automatic in-chat screen reader announcements (audio/beep + spoken notification) for incoming messages, even when the conversation is focused, similar to how mobile versions handle alerts.
2. Streamline and stabilize keyboard navigation and focus management, reducing unnecessary focusable elements and preventing erratic jumps.
3. Eliminate extra navigation barriers between essential areas (chat list, message history, and input field) to make replying quick and intuitive.
4. Integrate regular accessibility testing with real blind users and screen reader experts into the development and update process, commit to preventing future regressions, and ensure major changes like app transitions include advance notice, beta testing for accessibility, and options for users to opt out or revert if issues arise.

By addressing these promptly, WhatsApp can ensure inclusive, efficient communication for everyone. Thank you for your attention—accessibility matters, and we look forward to meaningful improvements.