
Accessibility overlays bring promises of accessible sites in one line of code, but experiences from users tell us the opposite. At a previous A11yNYC Meetup, Adrian Roselli looks at the guarantees, the marketing efforts, the code efforts, and lived experiences of users.
Resources
- Adrian’s A11yNYC presentation page
- Visit the Overlay Fact Sheet and consider signing.
- Overlay False Claims
- Tips for Getting Started
- Tool to generate an accessibility statement
Highlights
- Examples of overlay problems
- AccessiBe marketing claims
- Lawsuits against overlays
- Privacy risk
- Organizations respond to overlay complaints
- The right way to create an accessible website
- Q&A with Adrian
Transcript: Overlays Underwhelm - Adrian Roselli
ADRIAN ROSELLI: The title of this talk is Overlays Underwhelm. I had the title before I had the content, though, so it might not be the best fit. We'll find out. Basically I'm going to try to shoehorn this over/under theme over the talk throughout. Good news is I'm protecting from hearing your groans thanks to the magic of one-way audio.
A little bit of context. This is my ego slide just to give you the barest indication that I have some experience. I want my arguments to stand on their merit, but I understand you might want to know my technical jobs, my background, et cetera. Business, books, sites, articles, all that stuff I've just thrown some examples of that on the site.
You can look me up at Adrianroselli.com. I'm also on twitter @aardrian. Now onto the meat of the talk. Overlays underwhelm. What we should do is consider what gaps accessibility overlays are filling. The web has lots of accessibility bits already built in, and there are more tools and features available to developers and users than there ever have been before.
After all, as Tim Berners-Lee said, the B4520 gets you there faster and bypasses that nasty roundabout outside Swindon. I might have gotten that quote wrong, this is his actual quote. I'm obligated to put his quote into an accessibility talk when it's a broad talk because otherwise I would not hit the cliche. You can get your own quotes from -- well, I'll put a link to it in my slides when they get posted.
So let's first ask what is an overlay? An overlay is essentially a tool that provides some sort of accessibility or usability feature that may or may not be built into the underlying site. Sometimes it replicates a native feature, sometimes it offers some other kind of affordance. Often it does the work in the end user's browser, so it's relying on each user's computer to replicate the same work as every other user's computer. It doesn't happen once, it happens once per visitor. Overlays can also be referred to as widgets, toolbars, add ons. There are a few different things people have called them throughout the years.
There were many tools that predated some of the native features that we may be used to now or that were created to fill some gaps in technology, including assistive technology. Some techniques and standards may not have been defined. or even well supported when these tools were created. The risk is that these tools required users to learn them anew for every site with features that would not carry across sites.
Here is an early example. Browsealoud. It converts the text on a page to speech. And if I can get the cursor there, there's some audio that will be playing in a moment.
COMPUTER: GB flag,Change Region, Products, for Education, Read and Write, Equatio, Speechstream, Wri-Q, Fluency Tutor, OrbitNote, For Work, Read…
ADRIAN ROSELLI: I'm going to stop it there, as you can see Browsealoud offers no context for what is being read, whether it's visible or not. It was never meant to replicate what screen readers can do. Instead it's more similar to a feature you can find built into browsers today, such as Edges's Immersive Reader. Browsealoud also required a third-party embedded script and back in 2013 this was briefly hacked.
In the slides I'll post afterwards I'll have some links to that information as well. Now, some widgets made an effort to replicate features already in browsers and in operating systems. These range from tech sizing to contrast and motion control and even zooming and magnification. In this video, this is a text sizing widget on the New York Times site, which shows how they can go wrong. No longer available on the New York Times site, so you won't see this in action anymore, but assuming you can find it behind a gear icon, the control only appeared when you were at the top of the page, and the widget only resized article content, not headlines, not navigation, nothing else. And since the article content was outside the view port, it also made it near impossible to compare the sizing options. It also didn't
retain the size, as you navigated throughout the site, so when you returned to the site or even if you tried to print the site, those new sizes that you set wouldn't be kept. Better implementations have shown users how to change their browser or operating systems instead, so don't make it a one-off, but educate them so they can carry that forward. However, this kind of feature could be a useful stop gap feature to gauge if users regularly scale text and then instead of adding the feature, remove it and make the text bigger if that's what you find users are doing. So that's just an approach of how you can get some benefit out of one of these.
Now, some widgets exist because there is no native equivalent or the needs aren't well represented in what exists. Success to those widgets really come down to how well they perform. Now, this is Hand Talk. It's another add on. What this does is load an animated avatar to sign the content of a page, in this case American Sign Language. Like the text to speech example, it presents the contents of the page in sign language but still can't offer the same context of what other content. I didn't explore how many sign languages it supports.
To its credit, though, it's not fingerspelling everything it encounters, but I would leave that to the audience to judge its value. Now, the current list of overlay vendors is not necessarily filling these gaps. They are capitalizing on a general lack of understanding of people in needs, and they are focusing on selling quick fixes to businesses instead. These companies, this is not necessarily all of them, but it includes accessiBe, AccessiWay, Adally, AudioaEye. There are vendors that white label some of these products, so you might find another vendor who has white labeled and is reselling the UserWay widget, for example.
Overlays tend to overstate their abilities. In technical reviews, they consistently underperform. Automated accessibility testing tools aren't perfect, we already know this, but we can use them to get a sense of whether or not an overlay has improved WCAG compliance of a page. I used an automated checker to compare the number of errors before and after an overlay was activated, and the page typically had more detectable WCAG errors after. And when I say typically, I mean, in every case. There might be exceptions, I just haven't found them yet.
The examples that follow are at this point about a year old, a little more than a year old. I opted not to retest them because I don't want to provide free testing to these vendors. That's not my thing. Besides, these vendors were claiming WCAG compliance when I tested them back then, so if they were lying then, there's no reason to assume that they would stop lying now.
So this is Deque's axe browser plug in, which prides itself on no false positives. It might be a little more lenient than a human tester would be. After running an overlay on the vendor's own page, in this case accessiBe, the number of errors detected bye axe tripled, from four to 12. TPGI's ARC toolkit plug in is less likely to be lenient. When testing the same page, on the accessiBe site, the number of detectibe errors doubled, jumping from 19 to 38 when the overlay was activated. ARC also jumped from 164 warnings to 193.
These don't represent clear WCAG violations, but they are flags to let you know that you need to do some manual testing, that there might be some issues. WebAIM's WAVE checker browser plug in returned no violations without the overlay active. After the overlay was activated, a single contrast violation appeared. I've written about my concern that accessiBe was spoofing WAVE, though I cannot weigh in with the code to confirm this, I think some other people have. WAVE used to display a message, specifically it read, quote, the third-party accessiBe integration on this page may temporarily modify content when WAVE is activated, resulting in interference with WAVE's detection of, and accuracy identifying accessibility and compliance issues, end quote.
That tells me that they also suspected something was up. So, we know automated accessibility testing tools only identify about 30% of potential issues, and that number shifts based on complexity and other factors. That is a known thing. That 30% number acknowledges that much of WCAG itself requires human judgment based on context. Overlay vendors tend to claim they can address the other 70%. It's a bold claim and surprisingly easy to disprove.
Here, the stop animations button that appears in this overlay fails to stop the auto-playing background video. That flag just keeps waving. To compound the confusion, the button only changes only its accessible name when pressed, it does not use 'aria-pressed' to indicate it has been activated, or any other programmatic change of state. Now, you'll see that the video has stopped playing, that's simply because I did not record any longer of the video than this for my slides.
Here is me trying the keyboard navigation feature of one vendor. Since it's unaddressed, navigation violates 1.4.13 'content on hover' and 2.4.7 'focus visible'. Even after I activate the feature, focus styles are still missing. Eventually a new box appears with different links. I was tabbing so much already, I tabbed past the item that displayed the instructions.
Oops. But to drive home the point, it dropped me into a de facto keyboard trap in its cookie popup. You could hear me pressing that key harder and harder out of anger. Now, it's not just the claim fixes that don't work, the tools themselves present barriers.
The button in that background video was just one example, the one we saw a few moments ago that would not stop the flag. In other cases, screen reader users have noted that they hear sounds from the overlay with no explanation of what they mean. The tools don't even prevent their own customer from making new WCAG violations. So, here the overlay is very tall, so what I did is I captured four screenfuls for what you're seeing is, if you stack those all on top, that would be the total scrolling area of the overlay. It shows how the contrast of the controls is so light, it is hard to determine if one is active, or what degree it is active.
Some of the text and icons are illegible. The language selector, which is the one over in the far right, commits the internationalization sin of using flags to choose language, and provides no alt attributes for those flags. The overlay itself violates at least three WCAG success criteria from just a few seconds of examination. Part of this is because the configuration options for the overlay customer do not prevent them from choosing colors that clearly fail contrast checks. Here, the white on the -- the white text on the sort of pink/white background has a contrast ratio of 1.2 to 1. To restate this, the overlay vendor's product allowed its customer to do this.
Now, here in this video, we can see that the browser's default focus ring is active. But then, the browser alert prompting the user to activate the overlay appears, right there. If the user declines, that focus ring is somehow removed from the page. The only clue that focus is changing, is in the browser status bar, or when the page jumps to scroll down.
Here, I navigate an overlay vendor's site and as the new page is loading, it grays itself, as if a modal will appear, and then some hidden audio starts to play.
COMPUTER: Hi, I'm Ronnie from accessiBe, the number one fully automated ADA and WCAG compliant solution. In this video, you will learn how accessiBe's AI power technology makees any website accessible in compliance with the WCAG2.1, the ADA...
ADRIAN ROSELLI: You could see that I clicked on the gray area in the hopes that maybe thehidden video modal would disappear. I scrolled around looking for player controls. I also hit the escape key with no luck. This page itself is a good example of a 1.4.2 'audio control' violation, and a 1.2.1 'audio only and video only prerecorded' violation. This is the Accessus.ai site.
Now here is an overlay button trigger with an icon of a paper boat, or a hat, really not sure, and the visible text customized accessibility. The browser dev tools indicate it has focus, so I tabbed over to it, I know it has focus. In the dev tools, I explicitly set focus so I could confirm the focus styles. But the browser dev tools show me, not in this screen shot, that there's an 'outline none important' that has been applied to that control, which means there's no visible style. So, right off the bat, there's a 2.4.7 'focus visible' failure.
The boat icon image has alt text. The alt text does not describe the image, instead it reads 'manage display settings'. It feels like a 1.1.1 'non-text content' failure to me, because it's not describing the image, but that also makes the full accessible name of the button, quote, manage display settings customized accessibility, end quote. It's a pretty long name. And that's -- we can only see the customized accessibility part of that.
But, to compound it, the button has an ARIA label, and that ARIA label reads 'facility: adapt display' and that overrides the text that we can see, which immediately causes a 2.5.3 'label and name' failure. So, the button that triggers the accessibility features for the Abilities.com site has three WCAG failures on its own, even before you've tried to use it. It is genuinely introducing WCAG risk at this point. Now, I have some more examples that are pulled from accessiBe. The reason accessiBe is more prominent in this talk, and my tweets and my posts, is because it seems to be the loudest at using its venture funding to promote its product. It took a year for accessiBe to update the terms on their site after I flagged the things I'm going to show you. I don't know
if these terms are written into their contracts. I haven't seen their contracts. The contracts might even retain the language that I'm going to walk through in a moment. Either way, other vendors have made similar compliance promises, and they have similarly mooted those promises in their own terms and contracts.
So, from the accessiBe home page: Does accessiBe protect me from lawsuits? Absolutely. accessiBe turns inaccessible websites into WCAg and ADA compliant websites. But not only that, it provides you with a litigation support package, in case you need to prove your ADA website compliance, and guides you through the process. Again, that's the accessiBe home page.
Another from the accessiBe home page: Does accessiBe cover all accessibility requirements? Yes! AccessiBe covers the WCAG web content accessibility guidelines version 2.1 at the AA level success criteria, and in certain areas even level AAA. This is a step beyond what legislation requires.
Now, that differed from the accessiBe terms and conditions page, here captured in December 2020, which I understand has been a bit of time ago now. In this section, accessiBe is defining the word 'Standard' to mean specifically, WCAG 2.1 level AA success criteria . From the accessiBe terms, the functionality of the accessiBe systems requires that the licensee website in which they're embedded, the website's based solely on HTML files and tags, and that the source code be written according to the standard, which we've defined a moment ago, of the Worldwide Web Consortium, W3C, without any errors or validation warning in W3C's troubleshooting inspections. Please note that licensee changes to such website may impact the functionality of the service. By way of example accessiBe systems do not support other components such as Canvas, Flash or SVG.
Essentially what accessiBe's terms here state is that its customer websites must already meet the standard, which they've already defined as WCAG 2.1 AA, with no errors or even warnings from the validator, so clean pass all around. Essentially, your site must be WCAG compliant to conform to accessiBe's terms. For a product guaranteeing to make your site WCAG compliant, accessiBe goes on to exempt pdfs, Flash, SVG files, and even any mobile devices not running Android 8 or iOS 10. Not older versions prior to those, and not later versions released after that, but exclusively Android 8 or iOS 10. Again, these terms have changed since I captured this, but this was the marketing angle, this was the message, these were the terms that they used for years.
Now, to remind us that accessiBe is not the only one making these claims, here is a bit from UserWay's site. It claims it will make your site ADA compliant, which is not really a thing. It brags about the lack of lawsuits mentioning it. I don't have a Lexis/Nexis account, so I haven't been able to absolutely confirm that. It claims to have a strong reputation in the disability community, it asserts its privacy chops, and it claims it is securer by not tracking people with disabilities.
Now, UserWay might be right about lawsuits mentioning its products, again don't have a Lexis/Nexis subscription, but I can say that many lawsuits do not name the overlay vendor. Many of these vendors claim they can protect their customers from lawsuits, though. AccessiBe's CEO has even written, and I want to quote this: "Never, not once, had encountered a company that got sued because of accessiBe." That's a statement from accessiBe's CEO, "Never encountered a company that got sued because of accessiBe".
Yet in 2020, over 250 companies were sued after investing in overlays. The lawsuit pace picked up to almost one per day by the end of that year. Here are just five examples, at least one of which mentions the vendor by name. Four of them mention accessiBe despite its CEO's very public claims. I'm going to list them all off: Kolesar v. Bylt, LLC; Thomas Klaus and Robert Jahoda v Upright Technologies; Blair Douglass v. Masterbuilt Manufacturing, LLC; Murphy v. Eyebobs, LLC; Fischler et al v. Dorai Homes; and finally, LightHouse et al. v. ADP.
The Lighthouse v. ADP case goes further, and explicitly states that, "For the purpose of this Agreement, overlay solutions such as those currently provided by companies such as AudioEye and AccessiBe will not suffice to achieve Accessibility." I think that's a very clear statement. The Eyebobs case concluded in a settlement where Eyebobs got to perform an audit, adopt a policy statement, implement an accessibility strategy, and provide accessibility training.
It doesn't really sound like the overlay protected Eyebobs in that scenario. Wired magazine wrote an article titled 'This Company Tapped AI for Its Website and Landed in Court'. I'm going to read an excerpt from the article. "In a statement, AccessiBe s head of marketing, Gil Magen, said the company had analyzed Eyebobs website and found it complied with accessibility standards. AccessiBe offers clients assistance with litigation but Eyebobs declined, the statement said. In its own statement, Eyebobs said AccessiBe failed to respond to requests for meetings with its lawyers. Eyebobs is no longer working with AccessiBe nor will we in the future, the statement said."
Now, sometimes a company relies on the overlay as its only way to become accessible to its customers. But what happens when the script will not load? Malwarebytes has blocked them, adblockers have blocked them, Firefox enhanced privacy protection blocks them, but what if the script has an error, or if the network chunks? Is your site still, air quote, protected just because the network hiccupped? Are the users helped in that scenario?
This screen shot of the browser dev tools shows that the overlay script has not loaded. Worse, the accessibility link in the footer is a div. It's a div with a tab index and a button roll, but it does nothing when it's been clicked. If you tap it, click it with a mouse, try and tab to it, whatever, it does nothing because the overlay script that's supposed to replace it with a real control doesn't fire. So now that site isn't, quote, protected.
On the Malwarebytes forum a user wanted to know if the script from after an overlay vendor was a tracker or not? The Malwarebytes staff acknowledged that the overlay script had indeed been blocked. Until the user asked the question, Malwarebytes had blocked it for all its customers for potentially years. They didn't give a timeline for how long they'd been blocking it.
The claims of no privacy risk are spurious at best. A data protection risk assessment, or a DPIA, is a process to help you identify and minimize the data protection risk of a project. You must do a DPIA for processing information that is likely to result in a high risk to individuals, but these vendors do not provide one. As a result any claimed GDPR compliance is in question, automatically.
Remember that these overlay scripts must parse all of the content on the page, essentially reading everything that you are surfing. Some of them keep your settings from site to site by setting tracking cookies. Now, here in a tweet, Leonie Watson demonstrates how cavalierly overlay vendors treat this compliance. Reading Leonie's tweet, "Hello @AccessiBe. I've asked you by DM and by phone for a copy of your Data Protection Impact Assessment (DPIA) and you have not responded. Since asking discretely has not worked, I am now asking openly for you to share your DPIA, since you claim GDPR conformance. Thank you." She asked this on April 1st, 2021. So, what, we're 11 months from when she asked. She still has not heard back. I'm not a lawyer, but this feels very much like a GDPR violation on the part of accessiBe.
The DSW Shoes website uses UsableNet s Assistive overlay. Though instead of an accessibility icon in the corner, which is what we've come to associate with most overlays, it uses the text "Enable Accessibility" in gray on gray located in the header of the site. If you block third-party cookies, you get the following browser alert when you try to activate it: "An embedded page at a40.usable net.com says your web browser privacy settings are preventing the accessibility mode to stay enabled. Try enabling third party cookies to ensure you receive accessible updates to the website." This presents a false choice between security and what may be a more accessible experience. Nowhere does the user have the opportunity to understand how those third-party cookies will be used, or what information will be shared. Essentially, a user has to disclose a disability or access need, with no indication
how that information will persist. It's also a reminder that these products don't make a site more accessible, instead these products make your computer try to make a site less broken. Overlay vendors will overpromise in their marketing, making claims about the utility and popularity while underdelivering on them. These vendors rely on a combination of fear, uncertainty and doubt. They know many website owners do not understand accessibility user laws. Even as users complain about the problems with these products, the vendors use astroturfing techniques to drown it out. This is an advertisement from one of the overlay vendors. It's a cartoon of a man at a computer happily explaining, "Finally my website is up!" Two men in suits suddenly appear next to him holding legal papers and say, "Not so fast!". Nice website but it's not accessible! You've been served". The website owner now crying, hands up in
the air, says "I'm broke now.. Why bother..." In the background the two men can be seen walking away carrying bags of money. Overlay vendors use fear of lawsuits to sell their product, not a desire to help users. This particular cartoon is careful to not show disabled people as the villains, but the implication is clear. The laws that protect disabled people will cost you money unless you pay for this vendor's help.
Now, one vendor cited that "silent majority" of users liked the overlay product, and as a result the complaints that appear online are only exceptions. Here Chancey Fleet tweets: "The founders of accessiBe are interpreting the complacency of nondisabled customers and the bone-deep fatigue of disabled users to mean that a "silent majority" -- their actual words -- is grateful for and enjoys accessiBe. Let's not be silent then". It was in reply to a tweet from Marco Salcissia: "Pretty much, as well as citing their silent majority of blind users who approve and "test" their product. I ran into so many issues just going through their example sites alone, I didn't want to give them a fully free audit of how much they were doing wrong."
In addition, these vendors have a history of astroturfing review sites, social media, and the web in general. The effort is to ensure only their message appears, and they have the money, the SEO chops, and the lack of integrity to pull it off. I have links to twitter spam, medium articles, paid promotion pieces at industry sites, questionable reviews on other platforms, even Wikipedia entries that were flagged by the moderator as spam. This image here shows a headline from WP Tavern, when one vendor had all the fake reviews for its WordPress plugin removed.
In addition to individual complaints there has been press coverage of these companies. Users with some standing in a disability community have spoken about overlay failures in general. Some users are so frustrated they share tips and tools to block overlays. One vendor has even threatened users with lawsuits. NBC news ran a story with the headline "Blind people, advocates slam company claiming to make websites ADA compliant". Vice also ran an article headlined "People With Disabilities Say This AI Tool Is Making the Web Worse for Them".
The Mosen at Large podcast devoted an entire podcast to the question of the value of overlays. Episode 105 asked: "The accessiBe controversy. Can AI make the web fully accessible in a few short years, or might it make matters worse?" A chunk of the follow-up episode was devoted to more frustrations from users. Other community podcasts have discussed these tools as well.
Some users are so frustrated they have written tools to block overlays. AccessiBegone gives instructions for blocking accessiBe. AccessiByeBye is a browser extension to disable overlays in the browser. One overlay company has opted to fight back. Last April, because we're not this April yet -- In April, FACIL iti s attorneys started sending letters demanding removal of any criticism.
I have a screenshot here of a letter to Koena that shows two tweets about FACIL iti. Koena declined to comply with the request and wrote about why. Another disabled user who I'm not naming here, but I have shared their plight on twitter, was subpoenaed to appear in court. FACIL iti asked for 5000 Euros in damages, 5500 Euros in fines, and in order to cease comments that may "FACIL iti solution". I can't think of a better way to say your products help disabled users than suing disabled people that say it does not. Great way to double down.
Overlay vendors also claim that organizations love them, but community and industry organizations have been clear that they do not. National Federation of the Blind, after accepting one as a sponsor for its annual event, went so far as to not only drop the sponsor, but to then issue a statement rebuking its very existence. This part of the statement stood out to me. "In particular, it is the opinion of the board that accessiBe scornfully dismisses the concerns blind people have about its products and its approach to accessibility. The nation's blind will not be placated, bullied, or bought off. Therefore the Board revoked accessiBe's sponsorship of the convention on June 22 2021."
The CSUN assistive technology conference briefly had an overlay on its site, and was met with such rapid and vocal anger that it was dropped immediately. It may very well have been implemented without anyone's knowledge based on this tweet which reads "the accessibility overlay has been removed. It was implemented without our approval. The conference does not endorse this product, and we apologize for the situation which has now been corrected."
The Olympic committee created the WeThe15 site in an effort to promote the Paralympics, but in doing so, it used an overlay. After responses from users and the disability community, the overlay was removed within a couple days. That same overlay is still on the main Olympics website, which may be a function of the vendor promoting it so heavily in its marketing materials. One of the WeThe15's tweets in response to all of this: "Thank you for alerting us about these issues. We're disappointed, too, that we've fallen short in this area. We've gathered together some new experts that are helping us to fix this. It would be great to have your support going forward to make the next iteration a complete success."
Many overlay vendors claim that detractors are really just frustrated competitors. It's a tactic to diminish all of the criticism and say it's just market competition. The overlay fact sheet kind of disproves that. Nearly 700 people have signed it so far. They represent web specification contributors, internal accessibility experts from companies in higher education, lawyers for the disabled, contributors to assistive technology, and end users with disabilities. I encourage you to visit the site at overlayfactsheet.com and read through the information and links. It identifies strengths and weaknesses of overlay widgets, and automated repair in general. It also touches on technical and privacy concerns.
In addition to the signatures there are statements from users. There is one professional organization for digital accessibility practitioners, one that I'm generally aware of, the International Association of Accessibility Professionals, IAAP. It is a division of G3ICT, the Global Initiative for Inclusive Information and Communication Technologies. It's weird having to say this out loud when I've only had to type it. Anyway, it allows membership for overlay vendors. Overlay vendors then brand their marketing materials with the IAAP logo, and overlay vendors use this for some veneer of credibility.
Some organizations display it on their website footer, UserWay and MaxAccess each do so using the weight of the accessibility professionals as a marketing boost. Others might get promotional consideration as AudioEye did when IAAP tweeted an AudioEye post, a post which if you read was arguably lifted fully directly from WC3 documents. There was finally some fallout, though. On January 17, IAAP promised a proactive response to that tweet and overlay membership. Even though I raised the concern in September, along with some others, the good news is that they were starting to act from some of that fallout. The organization produced a survey for members and nonmembers, and the results of that survey were posted this past Friday, February 25th. Of the 609 responses, 591, 97%, were not overlay vendors, not. That means there were still a bunch who were. 81% of
them, or 478 responses state that they do not compete with overlay vendors. 90% of the responses, or 549 responses say they have seen false claims by overlay vendors, and 86% or 533 responses believe IAAP should comment on marketing claims in general, and 90% believe IAAP should comment on overlay marketing claims specifically. As we have seen, overlays cannot make your site or your brand better overnight. 24 hours, nope. So, to wrap this talk up -- I'm paying attention to time, yay -- I want to cover some steps that you can undertake without overlays. See I've got under and the over?
Anyway, I really did shoehorn that theme in here. So this one is for folks who are actually building out there, in the trenches, making things, building sites and so on. Plan ahead. Hire a consultant who has some experience in this space. They can help you choose a vendor who prioritizes accessibility and write this into your contracts. They can also direct you to technology that have already been vetted, or maybe direct you away from ones that are terrible.
Some platforms have accessible features already. For example, WordPress offers 114 free accessibility ready themes, built with a baseline of compliance already in place. Add some free online resources when you create your content, and you may have all you need to get going. There is even a free tool to generate an accessibility statement for your site, provided by the very organization that sets accessibility standards, the W3C.
If you already have a site, you can use one of the many free automated accessibility checkers on the market. Assuming you aren't interested in getting into the browser's own tools that is, there is ARC, Axe, Lighthouse, WAVE, and Webhint. While they won't catch-all of the issues, maybe around that 30% mark, they will at least give you a sense where you stand. Where you have gaps, document them. Identify what's wrong, put together a plan and timeline to address them, and publish it on your site. Do that with an accessibility statement. As long as you honor the timelines you provide, you're the one who can choose what your ongoing budget will be to address them, even if it only comes out to $1,000 per year, or whatever's the going rate that an overlay vendor is pitching you.
If you're affected by overlays as a consumer, you can take some action. In the U.S., the Federal Trade Commission has rules that advertising must not be deceptive, must include evidence, and cannot be unfair. Overlayfalseclaims.com provides documented examples of overlay vendor false claims, along with consumer complaint resources for the United States, both federal and state, Canada, and New Zealand. You can use information there to file a false advertising complaint. It can also open a PR (pull request) submit information for filing complaints in other countries to the overlayfalseclaims.com site. So, i f you're in a country where you understand how you can do this, give some information to that site so that other people in your country can benefit from that.
Now, don't forget to claim your IAAP continuing accessibility education credits. They're preapproved. No vetting of this talk was needed. While you're claiming them though, remember this is your opportunity to ask IAAP to drop overlay vendors from its membership. Probably mention this talk as well. If they're going to be angry at somebody, it should be me. I'm not a member, so it's easier that way for everybody.
And that's it. That's the gist of the talk. I have a site, I have a page loaded on my site that has links to the material they've been referencing throughout, also has some of the videos and images. You can scan the QR code that's up on your screen now. I know that's weird, but people did it for the Super Bowl for some reason. Or you can go to -- read the URL, rosel.li/a11ynyc-overlays. That's rosel.li/a11ynyc-overlays. That's it. That's my talk.
Feel free to ask me questions or make fun of me or talk about my awesome beads.
THOMAS LOGAN: Well, I just want to say, thank you so much Adrian. You had tons of engagement happening in the chat while you gave the excellent presentation and I didn't mention it in the preamble of introducing Adrian, but I did a post that I linked into about the Eyebobs case. And when I looked at Adrian's website and saw, I guess I'll call them receipts, as we call them in today's language, the same way that your presentation today, I really appreciated how you showed the evidence of all these different things. There's probably an opportunity for some of these companies to say, Oh, we changed our terms from this to this. I really appreciated the screen shots, and seeing sort of the history of a lot of the things that have happened, even in this evolving narrative, and I'll just echo your
call to action that I think if we can tweet at IAAP, we can write the different business bureaus. It's really cool to see those options. And I'm going to now switch to -- is there anyone here that has a question? I'd like to turn it over to our audience for a question.
ADRIAN ROSELLI: So, at that URL I have videos, I have links to the things I was talking about, links to the sites, the accessiBe terms, for example. I link to the Wayback archived version of that page, so to your point, Thomas, I always have the receipts because I expect at some point I'm going to get a letter.
THOMAS LOGAN: Yeah.
ADRIAN ROSELLI: An official looking letter they I'm going to throw in the trash, maybe, or I'll panic. I don't know what I'll do, but I want to make sure that all of the claims that I'm making are backed up with data.
THOMAS LOGAN: Right.
ADRIAN ROSELLI: And I also want to remind people that the best predictor of future behavior is past behavior. If they were lying to you last year, why do you think they wouldn't be lying to you today? And I really think that's the really important takeaway from this. If you were a bad actor five years ago, two years ago, one year ago, you're probably still a bad actor, you've just learned from all this criticism different words you can use, and that's it.
THOMAS LOGAN: Totally agree. So we do have a question from Keith Laidlaw, he said overlay vendors are clearly marketing their products with non-technical risk averse managers in mind, for example, mine, who seem determined to add overlays to several eCommerce sites I manage. Do you have any tips or tactics that will help convince those same managers that these solutions are anything but?
ADRIAN ROSELLI: So that's tough, because I can present all this information and I feel I have an audience that, for the most part, is already on board with this, and this is sort of a validating talk. For individuals who don't have this background, though, it's important to understand why they chose the solution. Was it money, was it a timeline, was it a legal fear, or something? Ideally there's enough information now freely available, Overlay Fact Sheet, Overlay False Claims, my site, this talk, tons of other places, that you should be able to, first, ask why they chose it and come back to them with reasons why that probably wasn't a good choice anyway. If it's timelines, you can demonstrate nothing's been fixed. If it's a legal concern, you can point them to lawsuits. If it's cost, you
can walk through that slide where I talk about what you can do now to protect yourself from a legal perspective, and keep your costs down. But then you can also demonstrate -- if they genuinely think they're helping people -- you can demonstrate all the people in the community who are so viscerally angry at how their disability has been coopted as just a way to generate revenue for a well-funded venture startup.
THOMAS LOGAN: I also had a question on -- it was eye opening for me. I definitely missed the conversation on things like Malwarebytes or Ghostery flagging those, is that still ongoing, or is that more just like it could change any day? They get flagged?
ADRIAN ROSELLI: Malwarebytes had accessiBe flagged - I think it was accessiBe, I'd have to go back to the slides, it's all mush now -- had it flagged for a while until somebody raised it, it's probably not flagged anymore. But, for all we know, is if you have any internal policies or custom settings, those things could still be blocked, and there's no reason that they couldn't end up being blocked at some other point. And, as far as I know, Ghostery still blocks -- I hear people say Ghostery has blocked them for me, I just don't remember which one. I haven't put it in here until I can prove it myself.
THOMAS LOGAN: And maybe also related to that, you mentioned at the top of the talk a list of -- obviously it can never be comprehensive because these companies can start any day, but how did you get the ones that you listed? I mean, how do you become aware of someone's operating in this space?
ADRIAN ROSELLI: People tell me.
THOMAS LOGAN: Yeah.
ADRIAN ROSELLI: That's really all it is.
THOMAS LOGAN: Okay.
ADRIAN ROSELLI: I think I first wrote about terrible overlay solutions in 2015, and there was a bit of a dust up in the accessibility industry where people were talking about it, and then I just paid attention, then some of them started to appear in marketing e-mails, like, popular website that talks all about CSS sends me a marketing e-mail with all of its posts, and there's a big ad banner in the middle for one of these overlay vendors, and it's one I hadn't heard about before, or some client is saying, Oh, hey, somebody pitched me on this, can you look at this? But, for the most part, it's from people in the community who encountered one, had a terrible experience, and have flagged me, or other people who are n degrees of separation away and have told me.
THOMAS LOGAN: And it seems like just from the -- what you presented, but most of these company's probably have a general similar pitch that they're going to solve everything.
ADRIAN ROSELLI: Yeah.
THOMAS LOGAN: Add this thing.
ADRIAN ROSELLI: Yeah, so much so that I think AudioEye were suing accessiBe, or vice versa, for stealing technology and ideas.
THOMAS LOGAN: Oh, right.
ADRIAN ROSELLI: The point being that they're all up in each other's business, because they're all clawing at the same space.
THOMAS LOGAN: Uh-huh. So this is a different question, maybe tangential, but is it really safe to use an accessible word press theme. I've read that once you add a plugin, all bets are off.
ADRIAN ROSELLI: Yep. Absolutely true. But that's the case with anything out of the box that's accessible, as soon as you touch it, if you don't know what you are doing, there's a chance you could pull the wrong thing and the wheels could fall off. That's an unfortunate reality of all technology, anyway, anything could be broken pretty readily, but there are some good resources on how to write good content. Plugins are absolutely a risk at all times for everybody, but not just for accessibility, but also for security, and also for performance and so many other factors. I'd like to think a team is already doing some due diligence on plugins. If you've already got five things you're looking at, add accessibility in there as the sixth item. I mean, make it the first item, but the sixth thing you add,
as number one, of course, first. Not sixth, first. But to me, it's just part of that vetting process before you choose any technology anyway.
THOMAS LOGAN: Cool, and I want to highlight just a comment that I thought was very interesting, it was from one of the commenters saying, Hey, they're trying to work into their procurement language, don't procure accessibility overlays, and so I mentioned, hey, if you guys can share the language, I'm sure you'd be interested in that, too, but how can we get this to be more boilerplate for other organizations that care about it. We don't want the solution -- I mean, would you say -- like do you have any idea, is there any boilerplate language or something that people can use to --
ADRIAN ROSELLI: I think that that boilerplate language would be sort of industry-specific. So, for example, higher education has a completely -- not completely, has a significantly different procurement process from a multinational conglomerate bank, HSBC is going to do something different than an ivy league school, for example, and because of those differences in processes and vetting, and how they go about securing the funds etc, they're going to need to have their own language, but absolutely, look around, ask other people if they've got it. Take a look at the AudioEye ADP suit, pull that language out as an example. But once you get that, share it. That could be great information to share on the Overlay Fact Sheet. That's a pull request that I'd be happy to make if there's some good content. Carl doesn't yet hate me, so there's a reasonable chance he would merge it.
THOMAS LOGAN: That's wonderful. Yeah, and I think that's what we kind of were saying in the chat, like, if we can get stuff for people to reuse, we'll amplify it, we all want to do that. I mean, we -- at least I can say I -- share the same belief as Adrian, loved the presentation today. There's a comment from Billy Gregory.
ADRIAN ROSELLI: Hi Billy
THOMAS LOGAN: What's your take on conferences and podcasts giving these overlay companies a public platform to discuss their products? We've seen panels about overlays at events and notable accessibility professionals engage in conversation on podcasts. Helpful, or do you feel this unnecessarily legitimizes these companies?
ADRIAN ROSELLI: I think it unnecessarily legitimizes. I think that overlay vendors jump at these opportunities, because any platform is a platform that they'll take advantage of, but if they can have that platform with somebody who's got name or brand recognition, it lends credibility. It's sort of the weird stolen valor of their industry, as they're always going to try and attach their overlay product name to somebody who's got reputation. It's a two-pronged attack.
It's reputational harm to the person who brought them in and stood up for them, and it's also demonstrating to the industry in general that we can't trust those events anymore. There was a big reason that CSUN caught the flack, National Federation of the Blind, another one. They are trying too hard, and I think that the people who are actually affected by it recognize how bad that is.
THOMAS LOGAN: Okay. And then there's sort of a -- in this boilerplate comment, Lee says, I've been noticing the proliferation of overlays on eCommerce sites where I regularly shop. I've made a decision to not spend my money on these sites, but haven't contacted them about it. It would be great to have a boilerplate to use to contact these companies. Is there anything like that that exists currently for telling --
ADRIAN ROSELLI: I don't think so, and it's a great idea. I want to remind -- so it's a great idea, as is having language for procurement documents and for contracts, and for so many other places. I love the idea, I really do. I also want to qualify, I'm an independent accessibility consultant who can only make money when I'm billing people, and every time I'm out there taking swings at overlay vendors, that's revenue that -- that's food I'm not putting on my table. Overlay companies are proudly backed to the tune of 10s of millions of dollars. I can't fight them alone. I can't -- I just don't have the time or the resources to do it. But if people have good ideas like this, share them. Send them to me. I'll post them. Use the Overlay Fact Sheet. Overlay False Claims has driven outgrowth of some
of that, what action can we take, so yeah, maybe we can make something happen there. Thomas, lightning struck in your room or something?
THOMAS LOGAN: Yeah, so I think that's a good segue, though, when the lights go on and off. We're kind of nearing the end of the talk today, but I think a lot of what was discussed, the QR code we will also share into the meet up page, make sure everything's hyperlinked, we'll get this into the YouTube. Tons of awesome information today, and, again, thank you to Adrian. Hopefully this YouTube video, the recording of this presentation at Accessibility New York can also serve as a resource in your own actions to potentially combat an overlay solution in your organization and/or, you know, to help people gain education in this space. So, again, thank you so much, everyone, for being here, and especially to Adrian Roselli for the presentation today. Thank you as always and hope to see you at a future event.
ADRIAN ROSELLI: I'm going for king cake now.