Is that really Discord’s fault though? I’m not familiar with other chat apps, so maybe Discord is not doing something to prevent such accidents from happening.
Clicking on a channel name normally shows you the content of that channel. But clicking on some channel names automatically start an audio connection, and if you're on several Discord servers with many dozens of channels each, it's easy to miss which are which. Once the audio connection is started, assuming you realize what happened, the method for dropping the connection is a single unintuitive (for me, and apparently others) icon. If you instead switch away from the channel, thinking that just as the text for a channel disappears when you switch away from it, perhaps so does the audio, then you'll remain connected.
If you're focused on what you're doing, it's relatively easy to see what's happening and undo it. The icon is a monochromatic old-school phone handset with a tiny X in the corner, and recent versions of the Discord desktop client now include a reasonably large message on the lower-left telling you that you're part of an audio call. But if you're treating Discord like another chat app, then it is easy to accidentally end up broadcasting audio without realizing it, and I think Discord's design is to blame.
My comment about Discord’s inculpability was quite unfair anyway because even though I use Discord, I’ve never used the voice channel. It’s foolish of me to make that comment.
On another note, I wonder how many times those kinds of accidents had happened? And if it’s relatively high, is Discord aware of them?