I'd disagree that it is misleading. I'm betting browsers (or at least FF) make it deliberately hard to tell if the browser is in a "has WebRTC capability but i

I'd disagree that it is misleading. I'm betting browsers (or at least FF) make it deliberately hard to tell if the browser is in a "has WebRTC capability but it's disabled" state (to avoid fingerprinting), so I don't really place the blame on the author. Disabling WebRTC is something that was deliberately done, so that's on you to remember that you turned it off. Sure, the message could be more helpful and say "this website requires WebRTC to function", but a browser with WebRTC turned off is in fact not supported by this service.