I wonder how @neilpatel feels schilling for @accessiBe when a non-trivial number of actual people with disabilities are discussing how to *block* AccessiBe because it interferes with their experience on the Web?
Marc Solomon @mr_marcsolomon
27 Feb 2021
My former colleague created an awesome open source tool to prevent #AccessiBe from interfering with the #ScreenReader experience. It's a shame he had to waste his valuable the on this. Thanks for helping users reclaim web #accessibility @ed_edwardson! #a11y
1
9
23
Hey Karl, I'm out of the loop regarding accessibe can you provide a quick synopsis of the issue or a link for me to catch up it relates directly to my course of study currently and I would very much appreciate it thank you so much!
1
2
@aardrian has a post with a lot of info: adrianroselli.com/2020/06/ac…
2
4
Replying to @joedolson @karlgroves @neilpatel @AccessiBe @aardrian
Conclusion after study: accessiBe fails all foundational principles of Web, obfuscation of content is antithetical to #a11y and the broader meaning of accessible, paywalls cause division not unity, the AI is artifice not intelligence. This is not new, not #a11y and not the Web.

Mar 1, 2021 · 11:06 AM UTC

1
6
1
7
Replying to @mholzschlag @joedolson @karlgroves @neilpatel @AccessiBe @aardrian
Hm... it's worse than that. The web has all that, but let's add on top that AccessiBe can take an inaccessible-but-can-deal-with-it website and make it completely unusable (with a screen reader anyway).
1
3
I agree and I also think there's a larger danger here when people co-opt language and symbols then reuse them and shift meaning it causes extra confusion we don't need in our industry which is struggling enough with the tack it on after or it doesn't matter syndromes. I'm angry.
1
more replies