home.social

#userway — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #userway, aggregated by home.social.

  1. Specifically #AudioEye (best known for SLAPP suits versus useful tooling) and #UserWay (best known for destroying the Level Access brand). Anyway, utter disappointment to see #CSUNATC giving them a platform.

    Refs:
    adrianroselli.com/2023/02/audi
    adrianroselli.com/2021/09/user

    #accessibility #overlays #a11y

  2. Specifically #AudioEye (best known for SLAPP suits versus useful tooling) and #UserWay (best known for destroying the Level Access brand). Anyway, utter disappointment to see #CSUNATC giving them a platform.

    Refs:
    adrianroselli.com/2023/02/audi
    adrianroselli.com/2021/09/user

    #accessibility #overlays #a11y

  3. Specifically #AudioEye (best known for SLAPP suits versus useful tooling) and #UserWay (best known for destroying the Level Access brand). Anyway, utter disappointment to see #CSUNATC giving them a platform.

    Refs:
    adrianroselli.com/2023/02/audi
    adrianroselli.com/2021/09/user

    #accessibility #overlays #a11y

  4. Specifically #AudioEye (best known for SLAPP suits versus useful tooling) and #UserWay (best known for destroying the Level Access brand). Anyway, utter disappointment to see #CSUNATC giving them a platform.

    Refs:
    adrianroselli.com/2023/02/audi
    adrianroselli.com/2021/09/user

    #accessibility #overlays #a11y

  5. Specifically #AudioEye (best known for SLAPP suits versus useful tooling) and #UserWay (best known for destroying the Level Access brand). Anyway, utter disappointment to see #CSUNATC giving them a platform.

    Refs:
    adrianroselli.com/2023/02/audi
    adrianroselli.com/2021/09/user

    #accessibility #overlays #a11y

  6. @ppatel @aardrian I sure hope so... Right now I'm dealing with a health provider that's confused to learn they're not accessible despite paying for #UserWay... This isn't even just about #accessibility it is a straight up fraud case!

  7. From @LFLegal, a magistrate just has recommended the suit against UserWay (Level Access) from BloomsyBox move forward.

    BloomsyBox sued UserWay for violation of the Delaware Consumer Fraud Act.

    More info and links to recommendation:
    lflegal.com/2025/02/userway-ov

    #overlays #UserWay #LevelAccess

  8. From @LFLegal, a magistrate just has recommended the suit against UserWay (Level Access) from BloomsyBox move forward.

    BloomsyBox sued UserWay for violation of the Delaware Consumer Fraud Act.

    More info and links to recommendation:
    lflegal.com/2025/02/userway-ov

    #overlays #UserWay #LevelAccess

  9. From @LFLegal, a magistrate just has recommended the suit against UserWay (Level Access) from BloomsyBox move forward.

    BloomsyBox sued UserWay for violation of the Delaware Consumer Fraud Act.

    More info and links to recommendation:
    lflegal.com/2025/02/userway-ov

    #overlays #UserWay #LevelAccess

  10. From @LFLegal, a magistrate just has recommended the suit against UserWay (Level Access) from BloomsyBox move forward.

    BloomsyBox sued UserWay for violation of the Delaware Consumer Fraud Act.

    More info and links to recommendation:
    lflegal.com/2025/02/userway-ov

    #overlays #UserWay #LevelAccess

  11. From @LFLegal, a magistrate just has recommended the suit against UserWay (Level Access) from BloomsyBox move forward.

    BloomsyBox sued UserWay for violation of the Delaware Consumer Fraud Act.

    More info and links to recommendation:
    lflegal.com/2025/02/userway-ov

    #overlays #UserWay #LevelAccess

  12. But back to Michael's effort — it seems to validate things have not improved nearly two years after #UserWay / #LevelAccess had that hilarious failure with LLM-generated “accessible” code supposedly trained on its own stuff.

    Ref: FuxMyCode.ai/

  13. From @LFLegal:

    New on LFLegal: Another small business filed a federal class action lawsuit against a web #accessibility #overlay company. Why was UserWay sued? It believed the hype, licensed the software, and still got sued by a #blind person who couldn't use the site. #disability
    lflegal.com/2025/02/userway-ov

    From me: #LevelAccess is #UserWay now, remember that.

  14. Hey, I finally got access to the class action suit against #UserWay (LevelAccess) filed in July:
    adrianroselli.com/2021/09/user

    Untagged PDF, sorry.

    This covers UserWay making misleading claims about what its #overlay could do.

    #accessibility #a11y

  15. @aardrian I just saw a website with #UserWay and was at first swayed by the bells and whistles of it all... but this gives me some thought... and pause.

    See "Web Content Accessibility Guidelines (WCAG)"

    #Blogging #WordPress #Plugins #WCAG
    #ADA #Disabilities #Accessibility #AccessibilityOverlay #overlay #AmericansWithDisabilities #TheBarriersWeFace

  16. This a good distillation of #accessibility #overlays:
    chriscoyier.net/2024/07/13/its

    If they were actually useful, they wouldn’t need to use SLAPPs to silence detractors (#AudioEye, #Faciliti), or see their clients or themselves sued for failing to work (#accessiBe), or regularly misrepresent their relationship with standards bodies (#UserWay)

    Scams upon scams.

    #a11y

  17. Oh hey, it’s #GAAD.

    Be on the lookout for the (mostly corporate) performative A11yship of #GAAD which is about to fill your timelines.

    A couple years ago I demonstrated #overlay companies as the worst offenders:
    adrianroselli.com/2022/05/the-

    #accessiBe #AudioEye #FACILiti #LevelAccess #UserWay #accessibility #a11y

  18. “Socks, lies, and accessibility”
    janmaarten.com/gaad-2023/

    Where @janmaarten shows that just a couple days after #accessiBe’s CEO promised to stop being such a lying liarface it went and used sock puppet Twitter accounts to promote its #overlay.

    As I keep saying, past behavior is a predictor of future behavior (side-eyes #AudioEye, #UserWay, #FACILiti).

    #a11y #accessibility

  19. Irony.

    It's unfortunate when good messages are undercut (while also validated in this case?) because the site hosting them uses an #accessibility #overlay. In this case, #UserWay by #LevelAccess.

    Edited to add link to valuable article: c-q-l.org/resources/articles/m

  20. WCAG•com has bad/wrong info, eg. button:
    web.archive.org/web/2024020518

    It was made by Essential Accessibility, bought by Level Access, which now owns #overlay company #UserWay. Oddly, it obfuscates ownership.

    The lack of transparency was raised 7 months ago to the Level Access CMO (A11y Slack walled garden), but no action taken:
    web-a11y.slack.com/archives/C0

    And so bad info persists and the lack of branding is an accidental “win” for Level Access.

    Either way, maybe block at firewall.

  21. I have updated three posts on my site with this info (mostly the same content, tweaked for each post):

    • “#UserWay Will Get You Sued”
    adrianroselli.com/2021/09/user

    • “ADA Web Site Compliance Still Not a Thing”
    adrianroselli.com/2022/03/ada-

    • “‘Accessibility at the Edge’ W3C CG Is an Overlay Smoke Screen”
    adrianroselli.com/2022/09/acce

    Misrepresentation and misuse of the W3C brand and its employee / contractor relationships is the UserWay (now #LevelAccess) norm.

    #overlay #accessibility #a11y

  22. Consider when reading obvious puff pieces like this one:

    “How Level Access Acquiring UserWay Transforms The Web Accessibility Market”
    web.archive.org/web/2024040911

    Signs this is astroturfing:

    • Claims it is ‘AI’ (it never was, & UserWay’s first LLM effort is still a gag),
    • effusive positive terms to describe it and #LevelAccess,
    • ignores heaps of (real) press critical of UserWay,
    • no other sources,
    #UserWay has a history of doing this (see its overlay Community Group).

    #accessibility #a11y

  23. The #UserWay / #AudioEye CG has continually misrepresented its relationship with the W3C, which I have documented:
    adrianroselli.com/2022/09/acce

    The CG head doesn’t seem to think there is anything wrong with this behavior. I am of the opinion this behavior violates the @w3c CG rules (on a plane so cannot look it up easily).

    So now an #overlay BS document is referenced in a DoJ document.

    Yeah, I may be angry.

  24. Updated posts to reference the FT #overlay article, all with the same content (so pick your favorite overlay)…

    #UserWay: adrianroselli.com/2021/09/user

    #accessiBe: adrianroselli.com/2020/06/acce

    #AudioEye: adrianroselli.com/2023/02/audi

    I did not add it to #FACILiti because it is not explicitly named in the post. But they are also terrible and bullies.

    Thanks to @tink for first sharing the article.

    #accessibility #a11y

  25. FT article that references #AudioEye, #accessiBe, #UserWay (#LevelAccess), and #EqualWeb along with #overlays in general:
    front-end.social/@tink/1122285

    Non-paywall link:
    archive.is/MRhll

    While it mischaracterizes the crappy algorithms as ‘AI’, the output is still shitty for users regardless of branding.

    #accessibility #a11y

  26. @koos It’s an #overlay. It may not lie as openly as #UserWay (#LevelAccess) or #accessiBe, and it may not file frivolous lawsuits like #AudioEye, but Eye-Able introduces WCAG violations and does not fix much. You can read the discussion around trying to get itself delisted from the Overlay Fact Sheet a few months ago:
    github.com/karlgroves/overlayf

    FWIW, most overlay companies also do manual work. But Eye-Able’s own errors demonstrate it likely isn’t good at that either.

    #accessibility #a11y

  27. "this is another example of bullshit accessibility, profit driven products, fueled by private equity companies" 😢 html5accessibility.com/stuff/2 #a11y #UserWay #overlays #fail

  28. Steve shows a #UserWay bug I pointed out to UserWay (acknowledged by its CTO in person) still exists:
    mastodon.social/@SteveFaulkner

    My 2021 report:
    adrianroselli.com/2021/09/user

    The UserWay CTO claimed “they” fixed it — “they” being the UserWay customer by firing UserWay and removing the #overlay.

    #a11y #accessibility

  29. [3/3]

    Aaron’s is a less acerbic and more hopeful version of my binary “No, ‘AI’ Will Not Fix Accessibility”:
    adrianroselli.com/2023/06/no-a

    Léonie’s confirms that #UserWay / #LevelAccess has trained its LLM on its own broken code and has not improved since I called it out 8 months ago:
    adrianroselli.com/2021/09/user

    The point is, these are fallible tools that can be helpful with the right existing knowledge or in absence of anything else.

    #accessibility #a11y

  30. Sharing a LinkedIn (ugh) post because it hits at core concerns over the marketing- and revenue-driven models of the (abled) corporate efforts supplanting genuine #accessibility in favor of inadequate tools pitched using FUD, now buying veneers of credibility despite often amoral actions:

    linkedin.com/feed/update/urn:l

    By @fedbysandrine
    #a11y #overlay #AudioEye #accessiBe #UserWay #FACILiti

  31. Over in the walled-garden A11y Slack, the IAAP rep there has left this statement and said proper statements will be going out on its socials:
    web-a11y.slack.com/archives/C0

    Links in post:
    • “webpage” accessibilityassociation.org/s
    • “European Disability Forum” edf-feph.org/
    • “joint statement regarding overlays” edf-feph.org/publications/join

    Sorry for the wall of text.

    #overlay #UserWay #FACILiti #AccessiWay #accessibility #a11y #IAAP

  32. Late to the party because I really needed to think about this.

    I *believe* what is happening is IAAP is hosting a session promoting #overlays.

    It has 7 dudes on a panel:

    • One is from #FACILiti (filed SLAPPs against disabled critics).
    • One from #UserWay (known for lifting content, failing at WCAG).
    • One from #AccessiWay (was so bad I ignored it).

    And then three more I’m disappointed to see aligning themselves with this.

    What’s the point of IAAP again?

    web.archive.org/web/2024012616
    [Edited URL]

  33. Remember that SLAPP #AudioEye filed against me?

    The Accessibility Craft podcast covers it in its first episode discussing overlays:
    accessibilitycraft.com/a-long-

    Also touches on #LevelAccess becoming an #overlay vendor with its acquisition of (the amoral, IMO) #UserWay.

    I can neither confirm nor deny Amber’s assertion about who “won” that SLAPP, BTW. The settlement agreement precludes me speaking about it.

  34. 41 positive responses to my comment on the #LevelAccess CEO statement on the #UserWay purchase:
    linkedin.com/feed/update/urn:l

    The Level Access CEO has not responded — and I did not ask a question, so that is fine. But after a handful of initial replies, he has stopped responding.

    I assume lawyers suggested he not comment further.

    Which also suggests Level Access has decided to end its dialog with the #accessibility industry and community.

  35. Pat notes that if #LevelAccess successfully fixes #accessibility issues at the source for #UserWay customers, then the #overlay product will no longer have its claimed value (other than offering crappy versions of features already built into browsers).

    Which suggests #LevelAccess is financially motivated not to kill the monthly revenue streams it just paid $100 million to acquire.

    linkedin.com/feed/update/urn:l

  36. Utter horseshit framing from #UserWay (now #LevelAccess):

    “[‘Accessibility at the Edge’ Community Group] is where W3C is developing, identifying, and categorizing existing and prospective features relating to edge computing technologies in the realm of internet accessibility, including the role of overlays.”

    No, @w3c is not doing that. You and #overlay shills are.

    Remember, W3C Community Groups do not speak for W3C, and this one in particular is a smokescreen:
    adrianroselli.com/2022/09/acce