Same crawler. Now it reads your site the way a screen reader does.
Katla already visits every page to find cookies. From Pro, the same scan doubles as an accessibility scanner: it runs a WCAG 2.2 AA audit, scores the site, and tells you which element to fix first. Ready for the European Accessibility Act, without another vendor. And every plan, Free included, gets the accessibility widget at no cost.
- Standard
- WCAG 2.2, Level A and AA
- Regulation
- European Accessibility Act (in force since June 2025), EN 301 549
- Coverage
- Every page in your cookie scan, on the same schedule
- Plans
- Audit: Pro and Business. Widget: every plan, free
One crawl, two audits.
The cookie scanner already renders every page in a real browser. The accessibility audit runs in the same session, so there is nothing new to configure and nothing new to pay per page.
Scan runs as usual
Same crawl, same schedule. Pages render in a real browser, exactly as they do for the cookie inventory.
Audit per page
Once the page settles, it is tested against WCAG 2.2 Level A and AA rules in the state a consenting visitor sees.
Score and rank
Issues are grouped by severity, principle and criterion, with a score for the site and issue counts for every page.
Fix and re-scan
Export the report, prompt your coding assistant, or read it over the CLI and MCP server. The next scan shows the delta.
A report your coding assistant can act on.
Every issue carries the exact element, the WCAG criterion and how widely it occurs. “Prompt to improve” turns the issues you pick into a prompt for Claude Code, Cursor or Copilot. Or read the report straight from the MCP server.
# Accessibility fixes for example.com Source: Katla scan, Sep 2 2026 · WCAG 2.2 AA · 31 issues ## Critical (4) - [critical] Images must have alternative text (image-alt) WCAG 1.1.1 · 6 pages · 23 elements Reference: https://dequeuniversity.com/rules/axe/4.13/image-alt - [critical] Form elements must have labels (label) WCAG 1.3.1, 4.1.2 · 2 pages · 5 elements ## Serious (11) - [serious] Buttons must have discernible text (button-name) WCAG 4.1.2 · 14 pages · 41 elements For each issue: find the markup or component responsible, fix it at the source rather than per page, and say which files you changed.
Give visitors controls while you fix the code.
A small, accessible panel your visitors can open to adjust text size, contrast, spacing and motion for themselves. It does not replace fixing what the audit finds - nothing bolted to a page can - but it helps someone today. Free on every plan, including Free.
- Controls
- Text size, line and letter spacing, alignment, readable font, contrast and colour schemes, saturation, reading guide, highlight links, headings, focus and hover, large cursor, hide images, mute sounds, stop animations
- Built right
- Keyboard operable and screen-reader labelled, opens with Alt+Shift+A or the first tab stop on the page, and remembers each visitor’s choices in their own browser
- Honest about it
- It adjusts the page for the person who asks. It does not rewrite your markup, and installing it does not make a site conform to WCAG
- Install
- One script tag. Works on any site, headless or not, and starts from the visitor’s own reduced-motion and contrast settings
- Price
- Free on every plan. The snippet is in your dashboard right after sign-up
The panel carries a “Powered by Katla” line on Free and Starter, linking back to katla.app, and drops it on Pro and above. The tag is the same either way.
Automated coverage of WCAG 2.2 AA, honestly labelled.
Automated tools catch roughly half of accessibility problems. The report says which criteria were tested, which need a human, and never claims a pass it cannot prove.
Text alternatives
1.1.1Images, icons and SVG without a name; decorative images not hidden from assistive tech.
Contrast and colour
1.4.1 · 1.4.3Text contrast against the real rendered background, and meaning carried by colour alone.
Keyboard and navigation
2.1.1 · 2.4.1 · 2.4.2Keyboard traps, missing skip links and pages without a title - the things that strand a keyboard user.
Structure and names
1.3.1 · 3.3.2 · 4.1.2Headings in order, landmarks present, form controls and links with accessible names.
Target size
2.5.8New in WCAG 2.2: interactive targets at least 24×24 CSS px, or spaced so they do not overlap.
Needs a human
Flagged, never passedCriteria automation cannot judge - alt text quality, reading order, captions - are reported as manual checks, never as passes.
Widget on every plan. Audit from Pro.
No per-page or per-scan fee. Same flat price per site as before.
See pricing →Find out your score before someone else does.
Upgrade to Pro and your next scheduled scan includes the accessibility audit. Already on Pro? It is in your dashboard now.