
This falls under guideline #9 :ĭevelopers and their plugins must not do anything illegal, dishonest, or Not a new infraction, and it has been explicitly forbidden in theĭirectory’s guidelines for years. Suspicious behaviors indicating that the reviews were likely fake and removed Members of 's Plugin team investigated and found a pattern of Reviews for accessiBe after the investigative work of Joe Dolson. In February 2021, removed dozens of fake Highlighting the runWaveProcess function. Figure 5: Screenshot of "accessiBe will get you sued" by Adrian Roselli showing Its exact mechanism of operation cannot be determined but is assumed to be the codeĬreated to interfere with the WAVE tool.
Wave browser extension code#
The underlying code for that function has been Triggers a function called runWaveProcess. The code forĪccessiBe appears to have instances where it detects the use of WAVE, which Validate the claim of accessiBe's interference with WAVE. The existence of pieces of code within the accessiBe product that appear to

Sued" by Adrian Roselli, documenting accessiBe interfering with WAVEĪccessibility Consultant Adrian Roselli further documented With WAVE's detection and of and accuracy identifying accessibility andĬompliance issues" Figure4: Screenshot from "accessiBe will get you Temporarily modify content when WAVE is activated resulting in interference "The 3 rd party accessiBe integration on this page may The makers of WAVE needed to add a message within their product which states Use the accessiBe product including anecdotal evidence that sites containingĪccessiBe would report no errors when obvious errors are present. Users of the WAVE tool had reported noticing anomalous behavior on sites which In 2020, Adrian Roselli documented apparent attempts byĪccessiBe to interfere with WAVE as well. Uses the UserWay product, after activating the WAVE testing tool. With the effectiveness and accuracy of another productĪ result of #2) convincing the UserWay customer that they do not need to takeĪny further action on accessibility efforts.įigure 3: The "after" state of a page which When, in its non-interfering behavior it isn't The UserWay customer into believing that the UserWay product is fixing things On a black background, as shown in the figure below. Injects code onto the page that causes the white-on-blue text to be white text When the WAVE tool is activated, UserWay alters the page inĪ way that interferes with WAVE's ability to accurately test the page. Figure 2: The "before" state of a web page This color combination fails WCAG standards for color contrast Pay particularĪttention to the white text on blue background on the right side of the center The page before the WAVE testing tool has been activated. The first picture shows the default state of The example images below show the homepage from on November 4,Ģ021, at 4:09 PM US Central Time. "Use the Wave Browser Extension…", UserWay interferes with that toolĪs well. Screenshot taken OctoberĪlthough the above message makes the recommendation to Figure 1: Screenshot demonstrating UserWay's interference with WAVE. Wording of this message is likely intended to erode customer's trust in the Generated by UserWay, not WAVE, and is false. The Wave online scanner is unable to accurately parse theĪccessibility remediations on this page".

Interferes with WAVE, displaying a brightly colored message declaring

Submitted and display the results of its automated assessment.Īs shown in the image example below, overly product UserWay

Upon doing so, the WAVE service will assess the code on the URL that was Using the web service, a user needs only to enter the URL Market and is available via a few delivery methods including a browser WAVE,īy WebAIM, is one of the most popular web accessibility testing tools in the Anti-competitive behavior exhibited by overlay vendors Interference with web accessibility testing toolsĪmong the most notable anti-competitive behaviors exhibitedīy overlays is their interference with the operation of testing tools.
