[Athen] Vimeo Livestream accessibility

[David Engebretson]

Suggestion would be to contact their support team.  I told them their player wasn't accessible several months back and they agreed and said they are working on making it accessible.

We probably need numbers... sometimes it takes more than one or two people to change the culture at these types of companies.  Let them know what you are experiencing and then hope they find the resources, within their company, required to make the changes to make their products accessible.  Looks like 2014 was the last time they publicized their efforts regarding making their player accessible.

Philosophical question:  Why do we, as higher education technology professionals, even bring an inaccessible player on to our web platforms?  I suspect it is because we don't know they are inaccessible if we don't test them against WCAG and assistive technology.  Plus, it is difficult, tedious, and frustrating work to try and change the awareness of developers.  Also, it is difficult, tedious, and frustrating to try and change the awareness of any human.

It seems to me that the need for a11y awareness is still lagging.  Ever improving but still lagging.  What do we need to do to make a11y viral in the social media space?

Best,

David

David Engebretson Jr | Digital Technologies Accessibility Coordinator
Department of Web Communication Technologies
360.650.7755 | David.Engebretson2 at wwu.edu<mailto:David.Engebretson2 at wwu.edu>
University Relations & Marketing
How did I do? Please leave feedback.<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwwu.az1.qualtrics.com%2Fjfe%2Fform%2FSV_br2NhzupyEtQTTT%3FQ_SDID%3DSD_87CoVYO6SFgylVz&data=02%7C01%7C%7Cd92aba0714164eaf5b7508d5ba9e8025%7Cdc46140ce26f43efb0ae00f257f478ff%7C0%7C0%7C636620112260636719&sdata=A6AGsWpuIkxuytEqrqG%2Bk6lcfZEwY7WovQCIlBzcvOo%3D&reserved=0>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20181019/64432f01/attachment.html>