The Moa bridge that auto-posts my Mastodon bits to Twitter has shut down as of 7 May:
fosstodon.org/@moaparty/1103…
Which means a lot less stuff from me except what I bother to come over here and manually share.
Find me at toot.cafe/@aardrian.
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.
toot.cafe/tags/DisabilityIN
I updated my post “#accessiBe Will Get You Sued” with an embedded version of the Sherwin class action complaint against accessiBe.
Anchor link:
adrianroselli.com/2020/06/ac…
#a11y #accessibility #overlays
#AudioEye might be as immoral as we all suspect:
“Lawsuit Accuses NASDAQ-listed AudioEye CEO and its Executive Chairman of Stock Manipulation”
prnewswire.com/news-releases…
#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 prnewswire.com/news-releases…
I encourage you to read the full complaint against #AudioEye and Moradi, which I have embedded (tagged PDF):
adrianroselli.com/2023/02/au…
Or get it from the NYS courts site (same tagged PDF):
iapps.courts.state.ny.us/nys…
#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:
adrianroselli.com/2022/05/th…
#accessiBe #AudioEye #FACILiti #LevelAccess #UserWay #accessibility #a11y
FT references #AudioEye, #accessiBe, #UserWay (#LevelAccess), and #EqualWeb along with #overlays in general:
front-end.social/@tink/11222…
Non-paywall link:
archive.is/MRhll
Mischaracterizes as ‘AI’, but the output is still shitty for users regardless of branding.
#a11y
Updated posts, (same content so pick your favorite #overlay)…
• #UserWay: adrianroselli.com/2021/09/us…
• #accessiBe: adrianroselli.com/2020/06/ac…
• #AudioEye: adrianroselli.com/2023/02/au…
No #FACILiti (not explicitly named in post), but still terrible & bullies.
#accessibility #a11y
This #CSUNATC session was in book for 2:20pm Friday.
Slot empty online:
csun.edu/cod/conference/sess…
Not under #overlay names:
csun.edu/cod/conference/sess…
Nor daily addendum:
csun.edu/cod/conference/sess…
Anyone know what happened to this session with a #GAAD founder & two #AudioEye reps?
Follow-up:
#CSUNATC event page still there:
csun.edu/cod/conference/sess…
Host mentions it at 28:16 (then followed by an hour of dead air):
youtube.com/live/VykxHNigHQQ…
Disappointed CSUNATC accepted this *and* moderator #AudioEye affiliation hidden.
What I know:
adrianroselli.com/2023/02/au…
Remember #AudioEye is a bully:
adrianroselli.com/2022/04/my…
Its #overlay (still) does not work:
adrianroselli.com/2023/02/au…
It SLAPPs critics (I am not the only):
adrianroselli.com/2023/05/au…
…and in the end harms users & #accessibility industry as a whole:
adrianroselli.com/2024/01/au…
[1/2]
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]
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:
toot.cafe/@aardrian/11182316…
Supposedly it was in error and they are killing the panel now. After blowback.
This is a great post from @LFLegal :
“Overlays and Ethics: a conference panel that hurt my heart”
lflegal.com/2024/01/zero-con…
She hits at the larger issues, even after the promised cancellation, that I could not verbalize in my anger earlier.
#overlay #accessibility #a11y #IAAP
I resent Twitter and avoid it except when tagged.
But with overlays in general, they are happy to keep promoting their problematic products on this equally problematic platform.
Eg: #accessiBe’s CVO spamming the hashtag with feelgood stories that hide its broken product.
[1/5]
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):
adrianroselli.com/2020/06/ac…
#a11y
[5/5]

