Recent searches
Search options
Outrageous! #AudioEye, a so-called #accessibility overlay vendor, has sued @aardrian, a highly respected member of the Accessibility community! Adrian has spent countless hours unveiling the pitiful truth about overlay accessibility solutions, with AudioEye being one of the prime examples. These so called solutions not only FAIL to meet their promises, but they also manage to erect MORE accessibility barriers on the websites they’re supposed to be ‘improving’.
Instead of acknowledging their flaws and engaging with the community, Audioeye hides behind lawsuits, which makes them seem even more miserable.This behavior is a glaring testament to their true intentions - which seems to be anything BUT making the world a more accessible place.
Accessibility work is an emotionally draining field, and it’s sickening to think of what Adrian is being forced to endure right now. https://adrianroselli.com/2023/05/audioeye-is-suing-me.html #standWithAdrian #a11y #overlays #gaad23
@aardrian If you haven’t heard of accessibility overlays before, I do encourage you to take a look at the Overlay Fact Sheet, which gives you an overview of whats so wrong about the whole deal. https://overlayfactsheet.com
(she/her) @jakobrosin Um...he was the 30th to sign the fact sheet. @aardrian
@CharJTF I think @jakobrosin meant that as a threaded reply to his first post to give context to readers. I suspect me being included at the start was unintentional.
@jakobrosin Thanks for letting me know 
I was obviously confused!
@aardrian
@CharJTF @jakobrosin @aardrian I wasn’t sure either 
I hear Mastodon is working on a quote feature, which would’ve been ideal in this case.
@jakobrosin @aardrian FYI, this link is broken
@jakobrosin @aardrian yep, reading this now. just wow
So, I posted on LinkedIn. I volunteer teach students who use screen readers.
Quick intro for folks who wonder what the fuss is about. If you're sighted, you look at a website and see everything above the fold in #parallel - all at once, at the speed of light. With a screen reader, the user experience is #serial - one element at a time. And those elements are traversed at the speed of sound.
In the late 1990's I did telephone tech support for a local dial-up internet provider. I had no way to see the user's screen, so I'd ask the user, "What do you see?" and they would tell me. Imagine navigating the internet like that.
Screen readers are not stupid. If you have an HTML element tagged as h1 or h2, the screen reader will say, "Heading, level 1 (or 2 or ...)" in addition to the contend. There are keyboard shortcuts to tab through same-level headings, and go up/down levels, etc. It's very interactive. And they can be cranked up to talk faster than you'd think it possible for comprehension. The point is, a lot of accessibility can be baked in, if you code your site with intentionality.
Having a script only works for the things the script is coded to handle, and some web devs pride themselves on being creative. The best solution is to design intentionally, but people like shortcuts.