[chrismorgan]

Given the purpose “to help people listen to podcasts”, I’m a bit puzzled about which end you’re tackling it from. Does it not make more sense to work on the user’s side, on browser software, where you can make all sites work, rather than helping the odd site here or there to support this? When approached from the website side, I don’t expect many to adopt it.

(On the browser side, I am aware that various browsers have speech controls hooked up, most commonly inside a Reader Mode—to say nothing of screen readers, which have a different target market. There’s also the Web Speech API which could be used to replicate WebsiteVoice’s functionality using whatever voices are offered by the user’s device. Its quality will be heavily platform-dependent.)