AccessCheck: WCAG and Keyboard Accessibility Checker 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: odhbdcnojfgjbkbfajidablhibhhckgf
Permissions (5)
- Browser debugger access
- Execute scripts in pages
Related extensions
AccessCheck — Website Accessibility Checker, WCAG & ADA AuditProductivity
Accessibility Checker — WCAG, ADA & EAA ComplianceDeveloper
Contrast Check – WCAG Color TesterProductivity
Accessibility Checker: ADA, WCAG & Contrast – WCAGsafeMake Chrome Yours
Web Accessibility CheckerProductivity
AccessiSight – WCAG Accessibility CheckerDeveloper
Frequently asked questions
Is AccessCheck: WCAG and Keyboard Accessibility Checker safe to use?
Our latest automated scan rates the Chrome listing of AccessCheck: WCAG and Keyboard Accessibility Checker at 73/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 AccessCheck: WCAG and Keyboard Accessibility Checker require?
AccessCheck: WCAG and Keyboard Accessibility Checker requests 5 permissions. The most significant: Browser debugger access, Execute scripts in pages. See the full breakdown in the security report.
Who develops AccessCheck: WCAG and Keyboard Accessibility Checker?
AccessCheck: WCAG and Keyboard Accessibility Checker is published by marianacastrorc. 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.8.1
- Current listed version
- 1.8.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 critical and 8 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.