Is WCAG Accessibility Checker — Loupe safe to install?

What data it declares

The developer declares that it does not collect or use your data.

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing links to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

From the permissions it declares, Chrome shows no permission warning when you add it.

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

No site access is declared in the manifest, so it cannot read the pages you open on its own.

Worth knowing

• Run its own code on the pages it can access scripting

Routine for an extension

• Act on the current tab, but only after you click it activeTab
• Store data in your browser storage

What it may ask for later

Not granted when you add it: Chrome asks you the moment the extension requests one of these, and you can refuse. It may later ask for access to every site.

• *://*/* every site

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: No site access.

The typical extension there declares 3 browser permissions; this one declares 3 browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

26 users

• Last updated in the store 19 days ago, on 2026-10-14.
• We have seen 3 new versions in the last 90 days.

What the store shows

• Established publisher The store's badge for publishers with a good record and no history of violations.

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

The permissions this extension requests have not changed since we started watching it.

Versions we have seen

1. 2026-10-15Version 1.0.8
2. 2026-09-28Version 1.0.7
3. 2026-09-02Version 1.0.5

Who publishes it

Lucency, who publishes 4 listings we track. This listing has been in the store since 2026-06-18 and was last updated on 2026-10-14.

How to check or remove it in Chrome

1. Type chrome://extensions in the address bar and find the extension in the list.
2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
3. To uninstall it, choose Remove on the same page.

Questions people ask

What can WCAG Accessibility Checker — Loupe access?

No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 3 browser permissions.

What data does WCAG Accessibility Checker — Loupe collect?

The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

Has WCAG Accessibility Checker — Loupe asked for more permissions over time?

The permissions this extension requests have not changed since we started watching it.

Does WCAG Accessibility Checker — Loupe publish a privacy policy?

Yes, the store listing links to a privacy policy.