Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

127 views
Skip to first unread message

Mujtaba Merchant

unread,
Dec 26, 2025, 1:46:35 AM12/26/25
to Mujtaba Merchant

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

 

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: mujt...@gmail.com

Website: The Somebody, Nobody, Anybody & Everybody Blog!

Sent from Outlook ® for Windows 10

 

 

azhar...@gmail.com

unread,
Dec 26, 2025, 11:11:58 AM12/26/25
to nvda-...@nvaccess.org

Good initiative, I am facing lot of issues too on my Windows Desktop WhatsApp.

 

Azhar

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/000001dc7633%245d33ae70%24179b0b50%24%40gmail.com.

Sarah Alawami

unread,
Dec 26, 2025, 11:43:25 AM12/26/25
to nvda-...@nvaccess.org

Odd, I'm not having any such issues. I don't use any keyboard shortcuts mind you but it seems like it has become more accessible and a lot easier to use. I can finally get the code to work over m when I add my desktops and so much more. The interface does not appear to be missing any tab elements. it's not perfect, however it is a lot better than even a few months ago when I was struggling. No,I'm not using any add ons for nvda and what's app as far as I'm aware. I read about some of the issues , and i hope they do get solved.

--

Sergio Gómez

unread,
Dec 26, 2025, 1:02:19 PM12/26/25
to nvda-...@nvaccess.org
Hi Sarah,

I hope you're doing well. Thank you for sharing your experience with the new WhatsApp Desktop update. I completely agree with you. Personally, I find that the recent changes have made the application more accessible and user-friendly. Like you, I don't rely heavily on keyboard shortcuts, and I am quite satisfied with the current state of the interface.

In my opinion, the improvements, even if small, are a step forward compared to the previous versions. It's encouraging to see that some of us are having a positive experience with this update, and I hope that the issues others are facing get resolved soon.

Best regards,
Sergio

leoba...@gmail.com

unread,
Dec 26, 2025, 1:17:06 PM12/26/25
to nvda-...@nvaccess.org

Yeah, mostly a Jaws user here, but sometimes I switch to NVDA to help other folks do some stuff. New WebView2 interface on WhatsApp for Windows is both accessible and usable although I agree on the fact that an addon could add some shortcut keys to navigate quicker. I believe that the secret in this case is adaptation, not regression.

 

 

Cheers,

Leo Bado

 

“We don't rise to the level of our expectations, we fall to the level of our training.”   Archilochus.

azhar...@gmail.com

unread,
Dec 26, 2025, 5:26:24 PM (14 days ago) 12/26/25
to nvda-...@nvaccess.org

Hi All,

 

I am little lost about all this discussion about WhatsApp. Are we talking about the same thing.

 

I was using WhatsApp Windows Desktop App and it was working perfect until one fine morning I was logged out and when I got back in it was the new version and I found it absolutely terrible. The whole layout and accessibility is nothing like the pervious version.

 

Can someone suggest a solution.

 

Regards,

 

Azhar

 

 

From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of Sarah Alawami
Sent: December 26, 2025 11:43 AM
To: nvda-...@nvaccess.org
Subject: Re: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

 

Odd, I'm not having any such issues. I don't use any keyboard shortcuts mind you but it seems like it has become more accessible and a lot easier to use. I can finally get the code to work over m when I add my desktops and so much more. The interface does not appear to be missing any tab elements. it's not perfect, however it is a lot better than even a few months ago when I was struggling. No,I'm not using any add ons for nvda and what's app as far as I'm aware. I read about some of the issues , and i hope they do get solved.

Sarah Alawami

unread,
Dec 26, 2025, 10:10:11 PM (14 days ago) 12/26/25
to nvda-...@nvaccess.org

I just stay in focus mode and tab from area to area or in browse mode if I need to grab a code or copy a message. the app is not perfect but it gets the job done and is much more accessible than prior versions.

Mujtaba Merchant

unread,
Dec 27, 2025, 1:22:13 AM (14 days ago) 12/27/25
to nvda-...@nvaccess.org

Nice, I expected that more people would be having challenges with the new update on Windows for the desktop application, unless otherwise if you are talking about the web interface. Using NVDA with the Desktop application, please try doing this:
1. Select multiple messages in a chat.

2. Delete them, the messages in an individual or group chat, depending on which you will get delete for me or the option to delete for everyone.

3. Delete the chats, have fun trying to find the delete option but here is a clue, use tab a few times.

 

Once you delete the messages, you will hear an undo prompt, so this should have deleted the selected messages; but go back to the chat, did the messages delete OR do you still see them? This issue was reported by another member of our mailing list, but there was no response from anyone, to which I replied back with steps to perform the action but in turn found out myself that it is not possible to do. Hence, being the keyboard warrior I am, decided to report it to the Meta Whatsapp accessibility through their form, also felt that others who are experiencing this issue should also do the same. There is safety in numbers, and so is change!

 

Have a good one!

Mujtaba Merchant

unread,
Dec 27, 2025, 1:34:12 AM (14 days ago) 12/27/25
to nvda-...@nvaccess.org

I completely agree with Azhar on this one. My experience has been identical—the transition to the new version was sudden and the layout feels like a significant step backward in terms of intuitive accessibility. It’s a very different environment compared to the previous version we were all comfortable with.

 

I have to respectfully disagree with Sarah’s take. While I’m glad it’s working better for some, for my workflow, it’s been a major struggle. No hard feelings at all, but it just hasn’t been the improvement I was hoping for.

Hettie

unread,
Dec 27, 2025, 9:07:27 AM (13 days ago) 12/27/25
to nvda-...@nvaccess.org, Mujtaba Merchant

I agree with all who have problems with the webpage layout of Whatsapp. Reading and sending messages present no problems for me.

Deleting or saving a single message is fine.

When it comes to deleting multiple messages, it is night

If someone can write an add-on to enable NVDA to mark messages, that will help all of us. I think that sighted users will also welcome a "delete all" function as they are also complaining.


Hettie


Hettie

azhar...@gmail.com

unread,
Dec 27, 2025, 10:43:41 AM (13 days ago) 12/27/25
to nvda-...@nvaccess.org

I can’t even open the context menu using application key.

 

I wonder if Sarah and others are talking about the same application.

 

Azhar

Mujtaba Merchant

unread,
Dec 27, 2025, 10:50:07 AM (13 days ago) 12/27/25
to nvda-...@nvaccess.org

To open the context menu, focus on the message and use your right arrow key it will read context menu; then use spacebar to expand the context menu and the down arrow to read the options in it. How accessible! First you had to just use one keystroke now 3, brilliant and so damn productive

 


Sent: Saturday, December 27, 2025 9:14 PM
To: nvda-...@nvaccess.org

azhar...@gmail.com

unread,
Dec 27, 2025, 11:42:18 AM (13 days ago) 12/27/25
to nvda-...@nvaccess.org

Thanks Mujtaba, it worked, but did you notice that there is no Clear Chat option.

 

Azhar

leoba...@gmail.com

unread,
Dec 27, 2025, 1:23:42 PM (13 days ago) 12/27/25
to nvda-...@nvaccess.org

Accessible means it can be access, usable that it can be functionally used on a daily basis, there could be improvements, shortcut keys, but the definition of accessible is not threatened by any means. Meta is not going to pay a few dudes to continue to supporting an interface to satisfy a quite a small segment of the users only because they complain to the wind for hitting a few more keystrokes. Market doesn’t revolve around you!

 

 

Cheers,

Leo Bado

 

“We don't rise to the level of our expectations, we fall to the level of our training.”   Archilochus.

 

joseph....@gmail.com

unread,
Dec 27, 2025, 2:07:02 PM (13 days ago) 12/27/25
to nvda-...@nvaccess.org

Hi,

While blindness is one of the most visible disabilities around the world, the blindness experience is not taken into account when designing most products, including computer software user interfaces unless designers and developers are aware of disability issues and accessibility/usability barriers. Further, a product such as WhatsApp should also be viewed from the perspective of its developers (in this case, Meta) because when we send feedback like the effort described in this thread, we won’t reach the people responsible for maintaining the WebView2 version of WhatsApp unless our feedback is forwarded to appropriate places WITHIN Meta. In other words, think about who we are interacting with in the first place to make sure the words we use do reflect our thinking.

One strategy I recommend for a feedback effort like this thread is framing accessibility and usability issues as beneficial to Meta as an organization (this strategy might not work in some cases though). Think about it this way: if people send feedback messages without thinking about what Meta would think within its boardrooms and discussions among developers, the chances of the feedback being implemented would not be quite high. However, if the feedback is framed as an opportunity for Meta, then folks at Meta would see feedback as a chance to evaluate the accessibility of its products and at least say something, or if they can do so, find someone or a team to tackle accessibility and usability issues. Perhaps Meta then can say that they are focusing on accessibility, or if they want, market accessibility as a differentiating point for WhatsApp against similar services like GroupMe (Microsoft). IN other words, present the feedback not just as a collection of issues, but treat it as proposing a case to be considered to improve the standing of the organization (in NVDA terms, this means some of the most practical and persuasive GitHub issues and emails are content that address the question, “why should NV Access and the NVDA community care and what benefits can result from implementing the suggested idea”; if folks want, I can revisit an old topic from somewhere discussing what to think about when writing GitHub issues or emails to NV Access).).

Cheers,

Joseph

FARHAN ISHRAK Fahim

unread,
Dec 27, 2025, 2:44:30 PM (13 days ago) 12/27/25
to nvda-...@nvaccess.org

If you make any typin mistake, how can you correct it with nvda without rewriting again? Earlier, we could select option from context menu. However, I am unable to do the same in the new interface with nvda.

Ed Marquette

unread,
Dec 27, 2025, 3:21:43 PM (13 days ago) 12/27/25
to nvda-...@nvaccess.org
This is just a guess, but I think you may be talking about making corrections when you are typing a message in Outlook. NVDA will report the spelling error, but Shift + F10, right click, or the Applications key won't bring up the old context menu. That is enormously frustrating. One would think there is a mole inside Microsoft working for Apple or Google to render new Microsoft products (Windows 11 and Outlook) utter garbage.
Microsoft, however, is unapologetic.
I have made the following work (sometimes):
  1.    Make sure your cursor is on the misspelled word;
  2. Press NVDA + Numpad divide. This routes the mouse to the navigator object.
  3. Press Numpad divide (left click of the mouse).
Something like the old context menu will sometimes appear. You can navigate it as before.


From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> on behalf of FARHAN ISHRAK Fahim <fahim.n...@gmail.com>
Sent: Saturday, December 27, 2025 13:43
To: nvda-...@nvaccess.org <nvda-...@nvaccess.org>

Subject: Re: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back
If you make any typin mistake, how can you correct it with nvda without rewriting again? Earlier, we could select option from context menu. However, I am unable to do the same in the new interface with nvda.
--

***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.

leoba...@gmail.com

unread,
Dec 27, 2025, 3:22:44 PM (13 days ago) 12/27/25
to nvda-...@nvaccess.org

It is still the same, but in this interface once the focus of the screen reader is on the message you want to edit, you find relevant options if arrow right, e.g., context menu.

 

 

Cheers,

Leo Bado

 

“We don't rise to the level of our expectations, we fall to the level of our training.”   Archilochus.

 

From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of FARHAN ISHRAK Fahim
Sent: Saturday, December 27, 2025 1:44 PM
To: nvda-...@nvaccess.org
Subject: Re: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

 

If you make any typin mistake, how can you correct it with nvda without rewriting again? Earlier, we could select option from context menu. However, I am unable to do the same in the new interface with nvda.

--

***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.

Mujtaba Merchant

unread,
Dec 27, 2025, 10:29:26 PM (13 days ago) 12/27/25
to nvda-...@nvaccess.org

Hi Azhar,

 

Yes, the interface is easier to navigate and read messages as long as you stay in the NVDA Focus mode. It seems like staying in that mode is the only way to keep the workflow somewhat efficient.

 

I also found out that pressing Control + 1 will take you back to the chats list in the main window. However, if you want to filter your chats by groups, unread, or all, you actually need to do a Shift + Tab until you reach the filter tabs and hit Enter. Once you've selected your filter, you have to Tab all the way back to the chat message list.

 

It is a lot of extra keystrokes compared to what we are used to, and it definitely takes some getting used to! It's frustrating that simple tasks now require so much more navigation.

Mujtaba Merchant

unread,
Dec 27, 2025, 10:37:25 PM (13 days ago) 12/27/25
to nvda-...@nvaccess.org

Hi Leo,

 

While "accessible" technically means something can be reached, in the digital world, accessibility is inextricably linked to usability. If a task that used to take one keystroke now takes three or four, that isn't just a "minor inconvenience"—it is a functional regression that compounds hundreds of times a day for a power user. For those of us using screen readers, these changes often feel like a well-paved road suddenly being replaced with gravel; you can still travel it, but the friction is significantly higher.

 

You mentioned that the market doesn’t revolve around us, but I would argue that the market is us. According to the World Health Organization, 16% of the world's population—about 1 in 6 people—experience a significant disability. This is not a "small segment"; it represents over 1.3 billion people with an estimated annual spending power of over $13 trillion.

 

Companies like Meta don't just "satisfy a few dudes"; they respond to market data and user feedback. If we "complain to the wind" by staying silent, we effectively disappear from their metrics. By using the formal channels at our disposal, we turn that "wind" into actionable data that helps product teams understand that their "improvements" are actually breaking efficient workflows for millions of users.

 

If we don't speak up, we shouldn't be surprised when the products we rely on daily continue to drift toward being unusable. 16% is too large a voice to keep quiet.

Mujtaba Merchant

unread,
Dec 27, 2025, 10:43:43 PM (13 days ago) 12/27/25
to nvda-...@nvaccess.org

Hi Joseph,

 

I totally agree with your perspective. Having these channels available makes it vital that we report these issues so that at least some awareness gets through to the right teams.

 

I very well remember the last time I tried to advocate on my professional LinkedIn network; I was disappointed by how some members of this mailing list reacted, seemingly not understanding the need for such advocacy. I am doing my best to get my voice across. Everyone is of free will to support or ignore these efforts, but please do not discourage them. No one appreciates such an attitude when we are all striving for a more usable experience.

 

I appreciate your advice on framing this as a business opportunity for Meta. Ensuring they see accessibility as a competitive advantage rather than just a "fix" for a small group is a much more persuasive strategy.

joseph....@gmail.com

unread,
Dec 27, 2025, 11:13:40 PM (13 days ago) 12/27/25
to nvda-...@nvaccess.org

Hi,

Here is something else I would like to suggest: create a collection of app modules for WebView2 apps and package them as an add-on (minimum NVDA version for the add-on should be 2024.3, or I strongly recommend 2025.3.2). These apps should disable browse mode by default (this can be done as little as three lines of Python code) and offer additional hotkeys. But this should be done as a last resort option after advocacy (and activism) efforts are exhausted; give WebView2 app developers a chance to respond, and if they do not respond, then use code to advocate while keeping the conventional advocacy going. And no, I regret to inform the community that I cannot lead the add-on development effort for the foreseeable future.

Cheers,

Joseph

joseph....@gmail.com

unread,
Dec 27, 2025, 11:24:28 PM (13 days ago) 12/27/25
to nvda-...@nvaccess.org

Hi all,

Looks like I’m typing a lot today…

As an interim measure, I would like to suggest that community members revisit resources on NVDA and web usage, specifically resources on browse versus focus mode, quick navigation commands, web apps, and so on. Also, one thing folks should remember: the screen content “shown” in browse mode does not and will not fully correspond to visual content presentation because what browse mode will show is an aggregation of the raw web content, web browser/web view engine, accessibility API’s, NVDA’s browse mode implementation, add-ons and their code, and user settings.

Cheers,

Joseph

Sarah Alawami

unread,
Dec 28, 2025, 12:36:51 PM (12 days ago) 12/28/25
to nvda-...@nvaccess.org

so to get to actions menu imply hit right arrow, a right click is not necessary, at least on the copy I have. I can't right click my message list which is OK. I'd much rather prefer this new layout any time as I hated the older layout, it seemed so clunky.

Sarah Alawami

unread,
Dec 28, 2025, 12:39:20 PM (12 days ago) 12/28/25
to nvda-...@nvaccess.org

try a right arrow  then enter. It is now called actions. from there, you will see its such as mark as read. you will lose focus after invoking the actions and that's OK, shift tab a few times and you will be back in the message list, or use browse mode to  get there if you don't want to use focus.

Sarah Alawami

unread,
Dec 28, 2025, 12:40:48 PM (12 days ago) 12/28/25
to nvda-...@nvaccess.org

I personally don't mind.  It feels much more quicker for me but I'm a tab wizard anyway. Hehahahaha. and once you get used to the layout it is not bad, not perfect, and at the same time not as bad as the prior layout we had to deal with.

Sarah Alawami

unread,
Dec 28, 2025, 1:06:51 PM (12 days ago) 12/28/25
to nvda-...@nvaccess.org

I just write my stuff in word. I remember being able to do that though a few weeks ago, unless that changed, or I got lucky. I think I just down arrowed for the change, cant' remember now.

On 12/27/2025 11:43 AM, FARHAN ISHRAK Fahim wrote:

If you make any typin mistake, how can you correct it with nvda without rewriting again? Earlier, we could select option from context menu. However, I am unable to do the same in the new interface with nvda.
--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.

leoba...@gmail.com

unread,
Dec 28, 2025, 2:02:21 PM (12 days ago) 12/28/25
to nvda-...@nvaccess.org

Yeah, exactly as one would do on any web page, in and out of insertion points, it isn’t inaccessible, interface is kind of a medium for the screen reader, so the medium changed, but it is perfectly navigable. This reminds me of blind folks pissed off because other blind folks can create better songs in Suno than the solo guitar they can play lol  well, WebView2 and AI are here to stay!

 

 

Cheers,

Leo Bado

 

“We don't rise to the level of our expectations, we fall to the level of our training.”   Archilochus.

 

davyc...@gmail.com

unread,
Dec 29, 2025, 1:45:52 PM (11 days ago) 12/29/25
to nvda-...@nvaccess.org

Sarah

 

Contexting with arrow right is a really good finding.

I totally agree with you, yeah right this version is different but only different not inaccessible at all!

Blind people must learn once that things in life are always changing!

Regards to you and already a happy newyear!

Davy

Noelia

unread,
Dec 29, 2025, 10:40:17 PM (11 days ago) 12/29/25
to nvda-...@nvaccess.org
Hi Davy and all:
Firstly, happy new year 2026!
You say:

> Blind people must learn once that things in life are always changing!

I don't think that this applies specifically to blind people. Sometimes we all may have difficulties with some changes, and I think that it's not right nor fair to mention specifically blind people.
Blind people are different persons, and mentioning just a group of people and a particular characteristic may contribute reenforzing negative stereotypes, so please let's avoid it.
Kind regards,
Noelia

Mujtaba Merchant

unread,
Dec 29, 2025, 11:06:02 PM (11 days ago) 12/29/25
to nvda-...@nvaccess.org

Noelia, I completely agree with your sentiments. My only intention in bringing this up was to report a genuine accessibility challenge through the proper support channels.

 

The idea that "getting used to it" is a solution feels dismissive, as it is not a luxury we all have. Transitioning to these new layouts involves a significant amount of time, effort, and—quite frankly—frustration, especially when you are trying to complete tasks as efficiently as you were previously able to. My goal is to ensure that the support team understands that changes making an application more challenging to use should not be ignored or brushed aside.

 

To give you a concrete example of how this affects productivity: just yesterday on my desktop, I prompted Meta AI within the WhatsApp application. When I tried to SHIFT+TAB to copy the response, I couldn't even reach it. I actually had to switch to browse mode just to copy the text. While this might be a workaround for some, it is certainly not a productive or intuitive way of doing things for me.

 

Another member significantly bought up the issue of not being able to select multiple messages in a chat and delete them, this too is another example. I tried helping them by suggesting a work around but I myself was surprised that I could not get the job done. This example has multiple implications in the communication sent and what kind of control we have over it. If the platform was able to support such actions/ features earlier and is now broke; is it not fair for us to report it to the appropriate team through the channels we have at our disposal?

 

We should be advocating for "new" to mean "better," not just "different" at the cost of our efficiency.

 

Having said that, I wish all the members of the mailing list a great year ahead, lets together build towards an accessible experience for all!

Noelia

unread,
Dec 30, 2025, 1:34:43 AM (11 days ago) 12/30/25
to nvda-...@nvaccess.org
Unfortunately, I cannot join my BlindShell phone with WhatsApp easily, so I'm waiting for my trainer to see if she can help me to test this.
But I think that software and all should be as intuitive as possible, of course considering other factors like project maintenance. But making a change which affects performance or doing things in an intuitive way shouldn't be accepted.
Happy 2026 for you and all!

leoba...@gmail.com

unread,
Dec 30, 2025, 5:33:58 AM (10 days ago) 12/30/25
to nvda-...@nvaccess.org

Oh boy, this is the last time I response to this thread,  but dude, come on, explore the interface, both actions on which you make seemingly disparaging remarks, copying a response requested to Meta, and deleting multiple messages from message history  (including non-continuous messages) are both accessible, actionable options, and sufficiently enough usable to that the user between the chair and the keyboard can get acquainted with it to enhance agency and performance, which leads to productivity. I’m running a business here as well, not sitting all day long chatting on discord. I don’t deny the fact that a few actions could be done and enhanced via shortcut keys and addons, but saying it is inaccessible or unusable is making a coffee machine Rub Goldbergian!

 

 

Cheers,

Leo Bado

 

“We don't rise to the level of our expectations, we fall to the level of our training.”   Archilochus.

 

Sergio Gomez

unread,
Dec 30, 2025, 5:43:52 AM (10 days ago) 12/30/25
to nvda-...@nvaccess.org
Hello Noelia and everyone,

First of all, happy new year 2026! I completely agree with you, Noelia. It is unfair to apply the statement that "blind people must learn to adapt to changes" solely to this group. In reality, everyone in life faces changes and has to adapt to them. Limiting this observation only to blind people merely reinforces negative stereotypes. The comment was probably not made with ill intentions, but focusing on just one group did not come across well.

I wish you all an excellent start to the new year and all the best for 2026.

Best regards,

Sergio G. C.


De: nvda-...@nvaccess.org <nvda-...@nvaccess.org> en nombre de Noelia <nrm...@gmail.com>
Enviado: Martes, 30 de Diciembre de 2025 4:40
Para: nvda-...@nvaccess.org <nvda-...@nvaccess.org>
Asunto: Re: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

Gene Asner

unread,
Dec 30, 2025, 7:27:12 AM (10 days ago) 12/30/25
to nvda-...@nvaccess.org
In this discussion, it is important to distinguish between stereotyping,
they all do this, that's how they are, etc. and making statements such
as many blind people and then the statement.  Just saying this or that
is stereotyping and saying let's not do it, is all too easily
interpreted as saying, let's not discuss valid statements that are not
stereotyping, even if that meaning isn't intended by the person making
the statement.


It is a fact that, because there is a good deal of poor training about
and because many blind people are taught to have lower expectations than
they should, that many blind people do fear change when there is no
reason to, such as when moving from Windows 10 to 11, and this sort of
distinction is important to keep in mind.  That is not a stereotype.  It
is discussing a problem that exists and it doesn't say all or use other
such expressions.


Gene


Noelia

unread,
Dec 30, 2025, 9:03:07 AM (10 days ago) 12/30/25
to nvda-...@nvaccess.org
The statement said:

"Blind people must learn once that things in life are always changing!".

I reafirm what I said previously. Also, it's not the same discussing that people can have difficulties, with consequent resistance to change, that the mentioned sentence.
Talking about understandable difficulties can produce constructive discussions to find solutions. Saying that people with a characteristic must do something is about moving the problem just to that people, and I think that this is not good.
Noelia.

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md

You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.

Gene Asner

unread,
Dec 30, 2025, 9:07:04 AM (10 days ago) 12/30/25
to nvda-...@nvaccess.org
I'm not disagreeing with you, but I'm saying that in objecting to such
statements, it is important to point out that they differ from the kind
of statement I've been discussing. The advertising industry is built on
the knowledge that people are apt to misinterpret statements that are
literally true. You can't buy a better toothpaste than x may be
literally true, but a lot of people will interpret it as meaning, x is
the best toothpaste, which isn't what the statement says.

Gene

On 12/30/2025 8:02 AM, Noelia wrote:
> The statement said:
>
> "Blind people must learn once that things in life are always changing!".
>
> I reafirm what I said previously. Also, it's not the same discussing
> that people can have difficulties, with consequent resistance to change,
> that the mentioned sentence.
> Talking about understandable difficulties can produce constructive
> discussions to find solutions. Saying that people with a characteristic
> must do something is about moving the problem just to that people, and I
> think that this is not good.
> Noelia.
>
> El mar, 30 dic 2025 a las 13:27, Gene Asner (<gsa...@gmail.com
> <mailto:gsa...@gmail.com>>) escribió:
> <mailto:nvda-users%2Bman...@nvaccess.org>.
> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to nvda-users+...@nvaccess.org
> <mailto:nvda-users%2Bunsu...@nvaccess.org>.
> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/ba3e15b3-8b7c-4a56-94a2-a0bea60152ab%40gmail.com>.
>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
> NV Access expects that all community members will read and abide by the
> rules set out in this document while participating in this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
> <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org.
> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to nvda-users+...@nvaccess.org
> <mailto:nvda-users+...@nvaccess.org>.
> To view this discussion visit
> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAAtLpyfhPtJv11W36Fc2m_TGfSv%3DeKoRgzRtt8BJs27W2Sue5A%40mail.gmail.com
> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAAtLpyfhPtJv11W36Fc2m_TGfSv%3DeKoRgzRtt8BJs27W2Sue5A%40mail.gmail.com?utm_medium=email&utm_source=footer>.

Mujtaba Merchant

unread,
Dec 30, 2025, 9:44:24 AM (10 days ago) 12/30/25
to nvda-...@nvaccess.org
Hi Members,

I am really disturbed that a simple mail asking the mailing list members to report their challenges and issues with the new WhatsApp update on Windows introducing new accessibility barriers has digressed to such an extent. My simple intention was this: if you find the interface of the application after the update challenging to use, please use the resource I have shared to report it.

I was not asking the members to judge one's ability to use the application or opinionate on what accessibility means, what usability is, and the other off-topics that have been discussed in this thread. If you find the application accessible and you can work with it, I am happy for you. However, please spare the ones who are being challenged with the change. Learning is a curve and not all of us have that kind of luxury.

I am also happy for you, business man, but please do realize that each individual is different and has different priorities and commitments in a day. Sometimes the day is simply not enough.

I feel upset thinking that I am the cause for such discussions, as it was never my intention to instigate this kind of conversation. I hope this mail puts an end to this thread and that members respect each other's thoughts in the same manner I have been respectful of all the criticism I have received from the members of this list.

I wish you all well in your journey and pray that 2026 brings all of us happiness and things we can appreciate. Happy New Year.

-----Original Message-----
From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of Gene Asner
Sent: Tuesday, December 30, 2025 7:37 PM
To: nvda-...@nvaccess.org
Subject: Re: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAAtLpyfhPtJv11W36Fc2m_TGfSv%3DeKoRgzRtt8BJs27W2Sue5A%40mail.gmail.com?utm_medium=email&utm_source=footer>.

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md

You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/4898f136-f9e0-118e-8681-48a993ebb552%40gmail.com.

Sergio Gomez

unread,
Dec 30, 2025, 10:07:05 AM (10 days ago) 12/30/25
to nvda-...@nvaccess.org
Hello everyone,

I'd like to express my agreement with Mujtaba. The initial email aimed to provide guidance on how to report accessibility issues in the new WhatsApp update. Unfortunately, the thread has veered off into a series of unsolicited opinions, some of which have created a tense atmosphere.

It's essential to remember that each of us may find the new interface more or less user-friendly, but that doesn't mean one's experience is representative of everyone's. Opinions suggesting that the interface is "easy" should not be interpreted as insinuations that those who find it challenging are not trying hard enough. We all have the right to express our opinions respectfully, without judging others.

Lastly, I want to wish everyone a happy new year and sincerely hope that this thread can be closed so we can maintain an environment of mutual respect and support.

Best regards,

Sergio G. C.

De: nvda-...@nvaccess.org <nvda-...@nvaccess.org> en nombre de Mujtaba Merchant <mujt...@gmail.com>
Enviado: martes, 30 de diciembre de 2025 15:44
Para: nvda-...@nvaccess.org <nvda-...@nvaccess.org>
Asunto: RE: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back
 

Fawaz abdul rahman

unread,
Dec 30, 2025, 11:16:41 AM (10 days ago) 12/30/25
to nvda-...@nvaccess.org

Hi all,

I didn’t read all the messages in this thread, but I did read the last few. For what it’s worth, I — and quite a few friends of mine — also find the new interface a significant downgrade compared to the previous experience.

This does not mean the new interface is inaccessible; rather, it is simply not efficient enough and cannot be operated as quickly as the previous one.

Even something as basic as navigating the chat list becomes problematic. In focus mode, moving through the list marks chats as read, which means you constantly have to switch between browse mode and focus mode. To type a message, you need focus mode. When you exit it, depending on your settings, focus mode may turn off, so you then have to switch back again to read messages. Playing a voice message? Browse mode. Reading text in order? Focus mode. Taking an action? Focus mode. Downloading a file? Browse mode.

You can see where this is going. Is it usable? Yes. Is it as fast or smooth as the previous interface? Definitely not.

There are also other issues. Many times, it doesn’t even read the name of the person you are chatting with; instead, it just announces a number. Additionally, you can’t jump to the first unread message — you’re forced to read from bottom to top — and there are other problems that become more noticeable the more you use the app.

That said, if you find the new interface useful and enjoyable, I’m genuinely happy for you. You can absolutely enjoy it. I don’t believe this interface is going away anytime soon. In fact, I expect more and more Windows 11 apps to move toward web-based interfaces. This was also pointed out by the developer of Unigram: the old framework is simply no longer being maintained by Microsoft, as far as I know.

However, please don’t discourage others who are trying — or have tried — to report these issues to Meta or elsewhere. The new version has serious problems, not only accessibility and usability issues, but also functional ones.

Happy New Year to you all.

Best,
Fawaz


Noelia

unread,
Dec 30, 2025, 12:04:42 PM (10 days ago) 12/30/25
to nvda-...@nvaccess.org
I agree about provide feedback to WhatsApp accessibility support if required to inform about difficulties and degradation of user experience if needed.
I'll do it if I find a worse experience when I can test WhatsApp.
About my comments regarding blind people, my intention is to provide a smooth environment on this list where all people feels free to provide feedback.
Hope this can be done and we don't need to lock this topic.
Kind regards,
Noelia

davyc...@gmail.com

unread,
Dec 30, 2025, 1:34:24 PM (10 days ago) 12/30/25
to nvda-...@nvaccess.org
Thats the only thing Gene stresses that I wanted to say. And yes I could have stated it on another way but Gene reflects one thing here.

If I advise some blind people to take some education, to follow some training ... I always get the most negative possible reactions.

You are always humiliating other people asking questions you are such a pedantic person Davy, thank you very much and get a life, that’s my answer then!!

I am wanting to help people out here, I want to make people better and we are in mailing groups on different levels here from beginner to advanced but sometimes advance people get tired of those who want to stick to beginners level not because things are maybe not so easy to understand for everyone but because of laziness.

I've got a problem I ask on a list, over and over I do not ask copilot or chatgpt and I am reluctant to read any f..... manuals.
Yes and sometimes maybe I overreact and yes concerning the windows app of whatsapp, is there a regression in accessibility? No really no maybe a little regression in app navigation, and the user interface folks this is really true but I hope tomorrow night we have at least a pleasant new years eve and no stress about our whatsapp client that has to be managed with one ctrl or shft tab more or less.

Make the most out of your lifes, that’s what I do with or without accessibility which can be frustrated sometimes but living in Gaza, Ukraine or in Darfour in Soudan gives far more problems than another way the Whatsapp UI interacts with us.
Best wishes and positive greetings
Davy

-----Oorspronkelijk bericht-----
Van: nvda-...@nvaccess.org <nvda-...@nvaccess.org> Namens Gene Asner
Verzonden: dinsdag 30 december 2025 13:27
Aan: nvda-...@nvaccess.org
Onderwerp: Re: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

In this discussion, it is important to distinguish between stereotyping, they all do this, that's how they are, etc. and making statements such as many blind people and then the statement. Just saying this or that is stereotyping and saying let's not do it, is all too easily interpreted as saying, let's not discuss valid statements that are not stereotyping, even if that meaning isn't intended by the person making the statement.


It is a fact that, because there is a good deal of poor training about and because many blind people are taught to have lower expectations than they should, that many blind people do fear change when there is no reason to, such as when moving from Windows 10 to 11, and this sort of distinction is important to keep in mind. That is not a stereotype. It is discussing a problem that exists and it doesn't say all or use other such expressions.


Gene


--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md

You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/ba3e15b3-8b7c-4a56-94a2-a0bea60152ab%40gmail.com.

Hettie

unread,
Dec 30, 2025, 1:39:12 PM (10 days ago) 12/30/25
to nvda-...@nvaccess.org, Noelia

Hi Noelia

I totally agree with you. This is a List where we are supposed to help one another as far as possible. We are different persons, different ages with different abilities. If you feel it is necessary to say something nasty, get up from where you are and go and have a cup of tea, coffee or something stronger. When you come back your frustration level should be lower and you may even have some consideration for people who need some coaching when apps change. This was a major change to Whatsapp and not all of us can make the necessary changes over night.


I wish you all a prosperous and healthy 2026.


Hettie

azhar...@gmail.com

unread,
Dec 30, 2025, 2:01:10 PM (10 days ago) 12/30/25
to nvda-...@nvaccess.org

After reading all the messages in this thread, I am now afraid to ask even a simple question on this forum. I am still having many challenges with this new version but I will go some where else to get help.

 

Happy new year to all of you.

Fawaz abdul rahman

unread,
Dec 30, 2025, 2:19:20 PM (10 days ago) 12/30/25
to nvda-...@nvaccess.org
Hi Davy,
I want to respond to a few points you raised, because I think several different issues are being mixed together.
First, I strongly disagree with framing criticism of the new interface as a sign of laziness or an unwillingness to learn. Many of us raising concerns are not beginners trying to avoid learning new tools. We are experienced users who already adapted to the previous workflow and are now pointing out that the new one is slower, more fragmented, and less efficient. That distinction matters. A regression in efficiency for advanced users is not a moral failure, nor a refusal to improve.
Second, comparisons to situations like Gaza, Ukraine, or Darfur don’t really belong in this discussion. No one here is claiming that UI regressions are comparable to humanitarian crises. Bringing such comparisons into an accessibility discussion shuts down legitimate feedback rather than engaging with it. Accessibility and usability issues are worth discussing on their own terms, without ranking suffering.
Third, I don’t think it’s accurate to downplay what’s happening by saying there is “no real regression.” Constant mode switching, loss of jump-to-unread, forced read states, and slower navigation are not minor inconveniences for screen reader users who rely on speed and predictability. Usable does not mean efficient, and efficiency is a core part of accessibility for blind users.
Fourth, while I believe you genuinely want to help, the tone can sometimes come across as dismissive of other people’s lived experience. When users report problems and are told, implicitly or explicitly, that they should simply adapt or stop complaining, it discourages constructive reporting and pushes people away from the community. That effect is visible in this very thread.
This leads me to Azhar’s message. Azhar, if you are reading this: please don’t feel that way. It’s true that some responses can sound patronizing, and that is something we as a community should reflect on. But please know that there are many people here who genuinely want to help, who remember what it’s like to struggle, and who are happy to answer questions.
Finally, to be fair, I do agree with one broader point you made: in every community, there are people who repeatedly ask questions without trying available resources, and that can be frustrating. But that is a general human issue, not something specific to blind users, beginners, or any particular group. It shouldn’t be used to dismiss well-founded criticism or silence people who are engaging in good faith.
I hope we can keep this space one where both beginners and advanced users feel welcome to speak, ask, and disagree, without being reduced to stereotypes on either side.
Best regards,
Fawaz

davyc...@gmail.com

unread,
Dec 30, 2025, 2:39:30 PM (10 days ago) 12/30/25
to nvda-...@nvaccess.org

Karim slm

 

Why don’t you ask, shoot! There are no stupid questions only stupid answers.

Davy

azhar...@gmail.com

unread,
Dec 30, 2025, 2:48:33 PM (10 days ago) 12/30/25
to nvda-...@nvaccess.org

Yes Devy, after reading all the discussion, I am convinced that answers can be more stupid than questions.

davyc...@gmail.com

unread,
Dec 30, 2025, 3:07:24 PM (10 days ago) 12/30/25
to nvda-...@nvaccess.org

If you have questions just ask them!

 

Many people are struggling how to leave a conversation you can simply do that pressing ctrl tab.

Navigating a conversation can be difficult what I am always doing is, opening the chat, hitting ctrl end and arrow up a few times to see the last messages.

But for most of the time I am an iphone whatsapp user but if I want to type longer texts and use no audio, I prefer the windows environment.

Noelia

unread,
Dec 30, 2025, 4:53:32 PM (10 days ago) 12/30/25
to nvda-...@nvaccess.org
Hi Davy, please stop using this tone and mentioning specific groups of people here.
Remember that this list has a code of conduct, and according to that document:

A primary goal of NV Access and NVDA is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, nationality, socioeconomic status, education, level of experience and religion (or lack thereof).


I'm locking this topic, but please, feel free to encourage people to report issues about third party  applications like WhatsApp when appropriate.
Kind regards and sorry for those who have feel bad for this tone.


Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages