I am deaf. i already struggle with keeping up with subtitles on tutorial videos of some obscure stuff that has little to no docs. Kindly return this idea to a void function instead and try not to catch the erroneous thread with these satanic proposals.
In reality, an editor could have speech-to-text and it would transcribe the spoken comment into a comment with some tag to indicate it was a spoken comment. Then when an editor encounters such a comment, it would read it out using text-to-speech. For example
// transcript: Holy fuck what is wrong with this stupid code‽ for fucks sake! *inaudible* I've spent hours on this. I'm going to... nevermind it was a semicolon. Undo comment. Remove comment. Cancel comment.
While investigating an uncovered node in some aviation datalink software, I discovered a 15 year old comment from 1993 along the lines of, "this function never runs, I'll fix it later." I wish will all my heart I could have heard their voice. Even if just for a moment.
I actually like this, at least in some way it could lower the barrier for actually explaining what a function does. Though I don't see this working in an office environment
Only if your fifteen minute comment recorded during the morning commute is transcribed by the most limited speech to text system possible and put as alt text.