# Should I use an accessibility overlay?

DevFeed: [Should I use an accessibility overlay?](<https://devfeed.tech/articles/should-i-use-an-accessibility-overlay-9412.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/should-i-use-an-accessibility-overlay/>)

Author: The A

Published: 2021-03-08T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Accessibility](<https://devfeed.tech/topics/accessibility.md>), [digital accessibility](<https://devfeed.tech/topics/digital-accessibility.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [digital-accessibility](<https://devfeed.tech/tags/digital-accessibility.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [plugins](<https://devfeed.tech/tags/plugins.md>), [web](<https://devfeed.tech/tags/web.md>), [web-app](<https://devfeed.tech/tags/web-app.md>)

## AI overview

The article explains accessibility overlays and argues that permanent overlay plugins are technically, socially, and morally harmful. It distinguishes temporary overlays used as stopgap measures from persistent plugins, recommending that accessibility problems be fixed in the underlying website or web app code.

## Source excerpt

Due to their technical, social, and moral issues, The A11Y Project does not recommend using permanent overlay plugins. We view these kinds of products as actively harmful, and a step backwards for digital accessibility efforts. Background Accessibility overlays have become a controversial topic recently. Let's clarify what they are, and how they impact accessibility. An accessibility overlay is JavaScript that is written with the goal of helping to fix accessibility issues on a website or web app. Overlay code is applied after the website or web app is rendered by the browser, to transform it. Generally speaking, there are two types of accessibility overlays: Temporary bandage solutions, and More permanent plugins. Of the two, the more permanent plugins are incredibly problematic. Temporary bandage solutions Temporary bandage solutions have been around for awhile. Historically, they have been used by professional accessibility auditing companies as a stopgap measure. With the bandage approach, the overlay serves as a temporary measure. It is designed to be used to temporarily fix specific, critical accessibility issues until the underlying website or web app code can be updated. Think of these kinds of overlays like a bandage. Bandages are not intended to be left on permanently. They are removed after the injury they cover has healed. Bandage overlays usually have a process to signal when their code should be removed. This process is typically a negotiation between the accessibility auditors and the company who has the inaccessible experience. Permanent plugins Permanent plugins are more of a recent phenomenon. Unlike temporary bandage solutions, permanent plugins are designed to be a persistent presence on the inaccessible website or web app. Four examples of permanent plugins are accessiBe, AudioEye, FACIL'iti, and Max Access. There are numerous issues with permanent plugins. To build off the bandage metaphor, a permanent plugin left on a website or web app for to