Media
1 item
Description
Web accessibility checker for WCAG 2.2: color contrast, alt text, headings, focus order, color blindness simulator, audit reports. 🔍 Web Accessibility Checker for WCAG 2.0, 2.1 and 2.2 Web Accessibility Checker turns any browser tab into an audit workstation. Open the side panel, scan the page, read every failure grouped by rule, with the measured value shown against the required limit, why it matters, how to fix it, plus a code example you can paste straight into your editor. Under the hood this web accessibility checker runs axe-core 4.13 plus an own rule layer for the WCAG 2.2 criteria most tools still skip: target size, focus not obscured, accessible authentication, text spacing, reflow. Most people install a web accessibility checker to answer one question before a release: what will fail, and where exactly. That answer arrives in about two seconds, on the page you are already looking at, without a build step or a hosted crawler waiting in a queue. ✅ What every scan covers ➤ Contrast for normal text, large text, non-text elements ➤ Alt text, decorative images, images described somewhere else ➤ Heading structure, landmarks, page language, document title ➤ Form labels, link text, tables, captions, video alternatives ➤ Tab order, focus indicators, keyboard traps, target size 📐 Standards it speaks A bare pass or fail helps nobody. A result is only useful when it names the rule you will be judged against, so every finding here carries its success criterion, level, version, reading as a WCAG conformance record rather than a pile of warnings. 1. WCAG 2.0, 2.1, 2.2 across level A, AA, AAA 2. EN 301 549 plus the European Accessibility Act in Europe 3. Section 508, ADA Title III, AODA in North America 4. BITV 2.0 in Germany, RGAA in France, equivalents elsewhere 🎨 Contrast measured two ways Pick two colors with the eyedropper, edit them live, watch the WCAG ratio next to the APCA Lc value. The contrast ratio calculator returns a verdict for normal text, large text, non-text elements at once, so a level AA answer sits one glance from a stricter AAA answer. APCA contrast is the newer method explored for WCAG 3.0. 🕶 Vision simulations on the live page 1️⃣ Eight color vision types, protanopia through achromatopsia 2️⃣ Low vision, cataract, glaucoma rendered over the real layout 3️⃣ A reading difficulty mode for text refusing to hold still The color blindness simulator runs on the page itself, never on a screenshot, so hover states, charts, video posters are all included in what you review. 🧭 Find each problem without reading the DOM - Locate presses a docket onto the failing element with its criterion - Heading maps plus landmark maps draw real structure over the layout - Focus order is numbered along the path a keyboard actually takes - Alt text appears beside each image, decorative ones included 📄 Deliverables an audit actually ends in Testing is half the job. Everything below exports from one scan, so the accessibility report you hand over matches the tab you tested, down to the last measurement. 📊 Branded HTML report printing straight to PDF 🧾 CSV plus JSON for tickets, boards, pipelines ✍ Draft statement about the state of your site 📋 VPAT style table for procurement teams Run it as an accessibility statement generator on Monday, then as the source for an accessibility conformance report on Friday. One scan, two deliverables, zero retyped measurements. 🌐 Web accessibility testing beyond a single page Scan same origin pages in one crawl, keep the history, diff two runs to see what broke, what got fixed. One off checks become accessibility regression testing before every release, which is what teams really want from an accessibility monitoring tool. ✦ Why teams keep this panel pinned ✦ Findings show the measured value, never a vague severity word ✦ Guidance explains the fix, not only the name of the rule ✦ Everything exports, so nobody rebuilds the report by hand ✦ The panel itself passes the audit it performs, at WCAG 2.2 AA 🔒 Private by design Zero page content, zero URLs, zero results ever sent anywhere. A scanner that never phones home can go where hosted ones cannot: staging servers, intranets, pre release builds. No account, no signup, no network. 👥 Built for the whole team Developers clearing issues before code review, designers checking color decisions, QA running online accessibility testing inside a sprint, agencies producing client documents, editors deciding whether a page is publishable. Any rendered page qualifies. ⚡ Three steps, start to deliverable → Press Alt+Shift+A and let the web accessibility check run → Work the list, locate each element, fix, rescan the page → Export the report, statement or conformance table you need ⚖ Honest about the limits Automated tools reach roughly a third of WCAG success criteria, so every score, report, draft here says exactly that on its face. Clear the machine checkable failures fast, then spend your hours on judgment calls no automated tool can make. An aid to an audit, never a certificate. ⌨ Start in ten seconds Pin the extension, open any page, press Alt+Shift+A. No build step, no onboarding, no trial timer. Fifteen interface languages ship with the panel.