4 ms·
I think Google might mean that the community wasn't actually taking advantage of the feature to provide very many subtitles (i.e. low supply); not that there we
by derefr 6y ago
I think Google might mean that the community wasn't actually taking advantage of the feature to provide very many subtitles (i.e. low supply); not that there weren't many people using such subtitles when available.
It's not quite like removing a ramp. It's more like a city had a program of "we'll help pave and maintain the sidewalk in front of your business to be more accessible, and to add ramps to connect to your door, by request"; but then no businesses took them up on that offer by requesting ramp installation—so they stopped offering the program.
- idnefju 6y agoStill follows the same logic, why should it be removed for the minority if the majority abuses it?
- sangnoir 6y agoBecause the code still has to be actively maintained perpetually - internal APIs change over time, security risks have to be mitigated, some one (or some teams) have to have responsibility over this feature - and Google has decided it's not moving the needle enough to be worth it.
- paulryanrogers 6y agoADA doesn't care about their ROI on features
- sangnoir 6y agoYou are right, but ADA doesn't apply in this specific case.
- paulryanrogers 6y agoWhile technically true in this age of social distancing and increasingly online everything it probably should. Youtube is essentially a Monopsony for monetized Internet video. So this will make many previously accessible channels inaccessible to the deaf and hard of hearing.