The truth is that the OS usually hides the latency of wireless heapdhones, e.g. airpods, by delaying video to keep it in sync. The real latency is somewhere around 100-400ms if the RF environment is crowded. Even worse is that the latency isn't actually constant, but drifts all the time.
At many IT conferences organized by hackspaces, everything is done by volunteers, including broadcast and video/audio postproduction. And that is actually one of the most common issues: our volunteers use wireless headphones even if we ask them repeatedly not to.
We cut talks in postproduction primarily based on audio, e.g., when does the applause start/end, when does the speaker's introduction start/end, etc. Obviously, that doesn't work reliably if the audio latency is nondeterministic.
Even worse, as different venues have different audio setups, there are sometimes real audio/video sync issues that need to be fixed. But if our volunteers are using wireless headphones, they won't just set the wrong offset, but they end up trying to fix issues that don't even exist.
And then you get complaints from viewers that e.g. the livestream audio/video is out of sync, even though it's not. The issue turns out to be caused by the viewer's laptop and wireless headphones not supporting the latency compensation technique I explained earlier. And there's nothing we can do about that.
Wireless headphones tried to fix something that wasn't broken, and made it worse. In German, we'd call that "verschlimmbessern".