aevai want to make a little art portfolio site, and I'm stuck between wanting to fuck with scrapists and wanting to not fuck with screen readers. I'm considering chopping up images into tiles which would be assembled into their correct relative locations via css or something. i could even put alt text on it with a transparent image layered on top spanning the full area. downside is real people wouldn't be able to download the images though :/
of course that's all assuming they don't just dump the frame buffer somehow. same problem as anything else, it's unclear to what extent anti scraping measures actually work
another idea i had was use webgl instead of images and have the images gradually assemble, so you'd have to wait a short amount of time to see the full thing. that would allow downloading but scraping would need to be more elaborate
ferunando@aeva 🤔 if you are going to require javascript anyway, give yourself way more work and hook up that WAI-ARIA thingy? or the web-speech one. well, at least, those are the options *i* am considering for remaking my stuff....
* https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/Accessibility/WAI-ARIA_basics
* https://developer.mozilla.org/en-US/docs/Web/API/Web_Speech_API
WAI-ARIA basics - Learn web development | MDN
Following on from the previous article, sometimes making complex UI controls that involve unsemantic HTML and dynamic JavaScript-updated content can be difficult. WAI-ARIA is a technology that can help with such problems by adding in further semantics that browsers and assistive technologies can recognize and use to let users know what is going on. Here we'll show how to use it at a basic level to improve accessibility.