Is Accessia — Audit RGAA / WCAG safe to install?

What data it declares

The developer declares that it collects these kinds of data:

• Personally identifiable information such as name, address, email address or age
• Authentication information such as passwords, credentials or PIN codes
• User activity such as clicks, scrolling, keystrokes or network monitoring
• Website content such as text, images or links on the pages you open

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

When you add it, Chrome asks you to allow it to:

• Read and change all your data on all websites
• Read your browsing history

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

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

Reaches your browsing data or every site

• Attach to pages the way developer tools do debugger
• See the address and title of every tab you have open tabs

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
• Open a panel beside the page sidePanel
• Store data in your browser storage

Pages it runs its code on

It runs its own code on every page you open: the manifest declares a content script for all sites.

• <all_urls> every site
• https://www.accessia.app/* only www.accessia.app
• https://accessia.app/* only accessia.app

A content script is code the extension injects into pages matching these patterns. On those pages it can read and change what you see, whether or not a host permission is listed above.

How usual this is for its category

In Make Chrome Yours · Accessibility, 23% of extensions ask for access to every site. This one: Access to every site.

The typical extension there declares 2 browser permissions; this one declares 6 browser permissions.

• Attach to pages the way developer tools do (debugger): 1% of extensions in this category ask for it.
• See the address and title of every tab you have open (tabs): 23% of extensions in this category ask for it.

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

5 users

• Last updated in the store 1 day ago, on 2026-10-30.
• We have seen 6 new versions in the last 90 days.

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

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.

1. 2026-10-31Asked for more permissions (7, was 6) (changed: browser permissions, optional permissions)
2. 2026-10-30Changed where it works (changed: optional permissions)
3. 2026-10-27Changed where it works (changed: pages it runs its code on)

Versions we have seen

1. 2026-10-31Version 0.2.1 · Asked for more permissions (7, was 6) (changed: browser permissions, optional permissions)
2. 2026-10-30Version 0.2.0 · Changed where it works (changed: optional permissions)
3. 2026-10-28Version 0.1.8
4. 2026-10-27Version 0.1.6 · Changed where it works (changed: pages it runs its code on)
5. 2026-10-23Version 0.1.2
6. 2026-10-10Version 0.1.1

Who publishes it

Accessia. This listing has been in the store since 2026-10-08 and was last updated on 2026-10-30.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

1. RGAA Audit No site access · 3 permissions 11 users ★ 5.0
2. AccessLens — WCAG Accessibility Auditor No site access · 3 permissions 3 users (last published figure)
3. pour - Accessibility Checker & WCAG Audit Runs its code on every site · 3 permissions 9k users

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 Accessia — Audit RGAA / WCAG access?

Every site you visit. This extension can read and change the content of any page you open. It declares 6 browser permissions.

What data does Accessia — Audit RGAA / WCAG collect?

The developer declares that it collects these kinds of data: Personally identifiable information, Authentication information, User activity, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

Has Accessia — Audit RGAA / WCAG asked for more permissions over time?

Its permissions changed 3 times while we watched, most recently on 2026-10-31.

Does Accessia — Audit RGAA / WCAG publish a privacy policy?

Yes, the store listing links to a privacy policy.