At long accessible last 7/16 '23
Is OnePo fully accessible? Um... yeah almost certainly not, because I haven't had it tested rigorously for that, nor have I consulted anyone with a disability about their actual experiences. Those steps would be good to take.
One bit of accessibility progress though: alternative text for images.
Adding an alt text field for images in posts was easy-peasy. Adding this to images in comments was an absolute bear, because of the lil' shortcut pattern I had before: tapping the image button on a comment immediately prompted you for an image file, and then immediately uploaded it, and you were done!
This was a nice pattern in a lot of ways, very light and breezy, but also totally brittle: the moment you wanted to add alt text it didn't work for us at all.
So I reworked the image comment editor, and now there is an alt text field beneath an "Upload Image" button, all proper-like.
There's another win today though: image uploads should be considerably faster, especially over slow links, and especially when the original file is large. That's because images are now resized on your device before they are uploaded.
It's true that this puts a slightly greater burden on the local device, but in practice it's a device every web browser has been ferociously optimized to handle, and most likely handles in dedicated hardware. That's because every website is crammed to the gills with images that don't precisely match the size of your screen. So asking your device to do this is reasonable, and it significantly reduces the workload for the server.
"Uh... yeah Tom, that workload must be awful with somebody posting once every hour or so!" Yeah, true, but I still get to learn useful things about doing this kind of stuff at scale, even if scale hasn't really happened here.
Anyway, here's Wonderwall. Photo-comment away, and let me know if anything breaks!
P.S. Hovering the mouse etc. will not display the "alt text." That's because it is truly set up as alternative text (e.g. the "alt" attribute) for accessibility purposes, and regular browsers intentionally don't display it by default. That "text on hover" thing you may be thinking of is the "title" attribute, and describing an image effectively for those who can't see it isn't really the same use case.
(Also - that new profile pic is killing me! 😁)
Refreshed the page, and it appears to have functioned normally - just not informed me that it worked.
In case it matters - Chrome v 114.0.5735.199 on Windowz 10 Enterprise
I use Safari on my phone, Chrome on desktop for "work stuff" and Safari for OPW, but I'm willing to change.