Website Accessibility Checker: WCAG 2.2 & EAA

What does Website Accessibility Checker do?

Website Accessibility Checker runs an automated WCAG 2.2 audit on any list of web pages, up to 1,000 URLs per run. For every page you get:

• ♿ an accessibility score from 0 to 100
• 📋 a list of issues, each with the WCAG success criterion, level (A/AA), severity, number of affected elements, an example CSS selector and a plain-English fix
• 🇪🇺 European Accessibility Act (EAA) notes: whether the page looks like an online shop, payment or booking service, and how many issues map to WCAG A/AA
• 🔎 SEO basics: title, meta description, H1, canonical URL, language, robots meta
• 🔒 security headers: HTTPS, HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy
• 🧩 detected tech: CMS, shop platform, frameworks, analytics, CDN, and accessibility overlay widgets

Paste your URLs, click Start, and download the results as JSON, CSV, Excel or HTML, or get them through the Apify API. Because it runs on the Apify platform, you can schedule audits, call them from your own code, and connect the results to Google Sheets, Slack, Zapier, Make and other tools.

Who is this WCAG checker for?

• Web agencies and freelancers: audit a prospect's site in seconds and show concrete issues with the exact element and how to fix it.
• E-commerce and product teams preparing for the European Accessibility Act: screen all your storefronts and landing pages and find the most serious problems first.
• Accessibility consultants: triage hundreds of pages before the manual review, so your time goes to what automation can't check.
• SEO and marketing teams: get accessibility, SEO basics and security headers from one run.
• Portfolio and compliance monitoring: schedule a weekly run and track scores over time.

What does it check?

Area	Checks	WCAG 2.2
Images	missing alt text, alt text that is a file name, image buttons, image map areas, role="img" without a name	1.1.1
Forms	fields without a label, invalid autocomplete values	1.3.1, 4.1.2, 1.3.5
Buttons and links	buttons without a name, empty links, vague link text ("click here", "read more", also in German, French, Spanish, Italian and Dutch)	4.1.2, 2.4.4
Structure	page language, page title, H1, skipped heading levels, empty headings, main landmark, lists	3.1.1, 2.4.2, 1.3.1
Frames	<iframe> without a title	4.1.2
Navigation	skip link and its target, way to bypass repeated content, positive tabindex	2.4.1, 2.4.3
Zoom and timing	zoom disabled in the viewport tag, timed page refresh, <marquee>/<blink>	1.4.4, 2.2.1, 2.2.2
Media	autoplaying sound, videos with controls but no captions track	1.4.2, 1.2.2
IDs	duplicate ids used by labels or ARIA (serious), other duplicate ids (best practice; WCAG 2.2 removed 4.1.1)	1.3.1, 4.1.2
Colour contrast	text contrast against solid backgrounds, only with "Render JavaScript" on	1.4.3

Hidden elements (hidden, aria-hidden="true", display:none) are ignored, like a screen reader would.

How to run an accessibility audit

1. Click Try for free and sign in to Apify (the free plan is enough to start).
2. Paste one or more URLs into Website URLs, or upload a text file with one URL per line.
3. Optional: set Pages per website to follow links and audit up to 20 pages per site.
4. Optional: turn on Render JavaScript and check colour contrast for single-page apps and for the contrast check.
5. Click Start. Open the Overview, Issues, SEO basics or Security headers tab when the run finishes.

Input example

{
    "startUrls": [{ "url": "https://www.example.com" }, { "url": "shop.example.org/checkout" }],
    "maxPagesPerSite": 5,
    "renderJavaScript": false,
    "includeSeo": true,
    "includeSecurityHeaders": true
}

Output example

One item per page (shortened):

{
    "url": "https://www.example.com/",
    "accessibilityScore": 74,
    "issuesCount": 3,
    "criticalCount": 1,
    "seriousCount": 1,
    "moderateCount": 1,
    "minorCount": 0,
    "issues": [
        {
            "rule": "image-alt",
            "title": "Images without alternative text",
            "wcag": "1.1.1",
            "level": "A",
            "severity": "critical",
            "count": 4,
            "exampleSelector": "main > section.team > img:nth-of-type(2)",
            "exampleHtml": "<img src=\"/team/photo-2.jpg\" class=\"avatar\">",
            "fix": "Add an alt attribute to every <img>. Describe what the image shows or does; use alt=\"\" for purely decorative images."
        }
    ],
    "seo": { "title": "Example Shop", "metaDescription": "…", "h1": "Welcome", "canonical": "https://www.example.com/", "lang": "en" },
    "securityHeaders": { "https": true, "contentSecurityPolicy": false, "missing": ["Content-Security-Policy", "Permissions-Policy"] },
    "tech": ["Shopify", "Google Tag Manager", "Cloudflare"],
    "eaaRelevant": {
        "serviceSignals": ["e-commerce platform detected (Shopify)", "\"add to cart\" control"],
        "wcagAAIssueCount": 2,
        "notes": ["The European Accessibility Act (EAA) has applied since 28 June 2025 …", "…"]
    },
    "notChecked": ["Colour contrast (WCAG 1.4.3): run with renderJavaScript enabled to check it", "…"],
    "error": null
}

Pages that can't be audited get a row with an error code (invalid-url, blocked-by-robots-txt, http-404, http-403, request-failed, …) and cost nothing.

How much does a website accessibility audit cost?

This Actor uses pay per event. You pay only for pages that were actually audited:

Event	Price
Page audited	$0.005 per page
Page that failed, was blocked by robots.txt or returned an error	free

• 100 pages cost $0.50; 1,000 pages cost $5.
• The price is the same with or without JavaScript rendering.
• Apify also charges a tiny standard start fee per run ($0.00005 per GB of memory, so $0.00005 for a normal run and $0.0002 with browser rendering).
• Apify's free plan includes $5 of monthly usage, enough for about 1,000 audited pages a month.
• Set Maximum cost per run in the run options and the Actor stops when it is reached.

How is the score calculated?

Each check that applies to the page (for example, the image checks only apply when the page has images) has a weight by severity: critical 10, serious 7, moderate 3, minor 1. The score is the weighted share of applicable checks that passed, similar in spirit to how Lighthouse scores accessibility. A page with no detected issues scores 100.

The score is a way to compare and prioritise pages. It is not a compliance grade.

Limitations

• Automated checks find only part of all accessibility problems. Keyboard operation, visible focus, focus order, target size, reading order and whether alt texts and labels are meaningful need manual testing. Each row lists what wasn't checked in notChecked.
• Colour contrast is only checked with "Render JavaScript" on. It needs a real browser to compute styles. Text over images, gradients, semi-transparent layers or with text shadows is skipped rather than guessed, and the row says how many items were skipped.
• Without JavaScript rendering, only the HTML sent by the server is checked. Content added later by JavaScript (common in React/Vue apps) is only seen with rendering on.
• The Actor respects robots.txt and waits at least one second between requests to the same site. Sites that block automated visitors return an error row (free).
• Login-protected pages are not supported.
• This is not legal advice and not an EAA or WCAG conformance certificate.

FAQ

Does this make my website EAA compliant?

No tool can do that on its own. The Actor shows automatically detectable WCAG issues and signals that a page belongs to a service type covered by the European Accessibility Act. Use it to find and fix problems fast, then have a person test what automation can't. For legal questions, ask a qualified advisor.

Which standard is used?

The checks map to WCAG 2.2 Level A and AA. EN 301 549, the European standard used for the EAA, is based on WCAG 2.1 AA in its current legal version (v3.2.1); its new version v4.1.1, published in September 2026, uses WCAG 2.2 AA.

How is this different from Lighthouse or axe?

Those tools check one page at a time in your browser. This Actor audits up to 1,000 pages per run in the cloud, adds SEO, security header and tech data, and gives you a spreadsheet-friendly dataset and an API.

An accessibility overlay is installed on my site. Why are there still issues?

Overlay widgets don't change the HTML that the checks analyse, so the issues are still in the code. The Actor lists detected overlays under tech.

Can I run it on a schedule or from my code?

Yes. Create a task with your URLs and add a schedule in Apify Console, or call the Actor through the Apify API, the JavaScript or Python client, or integrations such as Make, Zapier and n8n.

Why did a page return blocked-by-robots-txt or http-403?

The site's robots.txt disallows crawlers for that page, or the site blocks automated visitors. These rows are free. You can try the Apify datacenter proxy in Advanced options for 403 errors.

More tools from the same developer

All pay-per-result, no proxy or login needed, built and maintained by the same developer:

Website audits

• Cookie & Tracker Audit: GDPR Consent Checker: cookies and tracking tags that load before consent.
• AI Crawler Access Checker: robots.txt & llms.txt: which AI crawlers a site allows, plus llms.txt.
• Website Change Monitor: Diffs, Prices & Alerts: get a row only when a page changes, with a clean diff.

Company data and compliance

• Company Contact Finder: Emails, Phones & Socials: contact details published on company websites.
• UK New Companies Feed: Companies House Daily: newly incorporated UK companies with sector filters.
• EU VAT Number Validator: Bulk VIES Checker: bulk VAT checks with name, address and consultation number.
• LEI Corporate Tree: GLEIF Parents & Subsidiaries: LEI lookup with parents, subsidiaries and a KYC summary.

Market signals

• US WARN Layoff Notices: 12 States Daily Feed: layoff and plant closure notices from official state sources.
• US Product Recalls Monitor: FDA & CPSC Feed: FDA and CPSC recalls in one feed, with severity.

Feedback

Found a false positive or missing check? Open an issue on the Issues tab. Bug reports with the page URL are fixed first.