The Moa bridge that auto-posts my Mastodon bits to Twitter has shut down as of 7 May:. Which means a lot less stuff from me except what I bother to come over here and manually share. Find me at

I am not on this hell-site anymore, but if you are following the #DisabilityIN hashtag I am posting stuff on my Masto under that same hashtag.

I updated my post “#accessiBe Will Get You Sued” with an embedded version of the Sherwin class action complaint against accessiBe. Anchor link:. #a11y #accessibility #overlays.

I encourage you to read the full complaint against #AudioEye and Moradi, which I have embedded (tagged PDF):. Or get it from the NYS courts site (same tagged PDF):. #accessibility #a11y #overlay.

“You will do the reviews and you will do what I tell you to do with AudioEye’s stock. Do what I tell you and set it [the VPN] up now.”. — attributed to #AudioEye CEO David Moradi at

“I will not support your healthcare and your salary, you mother**cker, earn your keep. You do what I say and when I say it. Respect your elders, mother**cker. — attributed to #AudioEye CEO David Moradi at

“First, do these reviews [for First Contact], then I need you to help me get AudioEye’s stock up.”. — attributed to #AudioEye CEO David Moradi at

“I am the law, I have the best lawyers in the world, I will never be in trouble, Buddy. I’m worth $200 million, and you’re a f*cking employee at AudioEye working for me.”. — attributed to #AudioEye CEO David Moradi at

“Buddy, if you’re not going to help with this, maybe you won’t get your equity in First Contact, and maybe I won’t feel like supporting your health benefits or your role at AudioEye anymore.”. — attributed to #AudioEye CEO David Moradi at

I collected its CEO’s threats against the whistleblower:. I have only returned to Twitter to tell you that this SLAPP-wielding #overlay company just might be run by a bad person. To excerpt what was in that article….

#AudioEye might be as immoral as we all suspect:. “Lawsuit Accuses NASDAQ-listed AudioEye CEO and its Executive Chairman of Stock Manipulation”. #accessibility #a11y #overlay.

Oh hey, it’s #GAAD. Be on the lookout for (mostly corporate) performative A11yship of #GAAD which is about to fill your timelines. I’ve shown #overlay vendors as worst offenders:. #accessiBe #AudioEye #FACILiti #LevelAccess #UserWay #accessibility #a11y.

Updated posts, (same content so pick your favorite #overlay)…. • #UserWay: • #accessiBe: • #AudioEye: No #FACILiti (not explicitly named in post), but still terrible & bullies. #accessibility #a11y.

FT references #AudioEye, #accessiBe, #UserWay (#LevelAccess), and #EqualWeb along with #overlays in general:. Non-paywall link:. Mischaracterizes as ‘AI’, but the output is still shitty for users regardless of branding. #a11y.

Follow-up:. #CSUNATC event page still there:. Host mentions it at 28:16 (then followed by an hour of dead air):. Disappointed CSUNATC accepted this *and* moderator #AudioEye affiliation hidden. What I know:.

This #CSUNATC session was in book for 2:20pm Friday. Slot empty online:. Not under #overlay names:. Nor daily addendum:. Anyone know what happened to this session with a #GAAD founder & two #AudioEye reps?

Throwing investor money at a clear PR ploy is not a fix (it didn’t help #accessiBe). If anything, it highlights the scam. Reputation washing works both ways. I feel bad for #AudioEye’s new CAO who likely had good intentions. We can’t save everyone. [2/2].

Remember #AudioEye is a bully:. Its #overlay (still) does not work:. It SLAPPs critics (I am not the only):. …and in the end harms users & #accessibility industry as a whole:. [1/2].

@IAAPOrg This is a great post from @LFLegal :. “Overlays and Ethics: a conference panel that hurt my heart”. She hits at the larger issues, even after the promised cancellation, that I could not verbalize in my anger earlier. #overlay #accessibility #a11y #IAAP.

Meanwhile, away from this awful platform, folks (and me) have been calling out @IAAPOrg for hosting a panel with two of the worst (and one I forgot existed) overlay companies:. Supposedly it was in error and they are killing the panel now. After blowback.

Anyway, I updated my post to show that, despite claims from #accessiBe that it has fixed its code and it tests with screen reader users, its very presence on a site will introduce WCAG violations (and legal risk, and break UIs for users):. #a11y. [5/5].