The engines behind Alexa and Google Assistant have decent enough accuracy, I'm not sure why there couldn't be a product to run the audio through those to get subtitles.
When there's not a single audio source for the main speaker, that becomes a problem, but that's the fault of the people recording it for not getting a clean audio source. However, in practice, this is rarely going to be the case for something like a product video because the studio will have recorded it correctly in isolated sound rooms.
We're automatically reverting to "a human should do it" with adding aria tags, video subtitles, and screen readers. That is the problem because developers often have many other things to worry about -- database, security, scalability, maintenance, documentation. Accessibility gets put right beside those and it's no wonder developers don't prioritize it.
It doesn't work well enough. We're no where NEAR it working well enough. People invent new words (product names, technologies), the text isn't synced to the video, there is background noise, the speech-to-text engine doesn't have the context of the video to guess which homophone is correct.
Technology is not the magic bullet to fix everything. We're no where near that place.
In the mean time, I still can't use your site. And neither can people with any number of other issues (medical, environmental, simple bandwidth, etc).
Don't pawn it off on tech, people need to take responsibility for this kind of stuff.
When there's not a single audio source for the main speaker, that becomes a problem, but that's the fault of the people recording it for not getting a clean audio source. However, in practice, this is rarely going to be the case for something like a product video because the studio will have recorded it correctly in isolated sound rooms.
We're automatically reverting to "a human should do it" with adding aria tags, video subtitles, and screen readers. That is the problem because developers often have many other things to worry about -- database, security, scalability, maintenance, documentation. Accessibility gets put right beside those and it's no wonder developers don't prioritize it.