Hey Product Hunt! I'm Jameson, solo dev at Royal Plugins. Origin: I built the WordPress version of Royal Access first (a visitor-facing accessibility toolbar). Clients kept asking the same question before installing it: "how do I even check if my site is accessible right now?" I'd send them Axe DevTools. They'd open it, see 47 violations in raw WCAG language, panic, and email me asking what any of it meant. Try sending a marketing director "Cells must have associated table headers (WCAG 1.3.1)" and watch their eyes glaze over. So I built the Chrome version for that exact moment. Click the icon on any page, get a 0–100 score with a color-coded ring, and read findings in plain English. No "WCAG 1.3.1." Instead: "This image is missing alt text. Screen readers will skip it. Add a short description of what's in the image." What it scans (8 categories): images, headings, color contrast (up to 200 elements), form labels, ARIA, landmarks, document structure, keyboard. WCAG 2.1 AA throughout. Two design rules I held to. activeTab permission only. Every other a11y extension I tested asked for full-URL access, meaning they can read every page you visit. I don't want that on my own browser, so I won't ship it. No account, no telemetry. Runs entirely in your browser. I never see what you scan. Free forever. Install: https://chromewebstore.google.co... Question: what's the worst "the developer report says it's fixed" moment you've had with accessibility?

Royal Access Chrome Extension

Forms, surveys, quizzes, payments — no add-on store

Forms, surveys, quizzes, payments — no add-on store