WICK-AG-Lens is a Chrome DevTools extension designed to show developers and testers where potential accessibility issues appear on a page. Its listing advertises colored issue markers, filters, element locating and copyable findings—but those automated checks are an aid to evaluation, not proof that a site conforms to accessibility standards.
What WICK-AG-Lens does
The Chrome Web Store lists WICK-AG-Lens: Accessibility Inspector as a Chrome DevTools extension. The developer describes it as a visual inspection aid: instead of relying only on a list of findings, a person can use on-page markers and an element locator to move from a reported condition to the relevant part of the interface.
As an Amazon Associate I earn from qualifying purchases.
According to the listing, the extension offers colored markers, filters by criterion and conformance level for WCAG 2.0, 2.1 and 2.2, explanations with selectors, and a button to copy findings for bug reports. These are vendor-described features; they were not independently tested for this article. Chrome Web Store listing
How its advertised inspection workflow works
- Open the page in Chrome DevTools. The extension is distributed as a DevTools accessibility inspector through the Chrome Web Store.
- Run an inspection and review the markers. The developer says the extension overlays potential findings on the page, helping connect a reported condition with a visible element.
- Narrow the results. The listing says findings can be filtered by criterion and WCAG conformance level.
- Inspect the element and its explanation. The advertised locator and selector information are intended to help identify where to investigate in the page or code.
- Copy findings into a bug report. The listing describes a copy button for sharing findings with a development or QA workflow. A copied finding still needs a person to verify the behavior and describe the user impact.
What the 40 advertised audits cover
In an October 6, 2026 launch article, developer Sebastian Clavijo Suero describes 40 independent audits divided between violation-oriented checks and informative or structural checks. Examples named include missing alternative text, form controls without labels, empty buttons, focus-order mapping, landmarks, language declarations and contrast checks. The count and examples are the developer’s descriptions, not an independent measurement of coverage or accuracy. Developer launch article
The developer also says the extension can inspect open Shadow DOM and same-origin iframe content, but cannot reach closed shadow roots or cross-origin frames. That scope description is likewise a vendor claim, not an independently verified capability. A scan should therefore not be assumed to cover every component or embedded frame on a site.
Why an automated finding is not an accessibility verdict
W3C’s Web Accessibility Initiative cautions that “Web accessibility evaluation tools can not determine accessibility, they can only assist in doing so.” Some checks require manual intervention, tools may be inaccurate, and human judgment is needed. WAI’s evaluation overview is equally direct: “Knowledgeable human evaluation is required to determine if a site is accessible.” W3C: Selecting Web Accessibility Evaluation Tools W3C: Evaluating Web Accessibility Overview
That distinction matters in both directions: a flagged element may need contextual review, and an empty result does not establish that users can successfully navigate or understand the page. A visual marker can help a developer reach a likely target; interpreting its purpose, testing interaction and assistive-technology experience, and determining overall conformance require more than automated checks. WAI describes WCAG-EM as an approach for evaluating conformance.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Privacy and availability claims
The Chrome Web Store privacy section says the extension handles “Web history” and “User activity.” The listing also describes the extension as operating locally in DevTools, without data transmission or telemetry. These are developer disclosures; the extension’s code and network behavior were not independently examined, so the statements should not be treated as a separately confirmed privacy guarantee. Chrome Web Store listing
The developer’s launch article calls the extension free and open source and points to a source blueprint on GitHub. The reviewed sources do not establish its current license, repository maintenance status or future pricing. The Chrome Web Store listing showed version 2.1.0, an update date of October 5, 2026, a 4.51 MiB download size and five users when reviewed; these are time-sensitive listing details, not evidence of quality or adoption. Developer launch article
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Who may find it useful
WICK-AG-Lens is aimed at developers and testers who want an on-page way to investigate possible accessibility findings during development or QA. Its advertised markers and copyable results may fit a workflow where someone identifies an issue, verifies it, and writes a clear ticket—for example, describing what happens when a user encounters a particular button. The sources do not establish measured accuracy, time savings or improved outcomes, so treat those as possible workflow benefits rather than demonstrated results.
For broader evaluation, WAI recommends considering a tool’s purpose, the product being evaluated, scope and standards. WICK-AG-Lens can be one aid in that process; it is not a substitute for knowledgeable human evaluation or a certification of conformance.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
