One hoopy frood who really knows where his towel is. Not a bird lawyer. Tweets are auto-posted from https://xitter.cf/t.co/kxh7sf2uwW, and sometimes they do not come over.

Buffalo, NY
Joined September 2008
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.
1
6,235
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
1
1,167
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?
1
3
1,199
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…
1
2
481
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]
3
12
2,410
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.
3
1
13
1,411
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]
1
3
1
13
1,505
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]
2
6
480