#UserWay Will Get You Sued
- Lie: Makes your site ADA compliant
- Lie: Strong reputation with the disabled community
- Questionable: Privacy by design, data minimization
- Lie: Loved by Disabled Community
- Anti-accessiBe Press is Critical of UserWay Too
- This Is Just UserWay’s Marketing Response
- Olympics and #WeThe15
- Removed: 19 September 2021
- UserWay Demonstrates It Does Not Understand WCAG
- UserWay Buys Positive Reviews
- UserWay Relies on False Advertising
- After a Conversation with the COO: 21 March 2022
- UserWay Tries to Cash in on W3C Brand: 19 June 20222
- UserWay Renames the Community Group: 23 June 2022
Thanks to a comment on my post #accessiBe Will Get You Sued, I found UserWay had taken the meat of that post, re-cast as its own effort, and was using it as a marketing effort to frame its overlay as a better product than accessiBe.
I promptly captured the page in the Wayback Machine, because I have no interest in linking to the live version, and asked UserWay to remove my name and any references from its post. Twice.
For some reason, in its response UserWay decided linking to Gareth Ford Williams’ post What are accessibility overlays good for? somehow validated it and its overlay.
Unlike my post #accessiBe Will Get You Sued, I am not going to give UserWay free technical or business advice. I learned that lesson when accessiBe used it to attenuate its messaging (but, interestingly, not fix its product). I am going to paint with some broad strokes, however. I am also skipping some of the claims that I cannot validate (because I have no access to their servers and/or the statements are fluff).
Makes your site ADA compliant
This statement misrepresents the ADA. UserWay is taking advantage of ongoing misunderstandings with what the ADA covers, what case law says it covers, and what people buying these products thinks it covers.
If we take ADA at face value, this is similar to saying UserWay makes your site FDA compliant. If we take ADA as interchangeable with WCAG, then a quick automated check will demonstrate otherwise.
Axe, which prides itself on no false positives, finds 3 WCAG issues tied to testable WCAG Success Criteria on that page. ARC Toolkit finds 4, matching Axe and adding another valid problem. WAVE finds none, but does raise 202 alerts, including 111 cases of suspicious image alternative text. My favorite example of this is the image of the accessiBe widget that has the alternative text
Picture of UserWay widget.
UserWay Causes WCAG Failures
Added 31 October 2021. The article Technology can’t solve the problems ableism creates at The Stanford Daily talks about the hype around the “laser cane” intended for blind people. It also unintentionally makes a statement on overlays, with UserWay’s tool providing the metaphor.
Update: 21 March 2022
After my conversation with UserWay’s COO, I evaluated the single site example in this post. To the COO’s credit, he is correct that someone fixed the problems I identified at The Stanford Daily — by removing the UserWay overlay.
Strong reputation with the disabled community
Nearly 600 people in and supporting the disabled community have said very much the opposite. They have signed on to the Overlay Fact Sheet which includes this statement:
- More specifically, we hereby advocate for the removal of accessiBe, AudioEye, UserWay, User1st, MK-Sense, MaxAccess, FACIL’iti, and all similar products and encourage the site owners who’ve implemented these products to use more robust, independent, and permanent strategies to making their sites more accessible.
Privacy by design, data minimization
I cannot look into UserWay’s systems to understand what it does with the data it captures. I can, however, look at how it presents privacy and compliance to users. It has an alphabet soup of related and unrelated laws linked from its footer: HIPAA, GDPR, COPPA, FERPA (it also lists ATAG and WCAG, which are outside the scope of privacy). I was surprised PCI-DSS wasn’t in there just for more letters.
Following each link brings you to a page describing the law but not how UserWay conforms — let alone how it is relevant. HIPAA, for example, has no bearing on UserWay (egad, I hope no patient portals are using it). Just like anti-vaxxer claims that asking for proof of a vaccine is a HIPAA violation, UserWay is happy to capitalize on that same misrepresentation.
UserWay is, however, happy for you to contact it instead of telling you how any of these apply:
To learn more about how UserWay’s Accessibility Widget complies with HIPAA regulations, please contact us. The contact us link is the same destination as the free trial link that immediately follows.
Loved by Disabled Community
As its sole piece of evidence, UserWay references (but does not link) one tweet from 2018. A 3½-year-old tweet. I suppose all I need to do is find a single tweet critical of UserWay and I have disproven it.
Maybe I can find a member of the disabled community who took more time than a casual tweet, though.
Haben Girma has been advocating on behalf of the disabled community for years. She wrote about being the first Deafblind person to graduate from Harvard Law School. When she weighs in on overlays, it is not just from personal experience but also based on her recognition of the harms the tool is creating.
Criticism from Twitter Users
I am a bit amused that UserWay thinks users critical of accessiBe automatically equates to support of UserWay. I mean, I get it, for the people they are targeting that is probably more than adequate.
But half of the people behind the tweets quoted on that page are signatories to the Overlay Fact Sheet. They have explicitly stated UserWay is one of the bad options. UserWay is intentionally misrepresenting their statements as a result. And they are not cool with that.
Anti-accessiBe Press is Critical of UserWay Too
UserWay makes it a point to reference articles that are critical of accessiBe explicitly. More accurately, it references two news pieces and two opinion pieces. One opinion piece is my post #accessiBe Will Get You Sued, which I have updated to include a note about UserWay.
Remember, these are pieces critical of accessiBe that go out of their way to note that all overlays are a problem.
But over the past several months in particular, as AccessiBe’s footprint has spread, many people with disabilities have grown increasingly angry at it and other automatic web overlay companies. The tools often make websites less usable than they were before, and the companies’ marketing strategies, they say, emphasize the need for business owners to avoid lawsuits rather than actually make their websites usable.
Greco, at the University of California, Berkeley, said other companies have similar products that have many of the same technical issues AccessiBe does. But AccessiBe stands out because of its rapid growth, heavy marketing and defensive style of engagement with blind people who claim it hasn’t worked for them.
The other opinion piece is a Forbes Sites piece (these are written by people who pay to host their articles under the Forbes banner, they are not Forbes writers) that says:
First and foremost, there remains one key principle to keep front of mind — currently, there exists no overlay technology on the market that can, by itself, render a website fully accessible and protect it from ADA lawsuits.
This Is Just UserWay’s Marketing Response
This post from UserWay is just a response to accessiBe’s own claim that UserWay will put you at risk, except in this case UserWay uses the title of my post (ostensibly to reduce its legal exposure). Obviously, there is evidence that sites with accessiBe still get sued, but UserWay’s argument is that accessiBe’s overlay is somehow unique for that.
UserWay has removed the abstract and link to my post, but it has not removed the title of my post. That title,
accessiBe Will Get You Sued, still lives on the UserWay page in an
<h2>. The heading suggests they like the link juice too much and the quotes imply some level of distance should accessiBe’s lawyers come calling (by claiming they are simply quoting me).
Olympics and #WeThe15
UserWay proudly advertises its use on the Tokyo Paralympics web site. Another site from the Paralympic Committee, #WeThe15, was launched to promote disability awareness and end discrimination. It also had the UserWay overlay.
But as the #WeThe15 campaign got traction on Twitter and the community it was claiming to support went and looked at the site, the response to that overlay was swift. Folks were surprised, called it out, shared their frustration, and even gave them the benefit of the doubt.
I am not surprised the Paralympic folks have done nothing. Partly because they were not directly engaging the community, and partly because between taking the inspiration porn angle and failing to make its videos accessible (that it borrowed from WeThe15), it seems fair to assume they were not really invested in the message.
Will UserWay get you sued? Maybe. We already know that users can disable overlays, scripts can fail, connections can be dropped, and features can collide. Even if the product itself performed as it claims, there is always a chance it will not function. As such, it is a poor substitute for building your thing the right way the first time.
I cannot say if UserWay is as bad as accessiBe on the technical side, because I am not giving away free reviews anymore. I cannot even say if UserWay is as amoral as accessiBe, simply because UserWay has less money to spend. I can say, however, that the trends are clear — UserWay lies about its offering and lies about community support. I doubt it is in any way better, no matter how low the bar is that accessiBe has set.
UserWay and accessiBe are two rotten peas in a dirty dirty pod.
Removed: 19 September 2021
UserWay has made no apologies nor explanations. I leave it to the reader to guess why UserWay decided now to remove it, and wonder how many other false claims and stolen material UserWay is passing off as its own truthful content. If nothing else, UserWay has demonstrated it has a credibility problem.
Update: 21 March 2022
After my conversation with UserWay’s COO, he asked me to remove this post, believing that since UserWay had deleted the page with my stolen content there was no longer a reason for me to leave it. I pointed out that UserWay never publicly acknowledged it had taken my content, mis-represented my words, and used my name in its marketing efforts all without my consent. Even today that page is a 404 instead of a public apology, which I explained demonstrates how UserWay believes it did no wrong and only moved to limit its reputational harm.
This post will remain, even if UserWay finally demonstrates contrition, because it is a record of UserWay’s unethical business practices and its failure to take steps to correct them. The best predictor of future behavior is past behavior, and we need to remember how UserWay (and its leadership) has operated in the past before trusting it in the future. We can only hope it is willing to make that difficult journey to rehabilitate its products and services before trying to do so with its image.
UserWay Demonstrates It Does Not Understand WCAG
Added 21 November 2021. Or perhaps UserWay chooses to ignore WCAG. The more charitable take, however, is UserWay is just incompetent, not intentionally ignoring a standard that its own product claims will
The code also demonstrates UserWay does not understand ARIA. While
aria-label does not belong on a
<div>, maybe UserWay’s hope was to override all the content within (because that’s what
aria-label does). Though if the
aria-hidden="true" on the images with
alt="" wasn’t a head scratcher on its own, given the context of the
aria-label wrapper it is certainly one now.
<div class="bf2021__inner" aria-label="Black Friday 30% Off! Start Free Trial" onclick="[…]"> <div class="bf2021__title" data-uw-styling-context="true"> Black Friday <br role="presentation" data-uw-rm-sr=""> 30% Off </div> […] <div class="logo"><img src="[…]" alt="" aria-hidden="true"></div> <div class="logo-gradient"><img src="[…]" alt="" aria-hidden="true"></div> <div class="woman woman_b"> <picture>[…]</picture> </div> <div class="dots"><img src="[…]" alt="" aria-hidden="true"></div> </div>
As part of this Black Friday deal, UserWay’s spam emails are also promising
full WCAG coverage (emphasis theirs). That is clearly not true.
UserWay Buys Positive Reviews
Added 22 November 2021. Not to be outdone by accessiBe’s practice of paying for praise, UserWay is offering its customers Amazon gift cards to leave positive reviews at software review site G2.com.
The UserWay reviews on G2.com are not from end users, but from UserWay customers. To reiterate, the people rating the product are not disabled end users who need accessibility affordances, they are from business owners who are being compensated to leave positive reviews. Note that UserWay says it will review submissions before compensation.
If you want to see what contributors and editors for WCAG, ARIA, and HTML specifications, internal accessibility experts for companies, internal accessibility experts from higher education institutions, lawyers for the disabled, contributors to assistive technology software such as JAWS and NVDA, and scores of end users with disabilities think about UserWay, then visit the Overlay Fact Sheet.
None of the names on the Overlay Fact Sheet were paid for their signature.
UserWay Relies on False Advertising
Added 15 December 2021. The site Overlay False Claims documents provably incorrect assertions made by UserWay throughout its marketing efforts. The site also tracks other anti-competitive behavior, downloads for use in legal action or consumer complaints, and links for filing consumer complaints throughout the US and Canada.
If you have other examples of false advertising (perhaps you have received marketing emails, or been pitched by your web site vendor / overlay reseller) or links for filing consumer complaints in other countries, then please submit a GitHub issue.
UserWay Will Not Protect from Lawsuits
As part of the 2021 Digital Accessibility Legal Summit, Jeremy Horelick, Jason Taylor and Richard Hunt discuss widgets, plug-ins and overlays being marketed as one-step software solutions to website accessibility. They provide a brief review of terminology and differences between the various products, followed by an examination of whether these tools will do what they promise—in terms of both actual accessibility and protection from website accessibility litigation.
When asked if overlays reduce litigation expense or risk, the answer was a resounding no. You can jump to 31:46 of the video and listen/read for yourself, but I have quoted the salient bit:
They absolutely do not. And there are two reasons why this is true. The first reason is simply because they don’t actually fix websites. […]
The other reason is because the law firms, not all the law firms, but many of the law firms that are in this area do not care whether the website is really accessible or not. Their desire is to find something that they can identify as an error, usually by measuring it against WCAG, and if they can find that error, they can file a lawsuit in good faith. Remembering that their goal is to settle the lawsuit as soon as possible.
Update: 21 March 2022
On slide 31 I referenced a claim by UserWay that there were no lawsuits mentioning UserWay. I said I could not verify that claim. Thanks to UserWay saying the talk was not accurate, I was motivated to dig up a suit that mentions UserWay. Remember UserWay’s now-deleted claim was live as far back as 9 September, and most certainly earlier.
In Paguada v. YieldStreet, YieldStreet attempted to get the lawsuit dismissed by adding the UserWay plug-in sometime in March 2021. In April 2021, an expert witness identified barriers and WCAG failures that persisted despite (and/or because of) the plug-in. The motion to dismiss was denied, signed 20 October 2021.
UserWay was not named in the original suit, only the motion, and UserWay’s failure to provide the required cure was not official until more than a month after the earliest date of that post I could find. Though UserWay knew its failure of compliance by April 2021 given that it responded to the failure. Not enough to assert UserWay lied, but enough to make me wonder what UserWay considers a gray area.
After a Conversation with the COO: 21 March 2022
While at CSUNATC this year (2022), the Chief Operating Officer (COO) of UserWay intercepted me as I entered the opening night mixer, before I got to talk to anyone else. He wanted 10 minutes of my time, which I begrudgingly granted him even though it was not a public conversation.
I understand he spent much of CSUN asking for one-on-one conversations with known practitioners, something I later counseled people against accepting (also in real life) when I found out.
UserWay’s COO said he watched my a11yNYC talk about overlays and had read this post. He said the issues I raised had since been fixed but my material did not reflect that. So I went back through this post and the talk to see what warranted an update.
The following anchor links will take you to the appropriate part of this post:
- Read the update about UserWay’s lawsuit claims;
- Read the update about UserWay’s failures on a client site;
- Read the update about UserWay stealing my content.
My other findings — reputation, privacy guarantees, IAAP membership, criticisms, failures under WCAG, buying reviews, false advertising, legal claims — all still hold true.
UserWay Tries to Cash in on W3C Brand: 19 June 2022
On 26 May 2022 at 10:58am ET, the Chief Operating Office of UserWay proposed an overlay W3C Community Group. For a W3C Community Group to be formed, anyone with a W3C account can propose it and then five (5) people must show their support by activating a button. The W3C acts as nothing more than a host for an email discussion list.
The same day the Community Group was proposed, the UserWay COO, The UserWay CEO, two UserWay Advisors, and an Accessibility Evangelist at AudioEye all signaled their support and the group was formed at 7:56pm ET on 26 May 2022. This was announced on Twitter via an automated tweet from the W3C. At launch, the group had only two of the people who signaled their support, plus one other person, for a total of three (3) participants.
The automated tweet directed users to the seemingly auto-generated Call for Participation in Overlay Community Group, asking for people to join. On 27 May 2022 at 7:38pm ET I left the following comment on the Call for Participation:
I think it is crucial that a W3C Community Group is founded with accurate information, especially when soliciting participation.
Some notes on the premise of overlays as stated in this announcement:
The “snippet” is a script reference to a library of code that comprises a good deal more functionality than a snippet would imply. That script reference is then loaded by the end user’s browser and applied to the web page by the end user’s browser.
> Typically, this single line of additional code functions to enable, on each page load, additional content processing, delivered through the overlay provider’s servers, before the content is delivered to the end user.
Again, this “single line” is a reference to a URL where a much larger library of code lives (even if it has been minimized to have no line feeds).
The “content processing” is not done on page load. It is performed after the script has been fetched, parsed, and applied to the web site DOM by the end user’s browser.
The statement that this happens “before the content is delivered to the end user” is inaccurate since the page (content) must load at least enough for the end user’s browser to fetch the overlay provider’s library of code and then the end user’s browser must parse the DOM, which is after the content has been delivered. Then the end user’s browser can apply the overlay provider’s script.
> …informed by sober analysis of what technological innovation at the edge can offer.
I am not sure this is “the edge” given the sentence that precedes this one which reads “…this routing paradigm is by no means unique to accessibility applications…”
Finally, in the interests of full disclosure, this is the provided list of names of those who supported creation of this community group but with their overlay vendor affiliations added:
Lionel Wolberger (UserWay COO), Jeff Kline (UserWay Advisor), Janina Sajka (UserWay Advisor), Allon Mason (UserWay CEO), Alisa Smith (Accessibility Evangelist at AudioEye).
My comment was never approved. In fact, not only was my comment never approved but when I checked on 28 May 2022 at 5:04pm ET, I discovered the Call for Participation had been deleted completely. No new Call for Participation has since been generated.
As of this writing (19 June 2022), the Overlay Community Group has five (5) members, only two (2) of them from the original supporting people. It has no public email in its archives and has published nothing else publicly. It has sat for three weeks with no public activity of any kind, and has made no further call for participants.
My opinion is that this Community Group was never meant for genuine use. It seems more likely to me that UserWay is using the W3C brand to provide a veneer of credibility to its own ongoing marketing efforts. As evidence I point to the UserWay-heavy supporters, the lack of activity, the removal of the call for participants, and the failure to approve my comment after claming the group was intended to foster “sober analysis”.
UserWay Renames the Community Group: 23 June 2022
I got a tip that the Overlay Community Group has changed its name. If you go to w3.org/community/overlay you will be redirected to w3.org/community/a11yedge. The new name is the Accessibility at the Edge Community Group. At least 20% of its members did not know (and that person is not an impartial observer).
Same members, same lack of activity. Didn’t even fix the snipet typo in the intro.