Audit WCAG 2.2 extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: inopdchddpobeoikmeljdlelipbckgnp
Permissions (4)
- Execute scripts in pages
- Manage downloads
Related extensions
Accessibility AnalyzerMake Chrome Yours
WCAG Documentation CreatorDeveloper
Accessibility Compliance Auditor — WCAG & EAADeveloper
AccessAudit Pro - WCAG & ADA Accessibility AuditorMake Chrome Yours
Site Audit Lab: Website Accessibility Checker & SEO Audit (WCAG 2.2)Developer
WCAGBrief: WCAG 2.2 & ADA Accessibility AuditDeveloper
Frequently asked questions
Is Audit WCAG 2.2 safe to use?
Our latest automated scan rates the Chrome listing of Audit WCAG 2.2 at 79/100 (some risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does Audit WCAG 2.2 require?
Audit WCAG 2.2 requests 4 permissions. The most significant: Execute scripts in pages, Manage downloads. See the full breakdown in the security report.
Who develops Audit WCAG 2.2?
Audit WCAG 2.2 is published by lucas.grimont.06. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 1.0
- Current listed version
- 1.0
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 16 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.