The blog post should do a better job of explaining the real issue. It seems like the REAL issue is that Chrome's implementation of this feature is lackluster b

The blog post should do a better job of explaining the real issue. It seems like the REAL issue is that Chrome's implementation of this feature is lackluster because when the audio fails to play it does so with no notification to the user. A better implementation would be if when the website first tried to play audio sans interaction, a permission request was made like the ones that show up for websites that want to do desktop notifications, etc. That way the failure isn't silent and the user has some control over the option to allow or deny the permission on a site-by-site basis. Having said that, I find that websites auto-playing audio is such a nuisance these days that I'd personally selfishly allow every project/business that relies on the ability to just die and not really shed a tear if there was some reason the Chrome team couldn't come up with a better implementation.