DEV Community

Discussion on: March 3rd, 2022: What did you learn this week?

Collapse
 
grahamthedev profile image
GrahamTheDev

Twitter does not give you a way to protect people who have photosensitivity conditions (such as epilepsy).

I made a video with a load of flashing images, added the "sensitive" flag (which sadly destroyed my engagement) as per the great advice from @savvasstephnds and found out the video still plays and you can still see the flashes through the overlay, so that was pointless! 🤦‍♂️

I then found our that if your captions file (SRT file) has a start time that is before the previous captions end time you get a super helpful "your media could not be uploaded" message instead of something meaningful.

I think, in essence, I learned that I am rubbish at Video on social media, Twitter's accessibility is pretty meh for video, and I should leave video to the pros! 🤣

Collapse
 
savvasstephnds profile image
Savvas Stephanides

You would've avoided this whole story if you just didn't put flashes in your video to begin with 😅

Collapse
 
grahamthedev profile image
GrahamTheDev

Haha, very true! 🤣

Collapse
 
nickytonline profile image
Nick Taylor

Loki holding KFC

Collapse
 
grahamthedev profile image
GrahamTheDev

🤣

Collapse
 
optimisedu profile image
optimisedu

As an epileptic I want to thank you for this comment. Around one in 3000 people have uncontrolled epilepsy, many unknown. Only ten percent of epileptics are photosensitive but I got involved in development after my diagnosis - pretty severe but non photosensitive, certain frequencies just don't agree with me.

There is a huge problem with sloppy accessibility on the web, people are slowly catching on 👍, the more "a11y" is discussed the more people consider the tradeoff between acessability and performance.

Collapse
 
grahamthedev profile image
GrahamTheDev

I try…today as you can tell I was not very successful but I do try at least lol! A11y is a Massive and overlooked issue, I just try and do my part! ❤️

Thread Thread
 
optimisedu profile image
optimisedu • Edited

Yep even the term A11y isn't all that accessable (kinda the point but I can't help but feel the project is trying to be too clever. Different screen readers will read it differently).

Thing is semantic readability is important for teamwork if nothing else and I have met people who get half way through projects not knowing the meaning of an acronym because of imposter syndrome. "What is a SERP [search engine result page]"

Thread Thread
 
grahamthedev profile image
GrahamTheDev

Not to self promote (but I am lol), the "a11y" numeronym thing I wrote about that one, as it is one of the things that I totally agree needs rethinking / some thought in its use. I use it when others use the term if that is what they prefer but I will always start at "accessibility" and then move towards a11y if appropriate!

I also have a very "inappropriate" website "ultimatemotherf**kingwebsite.com" where I cover abbreviations and acronyms in my normal heavy-handed way 🤣 (if you don't mind gratuitous swearing you might enjoy that site! If you dislike swearing...yeah, don't go to that site!)

Basically, it is a very long winded and self-promotional way of saying "I agree with you 100%!" 😋

I noticed you just started becoming active here, I hope to see you pop up in the comments more often so we can discuss accessibility more, there are not enough of us fighting the good fight on this! ❤