Edit: As of build 2.25.20.83, this issue has been solved. The Voice Message button now behaves as expected.

PSA: If you use VoiceOver to send voice messages on iOS with WhatsApp build 2.25.20.75 and tend to lock the button, you will find it difficult to send the message. The send button disappears from VoiceOver's consciousness and the only way to have it reappear is to use screen recognition.
If you simply double-tap and hold, speak and then send to release, you will be fine.
I recommend either not updating at this time if you haven't already, or if you have, double-tap and hold for the foreseeable.
Be advised that shutting down WhatsApp completely and reopening the conversation will hide the text box as well as the send button from VoiceOver until screen-recognition is used, so even this is not an easy work-around.
Feel free to pass this on as necessary.
#WhatsApp #VoiceOver #iOS

This entry was edited (1 month ago)

reshared this

in reply to Andrew Hodgson

@andrew @cachondo @pitermach I actually have a harder time listening to speech on something that isnt' headphones. Especially if it's speaking rather quickly. I can do it, but it's not something i"M practiced at anymore. A phone speaker in the right environment is fine, but listening to a computer's speech on big monitors is just not something I can do. Not that I'm knocking anyone for doing it, but I just cannot, it honestly feels rather rude to just be using your computer or phone, at a volume that everyone in the room can hear. Sure you can choose not to listen, but when you hear

Message from... mom!
At loud volume, at a speed that anyone can understand at a volume the people in the next room can hear... you can't not hear it lol.

in reply to Xantastic

@cordova5029 @andrew @pitermach I can't do over 750 words per minute unless it's in my ear, I have to drop down to about 620 for speakers.
But yeah, I got used to using it in-ear because I was always around other people. Even if I'm alone I don't have my speech out loud now, although I might have system sounds on the speakers.
It probably started because the hardware speech synthesizers were separate physical devices to the headphone jacks on my computers.
in reply to Sean Randall

@cachondo @cordova5029 @andrew @pitermach Speech on monitors just doesn't work for me. I can do say, MacBook speakers and iPhone (if I must) but prefer headphones. I feel like it's equivalent to blaring an audio book at conversational volume, wherever you happen to be and I just don't enjoy that. I don't want to hear anyone's music or speech in a public place, so why would I ever throw mine out there?
in reply to Sean Randall

25 years ago, when my hearing was much better, and I lived in a basement, I used hardware synthesizers on small, but still quite full sounding speakers, which were separated from my much larger, better speakers for general audio stuff. Specifically, I used a Doubletalk PC and this nice little wooden cube speaker with no amplification, which still managed to get quite loud. Saying that now, I probably would struggle to deal with it.

I continued to primarily use hardware speech synthesizers up until about 2008 or so, being a bit of a hold-out. Though I primarily use Eloquence now, not because I love it, particularly, but because it's the easiest thing for me to understand, I didn't really use it for anything other than installing stuff on someone else's machine, or on my Symbian S60 phone until about ten years ago. Though I had access to it from early 1999 in the IBM ViaVoice days, as that came with IBM Homepage Reader, I actively avoided it where I could, mostly because I hated how it sounds on speakers, all boomy and stuff. With IBM Homepage Reader, that wasn't an option, and it had far better web support than any of the dedicated screen readers did at the time. This wouldn't last long, though, so it became a moot point in relatively short order.

On iOS, there is a per-voice EQ, so I turned the two lowest bands way down for Eloquence, specifically. I'd love to do that for Windows and Mac OS as well.
Now, on the very rare occasions I hear it on a reasonable speaker, it's not as annoying.

These days, I have a hard enough time using speech on headphones, and absolutely can't do speakers at all for basically anything long term. The sound is either too indirect (defused and smeared from standing waves, reverb or whatever) or, if it is loud enough for me to understand, it's annoying for everyone else. Even if I'm completely alone, a thing which rarely happens, and I have the ability to crank stuff up as much as I want, I still generally don't.

Over the years, I've slowed my speech down as well. Gone are the days when I can deal with 700+ WPM other than to sometimes get a general idea of things.

I'm transitioning to using braille more often. At this point, I'm probably using it about 75% of the time, but my hearing isn't so bad that I can't use speech at all, so I still often read long passages that way, but some days, I just can't do it.

@cordova5029 @andrew @FreakyFwoof @pitermach

This entry was edited (1 month ago)
in reply to Keri Svendsen

@sapphireangel @andrew @pitermach I was sat in First Class on the way home yesterday and at least 4 people within my hearing range had videos out loud on their phones, tablets or laptops.
It wasn't a quiet carriage, but the respect for your fellow passengers seems nonexistent these days.

There was also a very cute American toddler on the way to Oxford who wanted to watch Elmo. dad hadn't contended with Great Western's wifi, of course, so poor Elmo didn't happen. But the kid was sweet. I got a kick out of hearing them teaching the child to say Hanborough.