Skip to main content

Accessibility Overlays: Why UserWay & Eye-Able Fall Short

Information about the article

Portrait of Dmitry Dugarev

Author: Dmitry Dugarev

Consultant for digital accessibility & IT compliance

Last updated on:

You want a quick way to make your website comply with the BFSG. The BFSG (Barrierefreiheitsstärkungsgesetz) is Germany's implementation of the European Accessibility Act (EAA). In your search, you have come across Eye-Able, UserWay or accessiBe. These tools are called accessibility overlays or accessibility widgets. They add a small icon to the edge of your website [1]. They are meant to improve accessibility through software [2].

It sounds like a one-click solution. Sadly, it does not live up to its promise.

I test websites by hand. In this article, I show you what overlays can and cannot do. You will learn what Eye-Able and UserWay offer and cost, what German regulators say and what to do instead.

In short
  • An overlay does not necessarily make an inaccessible website accessible [2].
  • Overlays can get in the way of people who use screen readers [3]. They also bring privacy risks [4].
  • Germany's federal and state monitoring bodies say that public-sector websites must be accessible without an overlay [2]. In my view, the same applies to businesses.
  • Eye-Able itself says that a widget alone does not deliver full WCAG conformance [1].

What are accessibility overlays and widgets?​

Think of an overlay as a coat of paint. It sits on top of your website, and the code underneath stays the same. Vendors include accessiBe, UserWay (see Figure 1.1), Eye-Able, EqualWeb and DIGIaccess.

Screenshot of the UserWay website with the accessibility widget open on the right.
A typical overlay widget of the kind many vendors use (source: screenshot of the UserWay website, November 9, 2025).

Technically, an overlay is usually a snippet of third-party JavaScript. You add it to your site. Many municipalities and companies use such tools. In 2024, for example, most of Eye-Able's customers were municipalities or ministries [5].

Overlays promise two things:

  1. An on-page widget: Users get a menu where they can change the font size, adjust contrast or stop animations, for example.
  2. Automatic "repairs": The script looks for barriers in your site's code. Then it tries to fix them right in the browser.

The features sound impressive. Typical ones include:

  • Adjusting font size, line spacing and letter spacing.
  • Several contrast modes, for example inverted contrast.
  • Stopping animations and videos.
  • AI-generated alt text for images.
  • Highlighting links and clickable elements.

The problem: these automatic fixes are error-prone. Many features do not go far enough. I show you why in the next sections.

UserWay review: widget, WordPress plugin and pricing​

UserWay has been part of Level Access since March 2024 [6]. Level Access describes UserWay as technology for automatic fixes on live websites [6].

There is a WordPress plugin called "Accessibility by UserWay". It has over 80,000 active installations [7]. The plugin is free, but you need a UserWay account [7]. According to the plugin description, the widget changes elements it identifies as non-compliant [7]. I compare other plugins in WordPress accessibility plugins compared.

The premium plans cost extra. On its pricing page, UserWay lists US490peryearfortheProplan,forexample[@userway−pricing−2026].Itcoversupto100,000pageviewspermonth.TheProPlusplancostsUS490 per year for the Pro plan, for example [@userway-pricing-2026]. It covers up to 100,000 page views per month. The Pro Plus plan costs US1,190 per year [8].

Eye-Able review: features, pricing and track record​

Eye-Able was founded in Würzburg, Germany. The company behind the brand is Web Inclusion GmbH [9]. According to the German business paper Handelsblatt, Eye-Able had more than 2,000 customers in November 2024 [5]. In September 2026, the company reports over 5,000 customers in more than ten countries [9].

What Eye-Able offers​

Eye-Able is more than a widget. On its website, the vendor lists these products, among others [10]:

  • Assist: a widget with over 25 assistive features, for example read-aloud, contrast modes and color filters [1].
  • Report: automatic testing and reporting. It scans the whole website, usually weekly. The results are sorted by WCAG levels A, AA and AAA [11].
  • Access: AI suggestions for 26 error types, for example missing alt text or labels. You approve each suggestion. A script then applies it to the live page with JavaScript [12].
  • Eye-Able Ally: an AI assistant meant to help you remove barriers [10]. Do not confuse it with the Elementor plugin that used to be called Ally [13].
  • Other modules and services: accessible PDFs, plain language, translation, an accessibility statement generator, guided and manual testing, user testing and consulting [10].

You install Assist with a code snippet or with a plugin for WordPress or Shopware [1].

What Eye-Able says about conformance​

Eye-Able is more candid about this than some vendors. Its Assist page states that a widget does not offer 100 percent WCAG conformance [1]. Eye-Able calls Access an interim solution. The long-term goal, it says, is a clean code base [12].

This matches my experience. A script that masks errors in the browser is no substitute for fixing the code. The barrier stays in the source code. If the script fails, the barrier is back.

Eye-Able describes Assist as fully GDPR-compliant [1]. Still, check this with your data protection officer before you add a third-party script.

What Eye-Able costs​

Eye-Able does not publish its prices [14]. You get a quote on request. A freedom-of-information request made through the German platform FragDenStaat gives a rough idea. In February 2024, the City of Cologne replied that "Eye-Able Assist for one domain" costs €1,299.90 net per year [15]. Your price may differ.

A widget is an ongoing license. You pay for an audit and the fixes once, for your website as it stands. Our manual basic audit costs €490 net for the homepage and a few subpages. After the audit, you get a fixed price for the fixes. For the full picture of what to budget, read the article What an accessible website costs.

Eye-Able reviews: what independent tests and authorities say​

In 2025, the German agency dkd compared six testing tools, including Eye-Able [16]. The test covered the scanning features, not the widget. dkd praises the error analysis and the adjustments for users. It also sees the server location in Germany as a plus [16].

But dkd says it is hard to make meaningful use of the free version [16]. Site-wide analyses are only available if you request them through a form [16].

On OMR Reviews, a German software review platform, users rate Eye-Able 4.7 out of 5 stars on average (39 reviews, as of September 2026) [14]. I treat such ratings with caution. They show how happy the buyers are. They do not show whether screen reader users can use your site.

Germany's federal and state monitoring bodies do not name any vendor in their assessment [2]. Their statements apply to overlay tools in general. Read more in the section on German authorities.

Eye-Able alternative: fix the barriers in the code​

Looking for an alternative to Eye-Able? Then another widget is not the answer. The alternative is to fix the barriers in the code. This also works in WordPress, with your existing theme or page builder. The guide Accessible WordPress without a relaunch shows how.

Eye-Able itself also offers manual testing, user testing and consulting [10]. My criticism is aimed at the widget and the script-based fixes.

  1. The free BFSG check shows you the errors that a tool can find automatically.
  2. A manual audit tests all 55 criteria of WCAG 2.2 Level A and AA.
  3. Then you fix the barriers yourself, or have them fixed in your existing theme.

Here is a WordPress example. In my audits, I often find contact forms where screen readers do not read out the error messages. The cause lies in the form plugin or the theme. A widget does not change the source code. The message has to be connected to the field in the code, for example with aria-describedby. The page on accessible forms shows how.

The full process is in the step-by-step plan below.

Why accessibility overlays fall short: code, users, privacy​

Overlays cause problems in practice and in law. These problems fall into three areas.

The biggest problem: an overlay does not necessarily make an inaccessible website accessible [2].

  • No cure-all: Overlays do not fix structural errors in your website's code. If keyboard navigation is broken at its core, an overlay cannot reliably patch it. You have to change the source code itself, for example with our Semanti­cality™ Plugin.
  • Unreliable AI: An AI recognizes an image and writes "man at desk" as alt text. It does not understand the context. If the image shows a quote by Steve Jobs, the quote is the correct alt text.
  • Modern frameworks: Sites built with React, Angular or Vue change content with JavaScript. The overlay cannot repair content that changes this way [3].
  • Blind spots: The overlay script does not fix content in PDFs, SVGs, canvas graphics or media files [3]. Some vendors sell separate modules for this. Eye-Able, for example, has one for PDFs [10].

WCAG conformance means your site meets all criteria of the level. A tool that covers only some of them, and does so unreliably, is not enough.

What international experts say​

Many experts outside Germany reject overlays too.

More than 1,000 accessibility professionals have signed the "Overlay Fact Sheet" [3]. They include:

  • Contributors to and editors of the WCAG, ARIA and HTML specifications.
  • Accessibility specialists from Google, Microsoft and Apple.
  • Contributors to screen readers like JAWS and NVDA, and disability rights lawyers.

In 2020, Steve Faulkner wrote about such add-on solutions on the blog of The Paciello Group (now TPGi) [22], [23]:

"…these add-on solutions not only fail to help, they can increase the very risk (and cost) an organization is trying to avoid…"

Steve Faulkner, "Bolt-on Accessibility – 5 Gears in Reverse", 2020

What do German authorities say about overlays?​

On March 12, 2025, the Committee for Accessible Information Technology under § 5 BITV 2.0 discussed overlay tools [2]. BITV 2.0 is the German ordinance on accessible IT for public bodies. The discussion was based on the joint assessment of the federal and state monitoring bodies. Both texts were published together. Below, I refer to both as "the monitoring bodies".

The assessment in summary

Public bodies keep trying to meet their obligations with overlay tools. The committee views this with concern. A temporary display layer added by software after the fact does not meet the legal requirements.

Public-sector websites are only accessible if they meet the requirements of Directive (EU) 2016/2102 even without overlay tools [2].

The monitoring bodies even warn of a "deterioration of accessibility". The reason: overlays and users' assistive technologies can interfere with each other [2].

The assessment applies directly to public bodies under Directive (EU) 2016/2102 [2], [24]. It does not mention the BFSG. But its reasoning is technical: the overlay does not change the code. That is why I think it applies to businesses under the BFSG as well.

A look at the US: lawsuits despite overlays​

In the US, the legal basis is the ADA (Americans with Disabilities Act) [25]. There have already been many lawsuits over website accessibility.

As early as March 2020, attorney Richard Hunt listed five lawsuits against companies that used a widget or overlay [26].

The US Federal Trade Commission (FTC) stepped in too. accessiBe had claimed that its plug-in accessWidget makes any website WCAG-compliant [27]. The FTC alleged that this claim was false, misleading or unsubstantiated. In April 2025, it approved a settlement: accessiBe pays US$1 million. The company may now only make such claims if it can back them up [27].

And in Germany?

In 2024, there were more than 4,000 lawsuits in the US over inaccessible websites [28]. According to UsableNet, a quarter of them explicitly named widgets as a barrier [28]. In Germany, the BFSG has applied since June 28, 2025 [29]. The first BFSG warning letters followed soon after [30]. In German, these are called Abmahnungen: formal cease-and-desist letters.

The MLBF in Magdeburg monitors the BFSG across Germany [31]. MLBF stands for Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen, the market surveillance authority of the German states for accessibility. In March 2026, it reported handling more than 500 complaints [32]. The article on how an official inspection works explains the process. The fines you risk are covered in the article on BFSG risks and fines.

Here are the five cases from Richard Hunt's list. The defects listed are taken from the complaints. They are the plaintiffs' allegations, not court rulings. Reports by Equidox and Kris Rivenburgh name the overlay that ran on each site [33], [34].

Case: Walters v. Venum Training World, Inc. [35] Overlay according to Equidox: UserWay [33]

According to Equidox, the site ran the UserWay overlay. The lawsuit was filed anyway. Among other things, the plaintiff alleged these defects [33]:

  • The screen reader did not reliably announce the overlay.
  • There was a keyboard trap. You could tab into an element, but not out of it.
  • Required fields were not accessible.
  • Discount notices were not announced.
  • Screen reader users could not choose a product variant or add anything to the cart.

The case ended in September 2020 with a joint stipulation of dismissal [35].

These cases come from the US and involve a different legal system. But I expect authorities and courts in Germany to take a similar view. The monitoring bodies have already said so for public bodies: only what is accessible without an overlay counts as accessible [2].

The alternative: your step-by-step plan​

If overlays are not the answer, what is?

Only one approach lasts: treat accessibility as a process. Instead of a coat of paint added afterwards, you need a solid foundation in the code.

The monitoring bodies recommend planning for full accessibility from the concept stage of a website [2].

Here is how to go about it:

Get an honest picture (accessibility audit)​

You can only solve problems you know about. First, you need to know where you stand. How many barriers does your website have, and how serious are they?

  • First overview: Our free BFSG check tests 20 of the 55 criteria at least partly automatically. The other 35 can only be tested by hand, because a tool cannot judge what content means.
  • In-depth analysis: In the manual audit, I test all 55 criteria of WCAG 2.2 Level A and AA. I test with a screen reader, a keyboard and zoom. For every barrier, you get its location and a solution.
  • Example: The sample BFSG audit report shows what such a report looks like.

Check the exceptions (action plan)​

With the audit report in hand, you can now check your legal obligations. You do not have to fix every barrier right away, or at all, if the effort is extremely high.

Build skills in your team (training)​

Accessibility is not a project you tick off. It is an ongoing practice. Your team must understand why and how to write accessible code.

  • Lay the foundations: Developers and editors need training. Then they get semantic HTML, good alt text, form labels and keyboard access right from the start.
  • For reference: Our BFSG checklist gives your team the checkpoints for new pages and content.

Fix the barriers (remediation)​

Now it is time to get to work. Based on your plan, you fix the errors in the source code.

You now have a clear roadmap. Hand it to your development team or let us fix the barriers. Then document the result in an accessibility statement.

Decision tree: do you need an accessibility overlay?​

According to the monitoring bodies, there is only one narrow use case [2]. This decision tree helps you:

Text description of the decision tree

Do I need an accessibility overlay on my website?

First: does my website already meet WCAG AA?

If not: An overlay is not a solution. Instead, fix the barriers directly in the source code [2].

If yes: Do I want to offer additional AAA features, for example better visual adjustments or larger text spacing?

If not: The website is accessible enough. An overlay is not needed.

If yes: Is the overlay tool itself fully accessible? Can users switch it off? Does it work smoothly with screen readers and the keyboard?

If this is not certain, or if the tool creates barriers, do not use it [2].

If the tool is proven to be accessible and compatible, you can consider it as an add-on for convenience features [2].

StepDecisionResult
Website does not meet WCAGDo not use an overlayFix the errors in code
Website meets WCAG, no extra features neededOverlay not requiredDone
Website meets WCAG, overlay plannedOnly use it if it is accessible, can be switched off and has no conflictsOptional

How to test a widget yourself​

Do you already have a widget on your site? Then test it in four steps:

  1. Switch the widget off. Navigate the page using only the Tab key. Note where you get stuck.
  2. Switch the widget on and repeat the test. If you get stuck in the same places, the widget does not fix them.
  3. Start a screen reader, for example NVDA. Open the widget menu with the keyboard only.
  4. Check whether you can switch the widget off completely.

The monitoring bodies require overlay tools themselves to be fully accessible and to have an off switch [2]. If your widget fails step 3 or 4, it does not meet this requirement.

When overlays (might) help

The monitoring bodies concede that overlays "may well be used" for Level AAA criteria [2]. This matters for public bodies. § 3(4) BITV 2.0 requires the highest possible level of accessibility for central navigation and entry pages [40].

So if your site already fully meets Level AA, an overlay can be an option. This applies to additional Level AAA convenience features, for example criterion 1.4.8 "Visual Presentation" [2], [41]. The condition: the overlay itself meets all criteria and creates no new barriers.

My advice: put your budget into code, not a widget​

An overlay that solves every problem with one line of code is a tempting idea. But overlays do not reliably meet accessibility requirements [2].

An overlay masks errors. It does not fix them. In the worst case, it creates new barriers [2]. The monitoring bodies say that an overlay does not release you from the duty to make your website accessible [2]. In the US, a quarter of the lawsuits in 2024 explicitly named widgets as a barrier [28].

So do not invest your budget in software that only masks problems. Invest it in sound planning and accessible code. Tools like the Semanti­cality™ Plugin make this work easier. That is how you make your digital services accessible to everyone for the long term.

Frequently asked questions (FAQ)​

Does Eye-Able make my website BFSG-compliant?​

The widget alone does not. Eye-Able itself states that a widget does not offer 100 percent WCAG conformance [1]. For public bodies, the monitoring bodies say that a website must be accessible without an overlay [2]. I have not found a statement by the MLBF on this for the BFSG. But the technical reasoning applies just the same. You have to fix the barriers in the code.

How much does Eye-Able cost?​

Eye-Able does not publish its prices [14]. In February 2024, the City of Cologne stated €1,299.90 net per year for "Eye-Able Assist for one domain" [15]. Your quote may differ.

Do accessibility overlays work if the vendor promises 100% compliance?​

Be careful with such promises. The US Federal Trade Commission (FTC) alleged that such a claim by accessiBe was false or unsubstantiated. In the settlement, accessiBe paid US$1 million [27]. For public bodies, the monitoring bodies say that a temporary software fix does not meet the legal requirements [2].

Can I use an overlay as a stopgap until my site is rebuilt?​

That is risky and gives you no legal certainty. In the US, a quarter of the lawsuits in 2024 explicitly named widgets as a barrier [28]. The monitoring bodies warn that overlays can make accessibility worse [2]. Always focus on fixing the code.

Isn't an overlay better than nothing?​

Not necessarily. Users usually already have zoom and contrast in their operating system or browser [3]. On top of that, an overlay often makes the site less accessible for people who use assistive technology [2].


Disclaimer​

This article has been researched carefully and is for general information only. It is not legal advice and cannot replace individual advice from a lawyer who knows your specific situation.

Information on products, prices and company figures comes from the sources cited, as of September 2026. It may have changed since.

There is no guarantee that the information is correct, complete or up to date. Any action you take based on this information is at your own risk.


​

  1. Web Inclusion GmbH (Eye-Able), “Eye-Able Assist: Barrierefreiheits-Widget für bessere Inklusion.” 2026. [Online]. Available: https://eye-able.com/de/assist-assistenzsoftware ⤴
  2. Überwachungsstelle des Bundes für Barrierefreiheit von Informationstechnik (BFIT), “Gemeinsame Einschätzung der Überwachungsstellen des Bundes und der Länder für die Barrierefreiheit von Informationstechnik zum Einsatz von Overlay-Tools.” Mar. 2025. [Online]. Available: https://www.bfit-bund.de/DE/Publikation/einschaetzung-overlaytools.html ⤴
  3. “Overlay Fact Sheet.” 2021. [Online]. Available: https://overlayfactsheet.com/en/ ⤴
  4. AccessiCart, “Accessibility Overlays Create Info Privacy Concerns.” Oct. 19, 2022. [Online]. Available: https://accessicart.com/accessibility-overlays-create-info-privacy-concerns/ ⤴
  5. F. Kolf, “E-Commerce: Eye-Able bringt Onlinehandel durch Barrierefreiheit mehr Umsatz.” Nov. 19, 2024. [Online]. Available: https://www.handelsblatt.com/unternehmen/handel-konsumgueter/e-commerce-eye-able-bringt-onlinehandel-durch-barrierefreiheit-mehr-umsatz/100087561.html ⤴
  6. Level Access, “Level Access Completes Acquisition of UserWay, Signaling the Next Evolution of Digital Accessibility.” Mar. 20, 2024. [Online]. Available: https://www.levelaccess.com/news/level-access-completes-acquisition-of-userway-signaling-the-next-evolution-of-digital-accessibility/ ⤴
  7. UserWay, “Accessibility by UserWay.” 2025. [Online]. Available: https://wordpress.org/plugins/userway-accessibility-widget/ ⤴
  8. UserWay, “UserWay Pricing.” 2026. [Online]. Available: https://userway.org/pricing/ ⤴
  9. Web Inclusion GmbH (Eye-Able), “Eye-Able stärkt Führungsteam für nächste internationale Wachstumsphase: Oliver Berchtold wird CEO.” Sept. 01, 2026. [Online]. Available: https://www.presseportal.ch/de/pm/100103945/100941928 ⤴
  10. Web Inclusion GmbH (Eye-Able), “Digitale Barrierefreiheit für deine Website | Eye-Able.” 2026. [Online]. Available: https://eye-able.com/de/ ⤴
  11. Web Inclusion GmbH (Eye-Able), “Eye-Able Report: Kontrollzentrum für digitale Barrierefreiheit.” 2026. [Online]. Available: https://eye-able.com/de/barrierefreiheits-report ⤴
  12. Web Inclusion GmbH (Eye-Able), “Eye-Able Access: Barrierefreiheit automatisch mit KI.” 2026. [Online]. Available: https://eye-able.com/de/barrierefreiheit-mit-ki-optimieren ⤴
  13. Elementor, “Web Accessibility (formally known as Ally) – WCAG Scanning, Guided Fixes, Usability Widget – WordPress-Plugin.” 2026. [Online]. Available: https://wordpress.org/plugins/pojo-accessibility/ ⤴
  14. OMR Reviews, “Eye-Able pricing 2026.” 2026. [Online]. Available: https://omr.com/en/reviews/product/eye-able/pricing ⤴
  15. Stadt Köln, Amt der Oberbürgermeisterin, “Die jährlichen Kosten für Eye-Able auf der Website der Stadt Köln.” Feb. 20, 2024. [Online]. Available: https://fragdenstaat.de/anfrage/die-jaehrlichen-kosten-fuer-eye-able-auf-der-website-der-stadt-koeln/ ⤴
  16. K. Ivanova and T. Bieber, “Tools für Web-Barrierefreiheit: 6 Lösungen im Praxis-Check.” Apr. 01, 2025. [Online]. Available: https://www.dkd.de/de/blog/tools-fuer-web-barrierefreiheit-6-loesungen-im-praxis-check/ ⤴
  17. WebAIM, “Survey of Web Accessibility Practitioners #3 Results.” Jan. 26, 2021. [Online]. Available: https://webaim.org/projects/practitionersurvey3/ ⤴
  18. Europäisches Parlament und Rat der Europäischen Union, “Art. 9 DSGVO: Verarbeitung besonderer Kategorien personenbezogener Daten.” 2016. [Online]. Available: https://dsgvo-gesetz.de/art-9-dsgvo/ ⤴
  19. Gerichtshof der Europäischen Union, “Urteil des Gerichtshofs (Große Kammer) vom 16. Juli 2020. Data Protection Commissioner gegen Facebook Ireland Limited, Maximillian Schrems.” July 16, 2020. [Online]. Available: https://eur-lex.europa.eu/legal-content/DE/TXT/?uri=CELEX:62018CJ0311 ⤴
  20. Europäische Kommission, “EU-US data transfers: How personal data transferred between the EU and US is protected.” 2023. [Online]. Available: https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/eu-us-data-transfers_en ⤴
  21. Gerichtshof der Europäischen Union, “Data Protection: the General Court dismisses an action for annulment of the new framework for the transfer of personal data between the European Union and the United States.” Sept. 03, 2025. [Online]. Available: https://curia.europa.eu/site/upload/docs/application/pdf/2025-09/cp250106en.pdf ⤴
  22. S. Faulkner, “Bolt-on Accessibility – 5 gears in reverse.” May 13, 2020. [Online]. Available: https://www.tpgi.com/bolt-on-accessibility-5-gears-in-reverse/ ⤴
  23. L. L. Carlson, “Web Design Update, Volume 18, Issue 46.” May 13, 2020. [Online]. Available: https://www.d.umn.edu/ lcarlson/newsletter/vol_18_201907-202006/46.txt ⤴
  24. Das Europäische Parlament und der Rat, “Richtlinie (EU) 2016/2102 des Europäischen Parlaments und des Rates vom 26. Oktober 2016 über den barrierefreien Zugang zu den Websites und mobilen Anwendungen öffentlicher Stellen.” 2016. [Online]. Available: https://eur-lex.europa.eu/legal-content/DE/TXT/?uri=CELEX:32016L2102 ⤴
  25. U.S. Department of Justice, “Americans with Disabilities Act of 1990, as amended.” 2008. [Online]. Available: https://www.ada.gov/pubs/adastatute08.htm ⤴
  26. R. Hunt, “Is there a silver bullet for ADA website accessibility? Sorry, but the answer is no.” Mar. 2020. [Online]. Available: https://accessdefense.com/?p=5378 ⤴
  27. Federal Trade Commission, “FTC Approves Final Order Requiring accessiBe to Pay $1 Million.” Apr. 22, 2025. [Online]. Available: https://www.ftc.gov/news-events/news/press-releases/2025/04/ftc-approves-final-order-requiring-accessibe-pay-1-million ⤴
  28. Bundesministerium der Justiz und für Verbraucherschutz, “Gesetz zur Umsetzung der Richtlinie (EU) 2019/882 des Europäischen Parlaments und des Rates über die Barrierefreiheitsanforderungen für Produkte und Dienstleistungen (Barrierefreiheitsstärkungsgesetz – BFSG).” 2023. [Online]. Available: https://www.gesetze-im-internet.de/bfsg/ ⤴
  29. Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF), “Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen.” 2026. [Online]. Available: https://www.mlbf-barrierefrei.de/ ⤴
  30. K. Kramer, “‘Sanktionen sind für uns stets das letzte Mittel’. Interview mit Robert Richard, MLBF.” Mar. 10, 2026. [Online]. Available: https://www.boersenblatt.net/news/verlage-news/sanktionen-sind-fuer-uns-stets-das-letzte-mittel-414695 ⤴
  31. N. Overdorff, “Accessibility Overlays: Automation That’s Too Good to be True.” Oct. 07, 2020. [Online]. Available: https://equidox.co/blog/accessibility-overlays-automation-thats-too-good-to-be-true/ ⤴
  32. K. Rivenburgh, “Williams v. VaporDNA.” July 24, 2020. [Online]. Available: https://krisrivenburgh.com/williams-v-vapordna/ ⤴
  33. “Walters v. Venum Training World, Inc.” 2020. [Online]. Available: https://www.pacermonitor.com/public/case/33122298/Walters_v_Venum_Training_World,_Inc ⤴
  34. “Williams v. VaporDNA.” 2020. [Online]. Available: https://www.pacermonitor.com/public/case/32945835/Williams_v_Vapordna ⤴
  35. “Fredericka Nellon v. Agri Beef Co.” 2020. [Online]. Available: https://www.pacermonitor.com/public/case/33157169/Nellon_v_Agri_Beef_Co_dba_Snake_River_Farms ⤴
  36. “Ariza v. Carmen Sol FL, LLC.” 2020. [Online]. Available: https://www.pacermonitor.com/public/case/33125558/Ariza_v_Carmen_Sol_Fl,_LLC ⤴
  37. “Cruz v. Rockwell Time, Inc.” 2020. [Online]. Available: https://www.pacermonitor.com/public/case/32694992/Cruz_v_Rockwell_Time_Inc ⤴
  38. “Barrierefreie-Informationstechnik-Verordnung (BITV 2.0).” Verordnung zur Schaffung barrierefreier Informationstechnik nach dem Behindertengleichstellungsgesetz, 2011. Accessed: Nov. 06, 2025. [Online]. Available: https://www.gesetze-im-internet.de/bitv_2_0/ ⤴
  39. W3C, “Web Content Accessibility Guidelines (WCAG) 2.1.” 2021. [Online]. Available: https://www.w3.org/TR/WCAG21/ ⤴

About the author

Portrait of Dmitry Dugarev

Best regards,

Dmitry Dugarev

Founder of Barrierenlos℠. I test websites by hand and fix the barriers on WordPress websites – without a relaunch.