have also wanted to use localstorage to remember if the visitor wants to keep animated gifs on across pages but havent made any good progress yet. these kinds of things are difficult for me to learn
if anyone knows of any good resources to learn these things, i would love to know. my searches havent turned up anything helpful. but keep trying 👊👽 fighto
;u; right?! it seems to fix one accessibility concern, but cause another i think?! my options at this point... 1. cram as much javascript into my brain until something clicks (has been proving difficult for me personally) 2. take it to stackoverflow or somesuch place (and prepare to be berated)
3. pray that OS/browsers create more accessibility options so everyone can browse safely without fear and frustration ): but i try to do all i can til that day... 4. perhaps a secret fourth thing, i just havent thought of it yet.
re: no alt text on freezeframe canvases -- wave webaim doesnt flag any error, so might be a firefox accessibility false positive (found similar issue for svg). got rid of the error in firefox by updating freezeframe.js to have alt="" title="" in the canvas WHEW!!! as for the localstorage idea, no luck on that yet. stay tuned...
i've seen some examples of a modified details element that allow people to toggle the animated versions as they like! it doesn't require javascript, and if implemented well it doesn't cause a flash of animated content either. i'll try and fish it back up if you're looking
I checked my website and freezeframe.js doesn't seem to cause the same issue for me - no idea why though. It is very finicky in my experience and honestly it confuses me LOL.
so that alt text issue i mention, i only see in firefox accessibility so far, so might be a browser thing. im thankful for it but yea freezeframe is not perfect for sure ;u; i have a laundry list of things i want to improve for it with no clue if its even possible wahaha...
have also wanted to use localstorage to remember if the visitor wants to keep animated gifs on across pages but havent made any good progress yet. these kinds of things are difficult for me to learn
if anyone knows of any good resources to learn these things, i would love to know. my searches havent turned up anything helpful. but keep trying 👊👽 fighto
Wait, really?? That’s horrible! Ugh, what do you even do then?
;u; right?! it seems to fix one accessibility concern, but cause another i think?! my options at this point... 1. cram as much javascript into my brain until something clicks (has been proving difficult for me personally) 2. take it to stackoverflow or somesuch place (and prepare to be berated)
3. pray that OS/browsers create more accessibility options so everyone can browse safely without fear and frustration ): but i try to do all i can til that day... 4. perhaps a secret fourth thing, i just havent thought of it yet.
re: no alt text on freezeframe canvases -- wave webaim doesnt flag any error, so might be a firefox accessibility false positive (found similar issue for svg). got rid of the error in firefox by updating freezeframe.js to have alt="" title="" in the canvas WHEW!!! as for the localstorage idea, no luck on that yet. stay tuned...
i've seen some examples of a modified details element that allow people to toggle the animated versions as they like! it doesn't require javascript, and if implemented well it doesn't cause a flash of animated content either. i'll try and fish it back up if you're looking
oo i havent heard of that one! ill def look into it. if uve got a link on hand, that would be awesome too
I checked my website and freezeframe.js doesn't seem to cause the same issue for me - no idea why though. It is very finicky in my experience and honestly it confuses me LOL.
so that alt text issue i mention, i only see in firefox accessibility so far, so might be a browser thing. im thankful for it but yea freezeframe is not perfect for sure ;u; i have a laundry list of things i want to improve for it with no clue if its even possible wahaha...