More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Lantern: WCAG 2.2 AA accessibility audit

    1

    Audits a live page, local dev server, Figma frame, screenshot or component code against WCAG 2.2 AA, and writes up every issue by severity with evidence and a fix you can make today.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Lantern: WCAG 2.2 AA accessibility audit

    Lantern: WCAG 2.2 AA accessibility audit

    Example session with this skill installed

    Can you do an accessibility audit of my local dev server at http://localhost:8765/broken.html? It's our shop homepage.

    • Read your context and instructions
    • Compiled the lantern
    • Generated the design tokens stylesheet

    This is a live local page, so we loaded it in Chromium, ran axe-core and then a keyboard and layout probe. The probe walked the tab order, checked the page at 320px wide and at 200% text size, and submitted the sign-up form empty. That shows us how the page behaves, but it can't tell us how it sounds in a real screen reader, so we've noted those gaps at the end.

    Accessibility audit: Moth & Wick shop homepage

    Standard: WCAG 2.2 Level AA ·

    Input: http://localhost:8765/broken.html (local dev server) ·

    Method: axe-core 4.14.0 + keyboard and layout probe (Chromium, 1280×900 and 320×800, form submitted empty) ·

    Date: 2026-10-28

    We checked the homepage with automated rules, a keyboard walk-through, a reflow and text-zoom check, and an empty submit of the sign-up form. Right now, keyboard users can't add anything to the basket. Once they tab into the chat box they can't get out again. Screen reader users meet a basket button with no name, and the members' offer text is too faint for many people to read.

    4 blockers, 8 serious, 5 moderate, 2 minor.

    Blocker

    1. The chat box traps keyboard focus

    • Criterion: 2.1.2 No Keyboard Trap (A)
    • Where: #chat-msg and #chat-send in the "Ask us anything" box (#chat)

    What's wrong: Once focus reaches the chat input, Tab only moves between #chat-msg and #chat-send, over and over. The probe saw the pair repeat for 7 more stops, with no dialog open and Esc doing nothing. The footer's "Privacy" link is never reached.

    Who it affects: Keyboard users, switch users and screen reader users. They're stuck on the page and can't reach anything after the chat.

    Fix: Find the script on the chat box that handles Tab or blur and sends focus back to the input or the Send button. Remove it so Tab moves on to the footer. If the chat is meant to be a dialog, make it a real modal (role="dialog", aria-modal="true") that closes with Esc and returns focus to the control that opened it.

    2. "Add to basket" can't be reached or used with a keyboard

    • Criterion: 2.1.1 Keyboard (A), and 4.1.2 Name, Role, Value (A)

    Where: body > main > div:nth-of-type(2) > div:nth-of-type(1) > div:nth-of-type(1) (Amber & Oak) and body > main > div:nth-of-type(2) > div:nth-of-type(2) > div:nth-of-type(1) (Fig Leaf)

    What's wrong: Both "Add to basket" controls are clickable <div>s. They have no role and no tabindex, and the tab walk never reached them. Screen readers announce them as plain text, not as buttons.

    Who it affects: Keyboard users and screen reader users. They can't buy anything, which is the main job of a shop homepage.

    Fix: Use a real button and keep the existing click handler and class. A button is focusable, works with Enter and Space with no extra code, and is announced as a button.

    <!-- before -->
    <div class="…">Add to basket</div>
    <!-- after -->
    <button type="button" class="…">Add to basket</button>
    

    3. The basket button has no name

    • Criterion: 4.1.2 Name, Role, Value (A)
    • Where: body > header > button.cart

    What's wrong: The button holds only an SVG cart icon. It has no text, aria-label or aria-labelledby (axe button-name), so screen readers just say "button".

    Who it affects: Screen reader users and voice control users. They can't find the basket or tell what this button does.

    • Fix:
    <!-- before -->
    <button class="cart"><svg viewBox="0 0 24 24" width="24" height="24">…</svg></button>
    <!-- after -->
    <button class="cart" aria-label="Basket"><svg aria-hidden="true" focusable="false" viewBox="0 0 24 24" width="24" height="24">…</svg></button>
    

    When the basket has items in it, include the count in the name, for example aria-label="Basket, 2 items".

    4. The members' offer text is far too faint

    • Criterion: 1.4.3 Contrast (Minimum) (AA)
    • Where: .promo > p ("Members save 15% on every order. Terms apply. Offer ends Sunday.")
    • What's wrong: The text is #aaaaaa on #fdf6e3 at 16px normal weight, which gives 2.15:1. It needs 4.5:1.

    Who it affects: People with low vision, older people, and anyone reading on a phone in sunlight. They may miss the offer and its terms.

    • Fix: Change the text colour to #717171 (4.52:1) or darker, such as the page's body colour #222222.

    Serious

    5. No visible focus on the main navigation links

    • Criterion: 2.4.7 Focus Visible (AA)

    Where: body > header > nav > a:nth-of-type(1) (Candles), body > header > nav > a:nth-of-type(2) (Gifts), body > header > nav > a:nth-of-type(3) (Journal)

    What's wrong: When these links are focused, the outline is none, there's no box-shadow, and the pixels don't change at all (0% visible change). The focus screenshots confirm we see no indicator. Every other control on the page keeps the browser's default ring.

    • Who it affects: Sighted keyboard users. They lose track of where they are as soon as they start tabbing.
    • Fix: Bring back a clear focus style that works on the dark header, for example:
    header nav a:focus-visible {
      outline: 2px solid #ffffff;
      outline-offset: 3px;
    }
    

    6. Product images have no alt text

    • Criterion: 1.1.1 Non-text Content (A)
    • Where: .card:nth-child(1) > img (Amber & Oak), .card:nth-child(2) > img (Fig Leaf)

    What's wrong: Neither <img> has an alt attribute (axe image-alt). Without one, some screen readers read out the image source, and here that's a long data:image/svg+xml… string.

    • Who it affects: Screen reader users. They hear noise in every product card.

    Fix: If the image only repeats the product name shown below it, mark it decorative with alt="". If real product photos go here, describe what matters, for example alt="Amber & Oak candle in a smoked-glass jar".

    7. The email field's only label is its placeholder

    • Criterion: 3.3.2 Labels or Instructions (A)
    • Where: #email in the "Get 10% off your first order" form (#signup)

    What's wrong: The field's only label is its placeholder "Email address". That gives it an accessible name, but the hint disappears once someone starts typing, and placeholder grey is often hard to read. We rated this Serious rather than Blocker because screen readers still get a name.

    Who it affects: People with memory or attention difficulties, people with low vision, and anyone who gets distracted mid-typing.

    • Fix:
    <!-- before -->
    <input id="email" type="email" placeholder="Email address">
    <!-- after -->
    <label for="email">Email address</label>
    <input id="email" type="email" name="email" autocomplete="email">
    

    8. The sign-up error isn't tied to the field or announced

    • Criterion: 3.3.1 Error Identification (A), and 4.1.3 Status Messages (AA)
    • Where: #signup form, after pressing "Sign up" with the field empty

    What's wrong: Submitting empty adds the text "Error". It isn't in a live region and isn't linked to #email (no aria-describedby or aria-errormessage), #email doesn't get aria-invalid, and focus stays on the "Sign up" button.

    Who it affects: Screen reader users hear nothing and don't know the sign-up failed. Other people may not see which field is wrong.

    • Fix: Put the error next to the field, link it, mark the field invalid, and move focus to the field:
    <label for="email">Email address</label>
    <input id="email" type="email" aria-invalid="true" aria-describedby="email-error">
    <p id="email-error">Enter your email address, for example name@example.com</p>
    

    Then call email.focus() on a failed submit. That makes the error announced, so no live region is needed.

    9. Quantity buttons are too small and too close together

    • Criterion: 2.5.8 Target Size (Minimum) (AA)

    Where: .card:nth-child(1) > .qty > button[aria-label="Fewer"], .card:nth-child(1) > .qty > button[aria-label="More"], .card:nth-child(2) > .qty > button[aria-label="Fewer"], .card:nth-child(2) > .qty > button[aria-label="More"]

    What's wrong: Each button is 16×16px, and the safe space around them is only 12px across, where 24px is needed (axe target-size, confirmed by the probe).

    Who it affects: People with tremors or limited dexterity, and anyone on a touch screen. They'll often hit the wrong button.

    • Fix: Make them at least 24×24px, and ideally 44×44px on touch:
    .qty button { min-width: 24px; min-height: 24px; }
    .qty { gap: 4px; }
    

    10. The delivery ticker scrolls forever with no way to stop it

    • Criterion: 2.2.2 Pause, Stop, Hide (A)

    Where: body > div.ticker > span ("Free delivery on orders over £30 · New autumn scents are here · Hand-poured in small batches")

    What's wrong: A CSS animation called scroll runs for 12s per loop and repeats forever. It starts with the page, and there's no pause or stop control. It keeps running when prefers-reduced-motion: reduce is on.

    Who it affects: People with attention difficulties, people with vestibular disorders, and slow readers. Screen magnifier users also struggle, because the text slides out of view.

    Fix: Simplest: stop the animation and show the messages as static text that wraps. If it has to move, add a visible "Pause" button that toggles animation-play-state, and stop it for reduced motion:

    @media (prefers-reduced-motion: reduce) {
      .ticker span { animation: none; }
    }
    

    11. The page scrolls sideways on a phone-width screen

    • Criterion: 1.4.10 Reflow (AA)

    Where: body > main > div:nth-of-type(1) (the .promo box, 632px wide). The ticker body > div > span is also clipped.

    What's wrong: At 320px wide, the page is 656px wide (scrollWidth 656), so people have to scroll sideways to read the offer. The offer box has a fixed width.

    • Who it affects: People who zoom to 400% on a desktop, and people on small phones.
    • Fix: Let the box shrink to fit:
    .promo { width: auto; max-width: 632px; }
    

    12. The journal link only stands out by colour

    • Criterion: 1.4.1 Use of Color (A)
    • Where: #journal > p > a ("Read about our wax")

    What's wrong: The link is #2f5d8a inside #222222 text, which is only 2.31:1 against the words around it (3:1 is needed), and it has no underline. Against the white background, the link itself passes at 6.87:1.

    • Who it affects: People with colour blindness or low vision. They can't tell it's a link.
    • Fix: Underline links in body text:
    main p a { text-decoration: underline; }
    

    Moderate

    13. The page has no title

    • Criterion: 2.4.2 Page Titled (A)
    • Where: <head>, which has no <title> (axe document-title)
    • What's wrong: The browser tab and screen readers have no page name to announce.
    • Who it affects: Screen reader users, and anyone switching between tabs.
    • Fix: <title>Moth & Wick | Hand-poured candles</title>

    14. The page language isn't set

    • Criterion: 3.1.1 Language of Page (A)
    • Where: <html> (axe html-has-lang)

    What's wrong: There's no lang attribute, so screen readers guess the language and may pronounce the page wrongly.

    • Who it affects: Screen reader users, and people using translation or reading tools.
    • Fix: <html lang="en-GB">

    15. "Read more" links don't say what they open

    • Criterion: 2.4.4 Link Purpose (In Context) (A)

    Where: main > div:nth-of-type(2) > div:nth-of-type(1) > p:nth-of-type(2) > a (to #amber), main > div:nth-of-type(2) > div:nth-of-type(2) > p:nth-of-type(2) > a (to #fig)

    What's wrong: Both links say only "Read more", and each sits alone in its own paragraph. In a links list, a screen reader user hears "Read more, Read more".

    • Who it affects: Screen reader users moving from link to link, and voice control users.
    • Fix: Add the product name visually, or for screen readers only:
    <a href="#amber">Read more<span class="visually-hidden"> about Amber &amp; Oak</span></a>
    

    16. The error message says only "Error"

    • Criterion: 3.3.3 Error Suggestion (AA)
    • Where: #signup, the message shown after submitting empty
    • What's wrong: The only text that appears is "Error". It doesn't say what's wrong or how to fix it.
    • Who it affects: Everyone, and especially people with cognitive disabilities.

    Fix: Say what to do: "Enter your email address, for example name@example.com". If the address isn't valid, use: "Enter an email address in the format name@example.com".

    17. Headings jump from level 1 to level 4

    • Criterion: related to 1.3.1 Info and Relationships (A) (axe best practice heading-order)
    • Where: #candles (<h4>Best sellers</h4>)

    What's wrong: The outline goes h1 "Candles for long evenings", then h4 "Best sellers", then h2 for the sections that follow. "Best sellers" looks and works like a section heading at the same level as the others.

    • Who it affects: Screen reader users who navigate by headings. They may think they've missed sections.
    • Fix: Change it to <h2 id="candles">Best sellers</h2> and restyle it if it needs to look smaller.

    Minor

    18. The ticker sits outside any landmark

    • Criterion: best practice (axe region), not a WCAG failure
    • Where: body > div.ticker

    What's wrong: The ticker sits between <header> and <main> but isn't in either, so people who move by landmarks can skip past it without knowing.

    • Who it affects: Screen reader users who navigate by landmarks.
    • Fix: Move the ticker inside <header>. Or, once it's static, put it in an <aside aria-label="Offers">.

    19. Quantity button names don't say which product they change

    • Criterion: best practice (supports 2.4.6 Headings and Labels)
    • Where: the four .qty buttons named "Fewer" and "More"

    What's wrong: A screen reader user hears "More, button" with nothing to say what it's for. We didn't confirm whether the quantity "1" next to them is announced when it changes.

    • Who it affects: Screen reader users.

    Fix: aria-label="Increase quantity of Amber & Oak" and aria-label="Decrease quantity of Amber & Oak". Also make the number a live value, such as <output aria-live="polite">1</output> or a labelled <input type="number">.

    Needs a human check

    1.4.3 Contrast (Minimum), quantity buttons: axe couldn't measure the "−" and "+" glyphs because they aren't letters. In the screenshot they look like dark glyphs on the browser's default light grey, which would pass, but we didn't measure those colours. Check the computed color and background-color with contrast.py.

    2.5.3 Label in Name, quantity buttons: the visible labels are the symbols "−" and "+", and the names are "Fewer" and "More". Symbols usually aren't treated as text labels, so this probably passes, but axe couldn't decide. Ask a voice control user whether saying "click plus" works.

    3.3.2 Labels or Instructions, chat field: #chat-msg has no visible label, only an accessible name of "Your question" from aria-label. The "Ask us anything" heading above it may count as the instruction. Decide whether that's clear enough. A visible label is the safer choice.

    1.4.1 Use of Color, sign-up error: the probe recorded the "Error" text but took no screenshot of it. Check that it isn't shown only in red or only with an icon.

    1.3.5 Identify Input Purpose, email field: axe didn't flag autocomplete, which may simply mean the attribute isn't there. Check that #email has autocomplete="email".

    Product image, Amber & Oak: in our screenshot it renders as a broken image (the data: SVG doesn't load). That's not an accessibility failure in itself, but check it, because the alt text decision in issue 6 depends on what the image shows.

    Passed

    • 1.4.4 Resize Text: at 200% text size, body text grew from 16px to 32px with nothing clipped or overlapping.
    • 1.4.12 Text Spacing: with WCAG spacing applied (line height 1.5, letter spacing 0.12em, word spacing 0.16em, paragraph spacing 2em), no text was clipped.
    • 2.4.1 Bypass Blocks: the page has header, nav, main and footer landmarks, and only 4 tab stops come before the main content, so a skip link isn't needed.
    • 2.4.3 Focus Order: the tab order follows the visual layout from top to bottom, with no positive tabindex. The chat trap is reported separately under 2.1.2.
    • 2.4.11 Focus Not Obscured (Minimum): no focused element was hidden by sticky or fixed content.

    Not checked

    • 1.2.1 to 1.2.5 (audio and video): not applicable, because the page has no audio or video.
    • 1.3.2 Meaningful Sequence, 1.3.3 Sensory Characteristics: need a screen reader read-through.
    • 1.3.4 Orientation: not tested in landscape and portrait. Rotate a phone, or emulate it, to check.
    • 1.4.5 Images of Text: the Fig Leaf image contains the words "Fig Leaf". Whether that's a placeholder or a real image of text needs a person to judge.
    • 1.4.11 Non-text Contrast: we didn't measure input borders, the default focus ring against the header, or the cart icon. Run contrast.py --ui on the computed colours.
    • 1.4.13 Content on Hover or Focus: the probe doesn't hover. Check any tooltips or menus by hand.
    • 2.1.4 Character Key Shortcuts, 2.2.1 Timing Adjustable, 2.3.1 Three Flashes or Below Threshold: we saw no shortcuts, timers or flashing, but the probe doesn't test for them.
    • 2.4.5 Multiple Ways, 3.2.3 Consistent Navigation, 3.2.4 Consistent Identification, 3.2.6 Consistent Help: these need the rest of the site.
    • 2.5.1 Pointer Gestures, 2.5.2 Pointer Cancellation, 2.5.4 Motion Actuation, 2.5.7 Dragging Movements: need a manual pointer and touch test.
    • 3.1.2 Language of Parts, 3.2.1 On Focus, 3.2.2 On Input: need a manual pass once lang is set.
    • 3.3.4 Error Prevention (Legal, Financial, Data), 3.3.7 Redundant Entry, 3.3.8 Accessible Authentication (Minimum): these apply to checkout and sign-in, which aren't on this page.
    • How it actually sounds in VoiceOver, NVDA or JAWS: we checked the computed names and roles, not real screen reader output.

    This audit shows what we could find, not a certificate of compliance. Testing with disabled people, and with real assistive technology, still matters.

    Want these issues as a CSV for your ticket tracker?

    broken.html

    CSS · design tokens

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Lantern holds a light up to your work and shows what's hidden in the dark: the things that stop disabled people using it. It checks against WCAG 2.2 Level AA and writes up each issue by severity, with a fix you can make today.

    How it works

    1. Ask Claude. Say "is this accessible?" with a URL, your local dev server, a Figma link, a screenshot or some code.
    2. Lantern looks closely. On a page, it runs axe-core, then does what automated tools miss: a keyboard-only pass, visible focus, traps, 320px reflow, 200% text zoom, reduced motion, target sizes and focus hidden behind sticky bars. In Figma, it works out contrast from the real fills, gradients included, and checks every component has a focus state.
    3. You get a report. Blockers first, each with the WCAG criterion, where it is, who it affects and the fix. "Passed" and "Not checked" lists mean silence never looks like a pass.
    4. Take it to your tickets. Ask for a CSV and paste the issues straight into your tracker.

    What it checks

    • Live pages and dev servers: axe-core plus a manual pass over keyboard, focus, layout, motion, targets, names, labels and errors.
    • Figma frames: contrast from the actual fills, target sizes, focus and error states, colour-only meaning, and reading order.
    • Screenshots: what's visible, clearly marked as estimated, plus an honest list of everything a picture can't show.
    • Code: HTML, JSX, Astro and Vue, checked for semantics and ARIA mistakes, with file and line for each.
    • Quick questions: "Does this grey pass on white?" gets a ratio, a yes or no, and a nearby colour that passes.

    Lantern never invents a finding. If it can't be sure, it tells you how to check.

    Not a compliance certificate: every report lists what it couldn't check, and testing with disabled people and real assistive technology still matters. Auditing a live URL or dev server needs Claude Code with Node.js 18+ and a local Chromium (about 150MB, installed after asking). On claude.ai it reviews Figma frames, screenshots and code only. Screenshot findings are marked as estimated. It can't tell how a page actually sounds in a screen reader.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 13 days ago

    Requires

    Figma
    Node.js 18+
    Playwright
    axe-core
    Python 3
    Node.js

    Permissions

    Terminal / Shell
    Browser
    Read Files
    Write Files
    Network Access

    Allowed Hosts

    api.figma.com

    Terminal and Browser: in Claude Code, Lantern opens the page in a local Chromium (Playwright) on your own machine and runs axe-core there. Network access: only to install Playwright, axe-core and Chromium (about 150MB) from npm the first time, after asking. Read files: to audit component code. Write files: the npm install in the skill's scripts folder, probe screenshots, and a CSV of issues if you ask for one. Figma: read-only, through the Figma connector. Nothing is sent anywhere else.

    Listed13 days ago

    What's inside

    Frequently Asked Questions

    No. Lantern shows what it could find, and lists what it couldn't check. Testing with disabled people and real assistive technology still matters, and we say so in every report.

    It's built not to. Every issue needs evidence, such as an axe result, a measured ratio or a line of code. Anything it isn't sure about goes under "Needs a human check", with the reason.

    WCAG 2.2, Level AA, including the new criteria for focus, target size, dragging, consistent help, redundant entry and accessible sign-in. It knows 4.1.1 Parsing was removed.

    Yes, for Figma frames, screenshots, code and contrast questions. Auditing a live URL needs a browser, so that part works in Claude Code only.

    In Claude Code, pages are opened in a browser on your own machine, and axe runs there too. What Claude reads, it reads the same way it reads anything else you share with it. Lantern sends nothing anywhere else.

    Yes, on as many of your own and your clients' projects as you like. Please don't share or resell the skill files. The reports are yours.

    New in Frontend & Web Apps