bring to nvda new features for use in whatsapp

[fernando-jose-silva]

Is your feature request related to a problem? Please describe.

no

Describe the solution you'd like

I would like to suggest bringing two features to nvda, for interaction in whatsapp. Currently for the desktop app, downloaded from the microsoft store. But if possible, it can be on the other platforms on which whatsapp runs. the suggestions are: 1: nvda will announce when a new message is being typed. 2: nvda announces the text or file name when it is received, this being inside whatsapp. I know that there are addons for whatsapp, but I would like these features within nvda, this makes life easier for beginner users. In Brazil the use of nvda is gigantic. For those who are more aware, some of the ideas in this call are inspired by other screen readers.

Describe alternatives you've considered

Additional context

[codeofdusk]

The responsibility for implementing this feature ultimately falls on Meta, as this should be implemented via UIA notification events from the client. There's no other way to do this without resorting to hacks.

@seanbudd I recommend closing as requires external fix.

[XLTechie]

Didn't Jaws just announce more support for Whatsapp in their latest version? Are these features among those they are now supporting? I do believe the typing alerts one is.

I'm not saying that, or the popularity of Whatsapp, is enough for us to support it more than we do now. But PR should probably be a consideration at some level, in these kind of decisions between working around bad accessibility vs. insisting that it's the app vendor's problem and NVDA users should just complain to them.

https://groups.io/g/tech-vi/topic/february_updates_for_jaws_and/96999123?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,96999123,previd%3D1676592429931137367,nextid%3D1676380538248304462&previd=1676592429931137367&nextid=1676380538248304462

[fernando-jose-silva]

I am suspect to defend my own claim. I don't agree that we should simply close this request, I don't agree with the attitude of simply throwing to others a correction that we can make. I agree that the goal is who should solve this problem, however I don't think that the role of screen reader developers is just to point out responsibilities, we have to give resources to our users as soon as possible, and our screen reader manufacturer peers are doing this. I think the role of screen reader manufacturers this includes nv access is to ask the company to provide this feature, in this case the role of nv access is to get in touch with the meta and suggest these upgrades. In this case, as I know how to do this, I will do it myself. However, we have to change this attitude, not all users will know how to suggest changes to software manufacturers, and it must be nv access's role to do this, I know that we don't have enough people to keep demanding this from manufacturers, but just one call should not be so expensive, and thinking in the long run, it can even encourage partnerships with nv access, who knows even with financial donations or a service contract as a benefit to nv access. How much do we expect a change from software manufacturers, because we ourselves as a major screen reader developer cannot present our users with improvements. I live in close proximity to novice users, and I assure you, what matters at the end of the day is that the feature works, no matter how it was achieved. Comparing software features is what users do all the time. Therefore, my suggestion would not be to abandon this request, if you believe little in the proposal, classify it as low priority, and offer these changes to other developers who may want to work on it. I feel that simply closing the issue is disrespectful to the requester, and I don't just say this for myself, I also feel this for other troublemakers who open tickets and have their requests canceled so soon without further discussion. The work of those who reserve the time of their lives to open questions must be valued, logically from the developers as well. Thanks for listening.

[OzancanKaratas]

@fernando-jose-silva Have you contacted the WhatsApp team for your requests? These operations can be performed without an add-on or app module as they are handled by UI Automation. So WhatsApp can also fix this problem directly.

[fernando-jose-silva]

This has been going on for so long, but as far as I remember, I even tried to pay off the electricity, but to no avail. Anyway, I believe that no one will follow up with this question. Thanks.

[Adriani90]

To give my 50 cents on this, I agree with @fernando-jose-silva in general, that is, we need really more serious cooperations between screen reader developers and mainstream app developers. This is the only way to increase accessibility in a sustainable way. otherwise the responsibility is always given to the user who does not really have any leverage other than filling a complaint or issue. In the end, we are a small group of users compared to non disabled users, so I don't believe there will be a strong change in mindset of mainstream developers just because a small group of users is complaining. But when developers of both perspectives work together, this definitely will influence mindset on the long term. It sounds hard but this is the reality that i face alot. Building strong cooperations on a b2b level will have much more weight. Of course it also means investing more ressources, but this cooperation building argument could be used to generate more sponsoring, donations and other funding for screen reader developers and for NV Access. Users filling issues and complaints have of course a short term effect as well and should ideally be a common practice among users. But to be realistic, this will not change things significantly in the long term.