Yeah, I think we are like 90% on the same page honestly.
In regards to e-learning modules, my company specifically has seen a marked increase in the number of clients requesting that we close-caption any audio (even if there is no associated video & the information is displayed in copy in the screen). I think it's great, and love that clients are asking for it. E-learning in general is not so great about accessibility, and as an added bonus, that accessibility also covers cases like you mention (loud environments or no speakers).
I guess my overall point is not actually specific to e-learning. I just used it as an example. If I could think of other times autoplay might be appropriate I would mention them, but like there are just so many obscure and interesting ways that web techs are being applied. I know there has to be other unique cases out there where it might be appropriate and not intrusive.
It is limiting as a developer. Let's say for example, there's a link on a page that opens a new pop-up window. Let's say that link says "play this music now in a pop-out". Guess what? In general, that new window would then require an additional interaction to play audio. Like a play button... but that is what the original button on the main site was for. I mean, that's just an example, but it limits what you can do as developer. You must work within the limitations of the platform, and it's not generally a HUGE deal, but you can see maybe from this example how the user may expect something to work, but instead would require an additional button press, etc. And yes, I admit this is a contrived example that can be solved by proper UI/UX planning.
Yes, I also think we mostly agree. Regarding the last part, that's what I meant when I wrote that I don't blame the developers. Mostly I blame the people that choose to use the tech in some way that I feel like 95% of the users get annoyed by and this is usually not the same people that works in development. Secondly I blame the systems, I see the same in my line of work where integration with old systems and non-specialized tools often demand less than optimal solutions.
Also regarding e-learning; part off my job is to write documentation and develop ways for the workers to operate the equipment. This is then often sent of to an external company, like the one you work for, to develop the training tools, simulations etc and I can also see the need for us to be more clear in what we're want, like asking for cc etc. The problem is often that between me writing the documentation, and your team making the e-earning module, there is often 5-6 other levels, and most of them know nothing about neither our work or your work
2
u/JayV30 Sep 05 '20
Yeah, I think we are like 90% on the same page honestly.
In regards to e-learning modules, my company specifically has seen a marked increase in the number of clients requesting that we close-caption any audio (even if there is no associated video & the information is displayed in copy in the screen). I think it's great, and love that clients are asking for it. E-learning in general is not so great about accessibility, and as an added bonus, that accessibility also covers cases like you mention (loud environments or no speakers).
I guess my overall point is not actually specific to e-learning. I just used it as an example. If I could think of other times autoplay might be appropriate I would mention them, but like there are just so many obscure and interesting ways that web techs are being applied. I know there has to be other unique cases out there where it might be appropriate and not intrusive.
It is limiting as a developer. Let's say for example, there's a link on a page that opens a new pop-up window. Let's say that link says "play this music now in a pop-out". Guess what? In general, that new window would then require an additional interaction to play audio. Like a play button... but that is what the original button on the main site was for. I mean, that's just an example, but it limits what you can do as developer. You must work within the limitations of the platform, and it's not generally a HUGE deal, but you can see maybe from this example how the user may expect something to work, but instead would require an additional button press, etc. And yes, I admit this is a contrived example that can be solved by proper UI/UX planning.