RE: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

15 views

Skip to first unread message

Steve Nutt

unread,

Jan 5, 2026, 9:32:04 AM (4 days ago) Jan 5

to nvda-...@nvaccess.org

Also Joseph, some blind people want software to be like an old pair of slippers, never changing.

That won’t happen I’m afraid.

All the best

Steve

Computer Room Services

77 Exeter Close, Stevenage, Hertfordshire, SG1 4PW

T: +44(0)1438-742286, M: +44(0)7956-334938

E: st...@comproom.co.uk, W: https://www.comproom.co.uk

From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of joseph....@gmail.com
Sent: 27 December 2025 19:07
To: nvda-...@nvaccess.org
Subject: RE: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

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

From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of leoba...@gmail.com
Sent: Saturday, December 27, 2025 11:24 AM
To: nvda-...@nvaccess.org
Subject: RE: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

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.

From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of Mujtaba Merchant
Sent: Saturday, December 27, 2025 9:50 AM
To: nvda-...@nvaccess.org
Subject: RE: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

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

From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of azhar...@gmail.com
Sent: Saturday, December 27, 2025 9:14 PM
To: nvda-...@nvaccess.org
Subject: RE: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

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

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

Azhar

From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of Hettie
Sent: December 27, 2025 9:07 AM
To: nvda-...@nvaccess.org; Mujtaba Merchant <mujt...@gmail.com>
Subject: Re: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

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

On 12/27/2025 8:34 AM, Mujtaba Merchant wrote:

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.

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

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.
On 12/26/2025 2:26 PM, azhar...@gmail.com wrote:
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.
On 12/25/2025 10:46 PM, Mujtaba Merchant wrote:
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

--
***
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.
--
***
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/f0c05c98-034c-48fd-875b-f49c404aba3c%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

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/030501dc76b6%24a9027bf0%24fb0773d0%24%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

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/bfca14e9-5470-4989-a615-7d1b443e55bc%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

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/009d01dc76fa%24cdc62a10%2469527e30%24%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

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/89fb6b41-50b9-4031-8754-194c84016453%40gmail.com.

Steve Nutt

unread,

Jan 5, 2026, 9:34:53 AM (4 days ago) Jan 5

to nvda-...@nvaccess.org

Hi,

Here are the WhatsApp for Windows shortcut keys:-

https://faq.whatsapp.com/6204576529560565/?cms_platform=web

All the best

Steve

Computer Room Services

77 Exeter Close, Stevenage, Hertfordshire, SG1 4PW

T: +44(0)1438-742286, M: +44(0)7956-334938

E: st...@comproom.co.uk, W: https://www.comproom.co.uk

From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of Mujtaba Merchant
Sent: 28 December 2025 03:37
To: nvda-...@nvaccess.org
Subject: RE: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

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.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/004201dc77ab%2445846610%24d08d3230%24%40gmail.com.

Steve Nutt

unread,

Jan 5, 2026, 9:41:13 AM (4 days ago) Jan 5

to nvda-...@nvaccess.org

As I say, it’s the old slippers syndrome, and you’re right, it’s not just blind people.

All the best

Steve

Computer Room Services

77 Exeter Close, Stevenage, Hertfordshire, SG1 4PW

T: +44(0)1438-742286, M: +44(0)7956-334938

E: st...@comproom.co.uk, W: https://www.comproom.co.uk

From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of Mujtaba Merchant
Sent: 30 December 2025 04:06
To: nvda-...@nvaccess.org
Subject: RE: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

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!

From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of Noelia
Sent: Tuesday, December 30, 2025 9:10 AM
To: nvda-...@nvaccess.org
Subject: Re: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

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

El lun, 29 dic 2025 a las 19:45, <davyc...@gmail.com> escribió:

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

Van: nvda-...@nvaccess.org <nvda-...@nvaccess.org> Namens Sarah Alawami
Verzonden: zondag 28 december 2025 18:41
Aan: nvda-...@nvaccess.org
Onderwerp: Re: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

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.
On 12/27/2025 7:29 PM, Mujtaba Merchant wrote:
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.

From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of azhar...@gmail.com
Sent: Saturday, December 27, 2025 10:12 PM
To: nvda-...@nvaccess.org
Subject: RE: [NVDA] Urgent: Accessibility regression in new WhatsApp Desktop & How to fight back

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

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/03a301dc774f%24c0a31ff0%2441e95fd0%24%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

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/003601dc77aa%24278a8f50%24769fadf0%24%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

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/e4c2e7cd-bb70-4223-8427-b178c341297f%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

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/066301dc78f3%24582e2f00%24088a8d00%24%40gmail.com.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAAtLpyeSDJ1vWx7jw-JncuoRCfGLU18r6Tx%2BvXR%3DVBY96pEYpQ%40mail.gmail.com.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/001b01dc7941%249985cc30%24cc916490%24%40gmail.com.

Mujtaba Merchant

unread,

Jan 5, 2026, 9:58:31 AM (4 days ago) Jan 5

to nvda-...@nvaccess.org

Dear Steve,

Thank you for sharing the WhatsApp for Windows keyboard shortcut list. I have reviewed them, but I’ve encountered some significant usability issues on the desktop application that I wanted to highlight.

Firstly, I find it very strange that when navigating the message list, NVDA does not report whether a chat message is unread. This is a major functional gap for screen reader users, as we lose the primary indicator of new activity without this verbal feedback.

Secondly, I have to comment on the shortcut to start a new chat: Ctrl + Alt + N. I think it is absolutely "brilliant"—it must have taken a genius to choose the exact same shortcut used to start or exit NVDA itself. It’s an incredible oversight to have a core application shortcut conflict directly with the primary command for the screen reader required to use it.

And please, don't suggest that I simply change the NVDA shortcut to fix this. It’s the principle of the design; it makes me wonder if anyone at the development team actually tried using these shortcuts with a screen reader active.

I appreciate you providing the link, but these regressions in the desktop app's "WebView2" wrapper are making the experience increasingly difficult.

Mujtaba Merchant

unread,

Jan 5, 2026, 10:12:52 AM (4 days ago) Jan 5

to nvda-...@nvaccess.org

Hi Steve,

I think you’ve misunderstood the analogy. This isn't about blind people wanting software to be like an "old pair of slippers." It’s about not wanting our slippers to be replaced with a pair of concrete boots and being told it’s an "upgrade."

Efficiency and usability aren't "comfort" features we can grow out of; they are requirements. When a functional workflow is replaced by a convoluted one, it isn't "evolution," it’s a design failure. Suggesting that we should just accept a degraded experience because "things change" ignores the fact that change is only progress when it actually works better.

I’m all for new slippers, Steve—as long as they don't trip me up every time I try to take a step.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/020501dc7e50%2411401c90%2433c055b0%24%40comproom.co.uk.

davyc...@gmail.com

unread,

Jan 5, 2026, 11:07:13 AM (4 days ago) Jan 5

to nvda-...@nvaccess.org

I had hoped to use an older version to get back to the old normal.

I have always blamed Apple as being a jail I mean, you cannot get back to older versions whenever you update an app.

Sure you can but then you should jailbreak or go back to a previous version via Itunes which for most people is a huge difficulty.

I’ve always argued that maybe for windows or Android this is much easier to fulfil you simply connect the device to your phone and install an older version of an app with no accessibility regressions.

However, even with windows and whatsapp this is nolonger possible.

I have tried this but immediately after installing you are prompted to use the latest update and you cannot cancel this button.

This is a new policy which for one reason I can understand from software developers and that is security.

If major updates are released you have to update or stop using the program.

As we all know this can have negative influence for us as accessibility users.

The only thing to fight back is report, report and report again and again!

But I must admit: sure there are regressions but the usability of Whatsapp Web App is still there.

Davy

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/002601dc7e54%24cdb2c4f0%2469184ed0%24%40gmail.com.

Reply all

Reply to author

Forward

0 new messages