Verified AgentReady.md certificate
Issued sig: ff30fd083461ff33 Verify →

Analyzed URL

https://Wexlo.eu

Measured last week

Analyze another URL

AI-Ready Score

Good

out of 100

Token Savings

HTML tokens 40.330
Markdown tokens 1596
Savings 96%

Score Breakdown

Semantic HTML 93/100
Content Efficiency 60/100
AI Discoverability 55/100
Structured Data 100/100
Accessibility 100/100

Emerging protocols

0 of 6 detected

Well-known endpoints AI agents look for. Detected here means an agent can discover and connect to your service automatically.

  • OAuth Protected Resource RFC 9728
    /.well-known/oauth-protected-resource
  • OAuth Discovery RFC 8414
    /.well-known/oauth-authorization-server
  • MCP Server Card SEP-1649 draft
    /.well-known/mcp/server-card.json
  • A2A Agent Card A2A v1.0
    /.well-known/agent-card.json
  • API Catalog RFC 9727
    /.well-known/api-catalog
  • Agent Skills index Discovery RFC v0.2.0 draft
    /.well-known/agent-skills/index.json

Doesn't stay fixed by itself. Monitoring isn't built yet — join the list and we'll tell you when it is.

You're on the list! We'll notify you when it launches.

What we measured Content ratio: 4.1% (5933 content chars / 143566 HTML bytes)

Your page has a low ratio of actual content to total HTML. Much of the page weight is markup, scripts, or styles rather than content.

How to implement

Move CSS to external stylesheets, remove inline styles, minimize JavaScript, and ensure the HTML focuses on content structure.

Paste into a coding agent to make the fix

What we measured No Markdown for Agents support detected

Your site doesn't support Markdown for Agents. This Cloudflare standard lets AI agents request content in markdown format, reducing token usage by ~80%.

How to implement

Implement one or more: (1) Respond to Accept: text/markdown with markdown content. (2) Serve .md URLs (e.g., /page.md). (3) Add <link rel="alternate" type="text/markdown"> tags. (4) Add Link HTTP headers for markdown discovery.

Paste into a coding agent to make the fix

What we measured No Content-Signal found (robots.txt or HTTP headers)

No Content-Signal directives found. These tell AI agents how they may use your content (search indexing, AI input, training data). The recommended location is robots.txt.

How to implement

Add Content-Signal to your robots.txt: User-agent: *\nContent-Signal: search=yes, ai-input=yes, ai-train=no. You can also add it as an HTTP header on markdown responses.

Paste into a coding agent to make the fix

What we measured 11/590 elements with inline styles (1.9%)

Many elements have inline style attributes. These add noise for AI agents extracting content.

How to implement

Move all inline styles to CSS classes in your stylesheet. Use utility CSS frameworks like Tailwind if you need many unique styles.

Paste into a coding agent to make the fix
Markdown tokens: 1596
EAA · WCAG 2.1 AA · EN 301 549European Accessibility Act · WCAG 2.1 AA · EN 301 549

## Find what fails.Fix it. Prove it.

In plain terms: the European Accessibility Act (EAA) is the EU law that requires the websites and apps consumers use — shops, banking, booking, streaming — to work for people with disabilities. It has applied since 28 June 2025, and it also reaches businesses outside the EU that sell to EU consumers.

Wexlo scans your site against WCAG 2.1 AA — the standard behind the European Accessibility Act — shows exactly which element fails and how to fix it, and turns every fix into audit-ready evidence.

## Choose where to start

Need ongoing monitoring? [See subscriptions](https://wexlo.eu/pricing) (from €49/mo).

Engine

Real-browser scans

axe-core plus Wexlo's own checks, desktop and mobile viewports

Coverage

30 of 50 AA criteria

machine-checked in full or in part — stated in every report

Languages

Up to 4 languages

English, Nederlands, Français, Deutsch — by plan

Hosting

EU-hosted

infrastructure primarily hosted and processed in the EU

Anatomy of a finding

## Every finding tells you exactly what to do

No score, no vague warnings. Each finding names the rule, the element, and the fix — in language your developer can act on today.

The path

## From URL to evidence in four steps

1.  ### You give us a URL

    The free scan covers one page; on a paid plan we crawl up to 100 reachable pages per scan, on desktop and mobile viewports.

2.  ### The rule engine scans

    A real browser loads each page on desktop and mobile viewports, settles cookie banners and dynamic content, then runs axe-core plus Wexlo's own checks against WCAG 2.1 A and AA — the technical basis of EN 301 549.

3.  ### Every finding becomes a fix

    Per finding: the rule, the WCAG criterion, the CSS selector, a plain-language explanation, and a concrete fix suggestion.

4.  ### You get evidence, on a schedule

    Reports as HTML and PDF with a draft accessibility statement; scheduled re-scans verify that fixes stayed fixed.

The honest part

## Honest about what a scanner can see

Automated checks reliably cover roughly 30–50% of the WCAG 2.1 AA success criteria — today's scanner tests 30 of the 50 criteria automatically, in full or in part.

Every report states which criteria were tested automatically and which require manual review, so you know exactly where a human needs to look. Paid reports include the full criteria matrix and a manual checklist.

No automated scanner can certify legal compliance — anyone claiming otherwise is overclaiming.

[See all 50 criteria in plain language →](https://wexlo.eu/criteria)

Coverage of 50 AA success criteria

| Coverage | Criteria |
| --- | --- |
| 3 criteria — fully automated | 3 |
| 27 criteria — partially automated | 27 |
| 20 criteria — need human review | 20 |

## No cookie banner. Nothing to accept.

This site sets no tracking cookies — our visitor statistics are cookieless. The only cookie we ever set is the strictly necessary sign-in cookie in the customer portal (and the only one we hand out comes with a coffee — in person ☕).

[How we work without cookies →](https://wexlo.eu/faq#cookies)

The lane we're not in

## Real findings, not an overlay

### Overlay widgets

Inject a JavaScript layer and claim it makes your site compliant — the underlying code stays broken.

In April 2025 the FTC's final order against overlay vendor accessiBe (Docket No. C-4817, a $1M non-admission settlement) barred it from claiming its automated products can make websites WCAG-compliant without evidence.

### Wexlo

Reports what is broken in your actual code and how to fix it there. Fixes get verified on the next scan — that's what makes it evidence.

We will never ship or recommend an overlay.

Illustrative example — not from a customer site.

The deliverable

## What lands in your inbox

A tagged, accessible PDF plus an online report — evidence you can hand to a developer, an auditor, or an authority.

-   Every finding with criterion, selector, fix guidance, and effort estimate
-   The full 50-criteria matrix: tested, partially tested, needs review
-   A draft accessibility statement for your site
-   Scheduled re-scans that verify fixes stayed fixed

## Plans

[Monthly or yearly — pay yearly, get 2 months free](https://wexlo.eu/pricing?billing=year)

One website

### Starter

€49/mo

-   1 domain
-   Monthly automated scan
-   Unlimited rescans

[Choose Starter](https://wexlo.eu/pricing?plan=starter)

Up to 5 domains

### Growth

€149/mo

-   Up to 5 domains
-   Weekly automated scans
-   Unlimited rescans

[Choose Growth](https://wexlo.eu/pricing?plan=growth)

Up to 25 domains

### Business

€399/mo

-   Up to 25 domains
-   Daily automated scans
-   Unlimited rescans

[Choose Business](https://wexlo.eu/pricing?plan=business)

For agencies

### Agency

Volume pricing for agencies — request a quote.

-   20+ domains
-   Weekly automated scans
-   Unlimited rescans

[Talk to us](https://wexlo.eu/contact)

These cards show a few highlights per plan. The full comparison lists everything each subscription includes.

All prices exclude VAT · cancel monthly

[Compare all plan details](https://wexlo.eu/pricing#compare) — or [start with a free scan](https://wexlo.eu/scanner).

## Before you ask

**Is a Wexlo scan an accessibility audit?**

No — and any automated tool that calls itself an audit is overselling. A scan is automated: it reliably covers roughly 30–50% of the WCAG 2.1 AA success criteria. An audit adds human judgment: keyboard flows, screen-reader testing, meaningful alt text, logical reading order. Every Wexlo report states which criteria were tested automatically and which need manual review, so an auditor can start from our evidence instead of from zero.

**Does the European Accessibility Act apply to my business?**

The EAA (Directive (EU) 2019/882) has applied since 28 June 2025 to consumer-facing services in the EU — e-commerce is the broadest category: if consumers can buy products or services on your site, you are in scope. That includes non-EU companies selling to EU consumers. Purely B2B services fall outside it. Micro-enterprises providing services (fewer than 10 employees and ≤ €2M turnover) are exempt for services. Whether the law applies to your specific case is a question for your lawyer — what we can tell you is exactly what fails on your site.

**Can I cancel anytime?**

Yes. Subscriptions run monthly and you can cancel from the portal with one click; access runs until the end of the period you already paid for. No annual lock-in, no cancellation call.

[All questions →](https://wexlo.eu/faq)

Built to pass AA

## See what your site fails today
Wexlo — EU accessibility compliance scanning

[Skip to content](https://wexlo.eu/#main)

EAA · WCAG 2.1 AA · EN 301 549European Accessibility Act · WCAG 2.1 AA · EN 301 549

# Find what fails.Fix it. Prove it.

In plain terms: the European Accessibility Act (EAA) is the EU law that requires the websites and apps consumers use — shops, banking, booking, streaming — to work for people with disabilities. It has applied since 28 June 2025, and it also reaches businesses outside the EU that sell to EU consumers.

Wexlo scans your site against WCAG 2.1 AA — the standard behind the European Accessibility Act — shows exactly which element fails and how to fix it, and turns every fix into audit-ready evidence.

Your website

Scan free

One page, free · no account · results by email

Scan reportdemo-shop.example · 2026-07-06

One fix, proven

2.9:1 · Fail

→

5.5:1 · Pass

12Fail

5Review

41Pass

Top finding

WCAG 1.4.3 Checkout button label measures 2.9:1 against its background — normal text needs 4.5:1.

`button.checkout-cta > span`●Critical · fix: darken the label to #5B6B77

Illustrative example — not from a customer site.

Built to pass AA — this site passes the same automated checks we sell. [See our accessibility statement](https://wexlo.eu/accessibility).

## Choose where to start

### Free quick scan€0

1 page · instant · no account

[Run a free scan](https://wexlo.eu/scanner)

### One-off full report€79

up to 100 reachable pages · no subscription

[Order a one-off report](https://wexlo.eu/checkout/report_oneoff)

Need ongoing monitoring? [See subscriptions](https://wexlo.eu/pricing) (from €49/mo).

Engine

Real-browser scans

axe-core plus Wexlo's own checks, desktop and mobile viewports

Coverage

30 of 50 AA criteria

machine-checked in full or in part — stated in every report

Languages

Up to 4 languages

English, Nederlands, Français, Deutsch — by plan

Hosting

EU-hosted

infrastructure primarily hosted and processed in the EU

Anatomy of a finding

## Every finding tells you exactly what to do

No score, no vague warnings. Each finding names the rule, the element, and the fix — in language your developer can act on today.

Finding

WX-0142

Criterion

WCAG 1.4.3

contrast, minimum

Fail●Critical

What fails

The checkout button label measures 2.9:1 against its background — below the 4.5:1 required for normal text.

Element

`button.checkout-cta > span`

Fix

Darken the gray — same design language, passing contrast:

#9CA3AF · 2.9:1→#5B6B77 · 5.5:1Pass

Effort

S — under an hour, one CSS change

Illustrative example — not from a customer site.

The path

## From URL to evidence in four steps

1.  1### You give us a URL

    The free scan covers one page; on a paid plan we crawl up to 100 reachable pages per scan, on desktop and mobile viewports.

2.  2### The rule engine scans

    A real browser loads each page on desktop and mobile viewports, settles cookie banners and dynamic content, then runs axe-core plus Wexlo's own checks against WCAG 2.1 A and AA — the technical basis of EN 301 549.

3.  3### Every finding becomes a fix

    Per finding: the rule, the WCAG criterion, the CSS selector, a plain-language explanation, and a concrete fix suggestion.

4.  4### You get evidence, on a schedule

    Reports as HTML and PDF with a draft accessibility statement; scheduled re-scans verify that fixes stayed fixed.

The honest part

## Honest about what a scanner can see

Automated checks reliably cover roughly 30–50% of the WCAG 2.1 AA success criteria — today's scanner tests 30 of the 50 criteria automatically, in full or in part.

Every report states which criteria were tested automatically and which require manual review, so you know exactly where a human needs to look. Paid reports include the full criteria matrix and a manual checklist.

No automated scanner can certify legal compliance — anyone claiming otherwise is overclaiming.

[See all 50 criteria in plain language →](https://wexlo.eu/criteria)

Coverage of 50 AA success criteria

02550

| Coverage | Criteria |
| --- | --- |
| 3 criteria — fully automated | 3 |
| 27 criteria — partially automated | 27 |
| 20 criteria — need human review | 20 |

-   3 criteria — fully automated
-   27 criteria — partially automated
-   20 criteria — need human review

## No cookie banner. Nothing to accept.

This site sets no tracking cookies — our visitor statistics are cookieless. The only cookie we ever set is the strictly necessary sign-in cookie in the customer portal (and the only one we hand out comes with a coffee — in person ☕).

[How we work without cookies →](https://wexlo.eu/faq#cookies)

The lane we're not in

## Real findings, not an overlay

### Overlay widgets

Inject a JavaScript layer and claim it makes your site compliant — the underlying code stays broken.

In April 2025 the FTC's final order against overlay vendor accessiBe (Docket No. C-4817, a $1M non-admission settlement) barred it from claiming its automated products can make websites WCAG-compliant without evidence.

### Wexlo

Reports what is broken in your actual code and how to fix it there. Fixes get verified on the next scan — that's what makes it evidence.

We will never ship or recommend an overlay.

Scan reportdemo-shop.example
2026-07-06 · 5 pagesStarter · English

Illustrative example — not from a customer site.

The deliverable

## What lands in your inbox

A tagged, accessible PDF plus an online report — evidence you can hand to a developer, an auditor, or an authority.

-   Every finding with criterion, selector, fix guidance, and effort estimate
-   The full 50-criteria matrix: tested, partially tested, needs review
-   A draft accessibility statement for your site
-   Scheduled re-scans that verify fixes stayed fixed

## Plans[Monthly or yearly — pay yearly, get 2 months free→](https://wexlo.eu/pricing?billing=year)

One website### Starter

€49/mo

-   ·1 domain
-   ·Monthly automated scan
-   ·Unlimited rescans

[Choose Starter](https://wexlo.eu/pricing?plan=starter)

Up to 5 domains### Growth

€149/mo

-   ·Up to 5 domains
-   ·Weekly automated scans
-   ·Unlimited rescans

[Choose Growth](https://wexlo.eu/pricing?plan=growth)

Up to 25 domains### Business

€399/mo

-   ·Up to 25 domains
-   ·Daily automated scans
-   ·Unlimited rescans

[Choose Business](https://wexlo.eu/pricing?plan=business)

For agencies### Agency

Volume pricing for agencies — request a quote.

-   ·20+ domains
-   ·Weekly automated scans
-   ·Unlimited rescans

[Talk to us](https://wexlo.eu/contact)

These cards show a few highlights per plan. The full comparison lists everything each subscription includes.

All prices exclude VAT · cancel monthly

[Compare all plan details](https://wexlo.eu/pricing#compare) — or [start with a free scan](https://wexlo.eu/scanner).

## Before you ask

**Is a Wexlo scan an accessibility audit?+−**

No — and any automated tool that calls itself an audit is overselling. A scan is automated: it reliably covers roughly 30–50% of the WCAG 2.1 AA success criteria. An audit adds human judgment: keyboard flows, screen-reader testing, meaningful alt text, logical reading order. Every Wexlo report states which criteria were tested automatically and which need manual review, so an auditor can start from our evidence instead of from zero.

**Does the European Accessibility Act apply to my business?+−**

The EAA (Directive (EU) 2019/882) has applied since 28 June 2025 to consumer-facing services in the EU — e-commerce is the broadest category: if consumers can buy products or services on your site, you are in scope. That includes non-EU companies selling to EU consumers. Purely B2B services fall outside it. Micro-enterprises providing services (fewer than 10 employees and ≤ €2M turnover) are exempt for services. Whether the law applies to your specific case is a question for your lawyer — what we can tell you is exactly what fails on your site.

**Can I cancel anytime?+−**

Yes. Subscriptions run monthly and you can cancel from the portal with one click; access runs until the end of the period you already paid for. No annual lock-in, no cancellation call.

[All questions →](https://wexlo.eu/faq)

Built to pass AA## See what your site fails today

Your website

Scan free

One page, free · no account · results by email

Upload this file as /index.md on your server so AI agents can access a clean version of your page. You can also configure Accept: text/markdown content negotiation to serve it automatically.

Our recommendation

Download llms.txt
# Wexlo

> Automated WCAG 2.1 AA scanning for EU markets: findings with code-level evidence, plain-language fixes, multilingual reports, and a draft accessibility statement. No overlay widgets.

## Documentation
- [FAQ](https://wexlo.eu/faq)

## Main
- [Wexlo — EU accessibility compliance scanning](https://Wexlo.eu): Automated WCAG 2.1 AA scanning for EU markets: findings with code-level evidence, plain-language fixes, multilingual re…
- [Pricing](https://wexlo.eu/pricing)
- [About](https://wexlo.eu/about)
- [wexlo](https://wexlo.eu/)
- [How it works](https://wexlo.eu/how-it-works)
- [Customer portal](https://wexlo.eu/portal)
- [NL](https://wexlo.eu/nl)
- [Free scan](https://wexlo.eu/scanner)
- [Verify a report](https://wexlo.eu/verify)
- [Accessibility](https://wexlo.eu/accessibility)
- [[email protected]](https://wexlo.eu/cdn-cgi/l/email-protection)

## Legal
- [Privacy policy](https://wexlo.eu/privacy)
- [Terms & conditions](https://wexlo.eu/terms)

## Support
- [FAQ](https://wexlo.eu/faq)
- [Contact](https://wexlo.eu/contact)

Full llms.txt requires domain-wide analysis (coming soon)

Upload this file to https://wexlo.eu/llms.txt at the root of your domain. AI agents like ChatGPT, Claude, and Perplexity check this file to understand your site structure.

This site already has a llms.txt file.

Valid format
# Wexlo

> Automated EU accessibility compliance scanning. Wexlo scans websites against WCAG 2.1 A/AA (the technical basis of EN 301 549 and the European Accessibility Act) using the axe-core rule engine, and delivers findings with code-level evidence, plain-language fix suggestions, multilingual reports (EN/NL/FR/DE), and a draft accessibility statement. No JavaScript overlay widgets.

## What it does
- Scans pages with a real browser (Playwright) and the axe-core rule engine against WCAG 2.1 A/AA.
- Findings include the rule ID, WCAG criterion, impact level, and CSS selector of each affected element.
- AI-generated plain-language explanations and concrete code fixes per finding; the rule engine decides what counts as a finding, the AI only explains.
- Reports (HTML + PDF) and draft accessibility statements in English, Dutch, French, and German.
- Scheduled re-scans: monthly (Starter), weekly (Growth/Agency), or daily (Business).
- Free scan: one page, results by email, no account required.
- Honest scope: automated checks cover roughly 30-50% of WCAG 2.1 AA success criteria; every report states which criteria require manual review. Automated scanning is not a certification of legal compliance.

## Pricing (EUR, excl. VAT)
- Starter: €49.00/mo — Monthly automated EAA/WCAG scan for 1 domain, full report with fix suggestions, accessibility statement draft.
- Growth: €149.00/mo — Weekly scans, up to 5 domains, multilingual reports (EN/NL/FR/DE).
- Business: €399.00/mo — Daily scans, up to 25 domains, multilingual reports (EN/NL/FR/DE).
- Starter: €490.00/yr — Starter, billed yearly — 2 months free versus monthly.
- Growth: €1490.00/yr — Growth, billed yearly — 2 months free versus monthly.
- Business: €3990.00/yr — Business, billed yearly — 2 months free versus monthly.
- Agency: €15.00/domain/mo (minimum 20 domains) — Per-domain pricing for agencies, minimum 20 domains.
- One-time report: €79.00 (one-time) — One-off in-depth accessibility report for one website — full report with fix suggestions and a draft accessibility statement, in EN/NL/FR/DE. No subscription.

## Key pages
- Free scan: https://wexlo.eu/scanner
- Pricing: https://wexlo.eu/pricing
- Customer portal: https://wexlo.eu/portal

## Company
- Wexlo, KvK 66637694, VAT NL001677588B25, President Allendelaan 263, 1068 VM Amsterdam
- Contact: [email protected]

Semantic HTML

Uses article or main element (100/100)

Has <main>

Proper heading hierarchy (100/100)

Clean heading hierarchy

Uses semantic HTML elements (67/100)

23 semantic elements, 91 divs (ratio: 20%)

Meaningful image alt texts (100/100)

No images found

Low div nesting depth (100/100)

Avg div depth: 2.2, max: 7

Content Efficiency

Good token reduction ratio (100/100)

96% token reduction (HTML→Markdown)

Good content-to-noise ratio (0/100)

Content ratio: 4.1% (5933 content chars / 143566 HTML bytes)

Minimal inline styles (50/100)

11/590 elements with inline styles (1.9%)

Reasonable page weight (80/100)

HTML size: 140KB

AI Discoverability

Has llms.txt file (100/100)

llms.txt exists and is valid

Has robots.txt file (100/100)

robots.txt exists

Robots.txt allows AI bots (100/100)

All major AI bots allowed

Has sitemap.xml (100/100)

Sitemap found

Markdown for Agents support (0/100)
&#10007; Accept: text/markdown &#10007; .md URL &#10007; <link> tag &#10007; Link header
Has Content-Signal (robots.txt or HTTP headers) (0/100)
&#10003; robots.txt &#10003; HTTP header &#10007; Policy

Structured Data

Has Schema.org / JSON-LD (100/100)

JSON-LD found: Organization, WebSite, SoftwareApplication

Has Open Graph tags (100/100)

All OG tags present

Has meta description (100/100)

Meta description: 182 chars

Has canonical URL (100/100)

Canonical URL present

Has lang attribute (100/100)

lang="en"

Accessibility

Content available without JavaScript (100/100)

Content available without JavaScript

Reasonable page size (100/100)

Page size: 140KB

Content appears early in HTML (100/100)

Main content starts at 7% of HTML

{
  "url": "https://Wexlo.eu",
  "timestamp": 1783841895419,
  "fetch": {
    "mode": "simple",
    "timeMs": 109,
    "htmlSizeBytes": 143566,
    "supportsMarkdown": false,
    "markdownAgents": {
      "contentNegotiation": false,
      "mdUrl": {
        "found": false,
        "url": null
      },
      "linkTag": {
        "found": false,
        "url": null
      },
      "linkHeader": {
        "found": false,
        "url": null
      },
      "responseHeaders": {
        "contentSignal": null,
        "xMarkdownTokens": null,
        "vary": null
      },
      "frontmatter": {
        "present": false,
        "fields": [],
        "level": "none"
      },
      "level": "none"
    },
    "statusCode": 200
  },
  "extraction": {
    "title": "Wexlo — EU accessibility compliance scanning",
    "excerpt": "Automated WCAG 2.1 AA scanning for EU markets: findings with code-level evidence, plain-language fixes, multilingual reports, and a draft accessibility statement. No overlay widgets.",
    "byline": null,
    "siteName": "Wexlo",
    "lang": "en",
    "contentLength": 5933,
    "metadata": {
      "description": "Automated WCAG 2.1 AA scanning for EU markets: findings with code-level evidence, plain-language fixes, multilingual reports, and a draft accessibility statement. No overlay widgets.",
      "ogTitle": "Wexlo — EU accessibility compliance scanning",
      "ogDescription": "Automated WCAG 2.1 AA scanning for EU markets: findings with code-level evidence, plain-language fixes, multilingual reports, and a draft accessibility statement. No overlay widgets.",
      "ogImage": "https://wexlo.eu/og/og-en.png",
      "ogType": "website",
      "canonical": "https://wexlo.eu",
      "lang": "en",
      "schemas": [
        {
          "@type": "Organization",
          "@id": "https://wexlo.eu/#organization",
          "name": "Wexlo",
          "url": "https://wexlo.eu",
          "logo": "https://wexlo.eu/apple-icon.png",
          "description": "Automated WCAG 2.1 AA scanning for EU markets: findings with code-level evidence, plain-language fixes, multilingual reports, and a draft accessibility statement. No overlay widgets.",
          "email": "[email protected]",
          "contactPoint": {
            "@type": "ContactPoint",
            "email": "[email protected]",
            "contactType": "customer support",
            "availableLanguage": [
              "English",
              "Dutch"
            ]
          },
          "areaServed": "EU"
        },
        {
          "@type": "WebSite",
          "@id": "https://wexlo.eu/#website",
          "name": "Wexlo",
          "url": "https://wexlo.eu",
          "inLanguage": [
            "en",
            "nl"
          ],
          "publisher": {
            "@id": "https://wexlo.eu/#organization"
          }
        },
        {
          "@type": "SoftwareApplication",
          "@id": "https://wexlo.eu/#software",
          "name": "Wexlo",
          "applicationCategory": "BusinessApplication",
          "operatingSystem": "Web",
          "url": "https://wexlo.eu",
          "description": "Automated WCAG 2.1 AA scanning for EU markets: findings with code-level evidence, plain-language fixes, multilingual reports, and a draft accessibility statement. No overlay widgets.",
          "provider": {
            "@id": "https://wexlo.eu/#organization"
          },
          "offers": {
            "@type": "AggregateOffer",
            "priceCurrency": "EUR",
            "lowPrice": "49.00",
            "highPrice": "3990.00",
            "offerCount": 8
          }
        }
      ],
      "robotsMeta": null,
      "author": null,
      "generator": null,
      "markdownAlternateHref": null
    }
  },
  "markdown": "EAA · WCAG 2.1 AA · EN 301 549European Accessibility Act · WCAG 2.1 AA · EN 301 549\n\n## Find what fails.Fix it. Prove it.\n\nIn plain terms: the European Accessibility Act (EAA) is the EU law that requires the websites and apps consumers use — shops, banking, booking, streaming — to work for people with disabilities. It has applied since 28 June 2025, and it also reaches businesses outside the EU that sell to EU consumers.\n\nWexlo scans your site against WCAG 2.1 AA — the standard behind the European Accessibility Act — shows exactly which element fails and how to fix it, and turns every fix into audit-ready evidence.\n\n## Choose where to start\n\nNeed ongoing monitoring? [See subscriptions](https://wexlo.eu/pricing) (from €49/mo).\n\nEngine\n\nReal-browser scans\n\naxe-core plus Wexlo's own checks, desktop and mobile viewports\n\nCoverage\n\n30 of 50 AA criteria\n\nmachine-checked in full or in part — stated in every report\n\nLanguages\n\nUp to 4 languages\n\nEnglish, Nederlands, Français, Deutsch — by plan\n\nHosting\n\nEU-hosted\n\ninfrastructure primarily hosted and processed in the EU\n\nAnatomy of a finding\n\n## Every finding tells you exactly what to do\n\nNo score, no vague warnings. Each finding names the rule, the element, and the fix — in language your developer can act on today.\n\nThe path\n\n## From URL to evidence in four steps\n\n1.  ### You give us a URL\n\n    The free scan covers one page; on a paid plan we crawl up to 100 reachable pages per scan, on desktop and mobile viewports.\n\n2.  ### The rule engine scans\n\n    A real browser loads each page on desktop and mobile viewports, settles cookie banners and dynamic content, then runs axe-core plus Wexlo's own checks against WCAG 2.1 A and AA — the technical basis of EN 301 549.\n\n3.  ### Every finding becomes a fix\n\n    Per finding: the rule, the WCAG criterion, the CSS selector, a plain-language explanation, and a concrete fix suggestion.\n\n4.  ### You get evidence, on a schedule\n\n    Reports as HTML and PDF with a draft accessibility statement; scheduled re-scans verify that fixes stayed fixed.\n\nThe honest part\n\n## Honest about what a scanner can see\n\nAutomated checks reliably cover roughly 30–50% of the WCAG 2.1 AA success criteria — today's scanner tests 30 of the 50 criteria automatically, in full or in part.\n\nEvery report states which criteria were tested automatically and which require manual review, so you know exactly where a human needs to look. Paid reports include the full criteria matrix and a manual checklist.\n\nNo automated scanner can certify legal compliance — anyone claiming otherwise is overclaiming.\n\n[See all 50 criteria in plain language →](https://wexlo.eu/criteria)\n\nCoverage of 50 AA success criteria\n\n| Coverage | Criteria |\n| --- | --- |\n| 3 criteria — fully automated | 3 |\n| 27 criteria — partially automated | 27 |\n| 20 criteria — need human review | 20 |\n\n## No cookie banner. Nothing to accept.\n\nThis site sets no tracking cookies — our visitor statistics are cookieless. The only cookie we ever set is the strictly necessary sign-in cookie in the customer portal (and the only one we hand out comes with a coffee — in person ☕).\n\n[How we work without cookies →](https://wexlo.eu/faq#cookies)\n\nThe lane we're not in\n\n## Real findings, not an overlay\n\n### Overlay widgets\n\nInject a JavaScript layer and claim it makes your site compliant — the underlying code stays broken.\n\nIn April 2025 the FTC's final order against overlay vendor accessiBe (Docket No. C-4817, a $1M non-admission settlement) barred it from claiming its automated products can make websites WCAG-compliant without evidence.\n\n### Wexlo\n\nReports what is broken in your actual code and how to fix it there. Fixes get verified on the next scan — that's what makes it evidence.\n\nWe will never ship or recommend an overlay.\n\nIllustrative example — not from a customer site.\n\nThe deliverable\n\n## What lands in your inbox\n\nA tagged, accessible PDF plus an online report — evidence you can hand to a developer, an auditor, or an authority.\n\n-   Every finding with criterion, selector, fix guidance, and effort estimate\n-   The full 50-criteria matrix: tested, partially tested, needs review\n-   A draft accessibility statement for your site\n-   Scheduled re-scans that verify fixes stayed fixed\n\n## Plans\n\n[Monthly or yearly — pay yearly, get 2 months free](https://wexlo.eu/pricing?billing=year)\n\nOne website\n\n### Starter\n\n€49/mo\n\n-   1 domain\n-   Monthly automated scan\n-   Unlimited rescans\n\n[Choose Starter](https://wexlo.eu/pricing?plan=starter)\n\nUp to 5 domains\n\n### Growth\n\n€149/mo\n\n-   Up to 5 domains\n-   Weekly automated scans\n-   Unlimited rescans\n\n[Choose Growth](https://wexlo.eu/pricing?plan=growth)\n\nUp to 25 domains\n\n### Business\n\n€399/mo\n\n-   Up to 25 domains\n-   Daily automated scans\n-   Unlimited rescans\n\n[Choose Business](https://wexlo.eu/pricing?plan=business)\n\nFor agencies\n\n### Agency\n\nVolume pricing for agencies — request a quote.\n\n-   20+ domains\n-   Weekly automated scans\n-   Unlimited rescans\n\n[Talk to us](https://wexlo.eu/contact)\n\nThese cards show a few highlights per plan. The full comparison lists everything each subscription includes.\n\nAll prices exclude VAT · cancel monthly\n\n[Compare all plan details](https://wexlo.eu/pricing#compare) — or [start with a free scan](https://wexlo.eu/scanner).\n\n## Before you ask\n\n**Is a Wexlo scan an accessibility audit?**\n\nNo — and any automated tool that calls itself an audit is overselling. A scan is automated: it reliably covers roughly 30–50% of the WCAG 2.1 AA success criteria. An audit adds human judgment: keyboard flows, screen-reader testing, meaningful alt text, logical reading order. Every Wexlo report states which criteria were tested automatically and which need manual review, so an auditor can start from our evidence instead of from zero.\n\n**Does the European Accessibility Act apply to my business?**\n\nThe EAA (Directive (EU) 2019/882) has applied since 28 June 2025 to consumer-facing services in the EU — e-commerce is the broadest category: if consumers can buy products or services on your site, you are in scope. That includes non-EU companies selling to EU consumers. Purely B2B services fall outside it. Micro-enterprises providing services (fewer than 10 employees and ≤ €2M turnover) are exempt for services. Whether the law applies to your specific case is a question for your lawyer — what we can tell you is exactly what fails on your site.\n\n**Can I cancel anytime?**\n\nYes. Subscriptions run monthly and you can cancel from the portal with one click; access runs until the end of the period you already paid for. No annual lock-in, no cancellation call.\n\n[All questions →](https://wexlo.eu/faq)\n\nBuilt to pass AA\n\n## See what your site fails today\n",
  "fullPageMarkdown": "Wexlo — EU accessibility compliance scanning\n\n[Skip to content](https://wexlo.eu/#main)\n\nEAA · WCAG 2.1 AA · EN 301 549European Accessibility Act · WCAG 2.1 AA · EN 301 549\n\n# Find what fails.Fix it. Prove it.\n\nIn plain terms: the European Accessibility Act (EAA) is the EU law that requires the websites and apps consumers use — shops, banking, booking, streaming — to work for people with disabilities. It has applied since 28 June 2025, and it also reaches businesses outside the EU that sell to EU consumers.\n\nWexlo scans your site against WCAG 2.1 AA — the standard behind the European Accessibility Act — shows exactly which element fails and how to fix it, and turns every fix into audit-ready evidence.\n\nYour website\n\nScan free\n\nOne page, free · no account · results by email\n\nScan reportdemo-shop.example · 2026-07-06\n\nOne fix, proven\n\n2.9:1 · Fail\n\n→\n\n5.5:1 · Pass\n\n12Fail\n\n5Review\n\n41Pass\n\nTop finding\n\nWCAG 1.4.3 Checkout button label measures 2.9:1 against its background — normal text needs 4.5:1.\n\n`button.checkout-cta > span`●Critical · fix: darken the label to #5B6B77\n\nIllustrative example — not from a customer site.\n\nBuilt to pass AA — this site passes the same automated checks we sell. [See our accessibility statement](https://wexlo.eu/accessibility).\n\n## Choose where to start\n\n### Free quick scan€0\n\n1 page · instant · no account\n\n[Run a free scan](https://wexlo.eu/scanner)\n\n### One-off full report€79\n\nup to 100 reachable pages · no subscription\n\n[Order a one-off report](https://wexlo.eu/checkout/report_oneoff)\n\nNeed ongoing monitoring? [See subscriptions](https://wexlo.eu/pricing) (from €49/mo).\n\nEngine\n\nReal-browser scans\n\naxe-core plus Wexlo's own checks, desktop and mobile viewports\n\nCoverage\n\n30 of 50 AA criteria\n\nmachine-checked in full or in part — stated in every report\n\nLanguages\n\nUp to 4 languages\n\nEnglish, Nederlands, Français, Deutsch — by plan\n\nHosting\n\nEU-hosted\n\ninfrastructure primarily hosted and processed in the EU\n\nAnatomy of a finding\n\n## Every finding tells you exactly what to do\n\nNo score, no vague warnings. Each finding names the rule, the element, and the fix — in language your developer can act on today.\n\nFinding\n\nWX-0142\n\nCriterion\n\nWCAG 1.4.3\n\ncontrast, minimum\n\nFail●Critical\n\nWhat fails\n\nThe checkout button label measures 2.9:1 against its background — below the 4.5:1 required for normal text.\n\nElement\n\n`button.checkout-cta > span`\n\nFix\n\nDarken the gray — same design language, passing contrast:\n\n#9CA3AF · 2.9:1→#5B6B77 · 5.5:1Pass\n\nEffort\n\nS — under an hour, one CSS change\n\nIllustrative example — not from a customer site.\n\nThe path\n\n## From URL to evidence in four steps\n\n1.  1### You give us a URL\n\n    The free scan covers one page; on a paid plan we crawl up to 100 reachable pages per scan, on desktop and mobile viewports.\n\n2.  2### The rule engine scans\n\n    A real browser loads each page on desktop and mobile viewports, settles cookie banners and dynamic content, then runs axe-core plus Wexlo's own checks against WCAG 2.1 A and AA — the technical basis of EN 301 549.\n\n3.  3### Every finding becomes a fix\n\n    Per finding: the rule, the WCAG criterion, the CSS selector, a plain-language explanation, and a concrete fix suggestion.\n\n4.  4### You get evidence, on a schedule\n\n    Reports as HTML and PDF with a draft accessibility statement; scheduled re-scans verify that fixes stayed fixed.\n\nThe honest part\n\n## Honest about what a scanner can see\n\nAutomated checks reliably cover roughly 30–50% of the WCAG 2.1 AA success criteria — today's scanner tests 30 of the 50 criteria automatically, in full or in part.\n\nEvery report states which criteria were tested automatically and which require manual review, so you know exactly where a human needs to look. Paid reports include the full criteria matrix and a manual checklist.\n\nNo automated scanner can certify legal compliance — anyone claiming otherwise is overclaiming.\n\n[See all 50 criteria in plain language →](https://wexlo.eu/criteria)\n\nCoverage of 50 AA success criteria\n\n02550\n\n| Coverage | Criteria |\n| --- | --- |\n| 3 criteria — fully automated | 3 |\n| 27 criteria — partially automated | 27 |\n| 20 criteria — need human review | 20 |\n\n-   3 criteria — fully automated\n-   27 criteria — partially automated\n-   20 criteria — need human review\n\n## No cookie banner. Nothing to accept.\n\nThis site sets no tracking cookies — our visitor statistics are cookieless. The only cookie we ever set is the strictly necessary sign-in cookie in the customer portal (and the only one we hand out comes with a coffee — in person ☕).\n\n[How we work without cookies →](https://wexlo.eu/faq#cookies)\n\nThe lane we're not in\n\n## Real findings, not an overlay\n\n### Overlay widgets\n\nInject a JavaScript layer and claim it makes your site compliant — the underlying code stays broken.\n\nIn April 2025 the FTC's final order against overlay vendor accessiBe (Docket No. C-4817, a $1M non-admission settlement) barred it from claiming its automated products can make websites WCAG-compliant without evidence.\n\n### Wexlo\n\nReports what is broken in your actual code and how to fix it there. Fixes get verified on the next scan — that's what makes it evidence.\n\nWe will never ship or recommend an overlay.\n\nScan reportdemo-shop.example\n2026-07-06 · 5 pagesStarter · English\n\nIllustrative example — not from a customer site.\n\nThe deliverable\n\n## What lands in your inbox\n\nA tagged, accessible PDF plus an online report — evidence you can hand to a developer, an auditor, or an authority.\n\n-   Every finding with criterion, selector, fix guidance, and effort estimate\n-   The full 50-criteria matrix: tested, partially tested, needs review\n-   A draft accessibility statement for your site\n-   Scheduled re-scans that verify fixes stayed fixed\n\n## Plans[Monthly or yearly — pay yearly, get 2 months free→](https://wexlo.eu/pricing?billing=year)\n\nOne website### Starter\n\n€49/mo\n\n-   ·1 domain\n-   ·Monthly automated scan\n-   ·Unlimited rescans\n\n[Choose Starter](https://wexlo.eu/pricing?plan=starter)\n\nUp to 5 domains### Growth\n\n€149/mo\n\n-   ·Up to 5 domains\n-   ·Weekly automated scans\n-   ·Unlimited rescans\n\n[Choose Growth](https://wexlo.eu/pricing?plan=growth)\n\nUp to 25 domains### Business\n\n€399/mo\n\n-   ·Up to 25 domains\n-   ·Daily automated scans\n-   ·Unlimited rescans\n\n[Choose Business](https://wexlo.eu/pricing?plan=business)\n\nFor agencies### Agency\n\nVolume pricing for agencies — request a quote.\n\n-   ·20+ domains\n-   ·Weekly automated scans\n-   ·Unlimited rescans\n\n[Talk to us](https://wexlo.eu/contact)\n\nThese cards show a few highlights per plan. The full comparison lists everything each subscription includes.\n\nAll prices exclude VAT · cancel monthly\n\n[Compare all plan details](https://wexlo.eu/pricing#compare) — or [start with a free scan](https://wexlo.eu/scanner).\n\n## Before you ask\n\n**Is a Wexlo scan an accessibility audit?+−**\n\nNo — and any automated tool that calls itself an audit is overselling. A scan is automated: it reliably covers roughly 30–50% of the WCAG 2.1 AA success criteria. An audit adds human judgment: keyboard flows, screen-reader testing, meaningful alt text, logical reading order. Every Wexlo report states which criteria were tested automatically and which need manual review, so an auditor can start from our evidence instead of from zero.\n\n**Does the European Accessibility Act apply to my business?+−**\n\nThe EAA (Directive (EU) 2019/882) has applied since 28 June 2025 to consumer-facing services in the EU — e-commerce is the broadest category: if consumers can buy products or services on your site, you are in scope. That includes non-EU companies selling to EU consumers. Purely B2B services fall outside it. Micro-enterprises providing services (fewer than 10 employees and ≤ €2M turnover) are exempt for services. Whether the law applies to your specific case is a question for your lawyer — what we can tell you is exactly what fails on your site.\n\n**Can I cancel anytime?+−**\n\nYes. Subscriptions run monthly and you can cancel from the portal with one click; access runs until the end of the period you already paid for. No annual lock-in, no cancellation call.\n\n[All questions →](https://wexlo.eu/faq)\n\nBuilt to pass AA## See what your site fails today\n\nYour website\n\nScan free\n\nOne page, free · no account · results by email\n",
  "markdownStats": {
    "images": 0,
    "links": 11,
    "tables": 1,
    "codeBlocks": 0,
    "headings": 21
  },
  "tokens": {
    "htmlTokens": 40330,
    "markdownTokens": 1596,
    "reduction": 38734,
    "reductionPercent": 96
  },
  "score": {
    "score": 77,
    "grade": "B",
    "dimensions": {
      "semanticHtml": {
        "score": 93,
        "weight": 20,
        "grade": "A",
        "checks": {
          "uses_article_or_main": {
            "score": 100,
            "weight": 20,
            "details": "Has <main>"
          },
          "proper_heading_hierarchy": {
            "score": 100,
            "weight": 25,
            "details": "Clean heading hierarchy"
          },
          "semantic_elements": {
            "score": 67,
            "weight": 20,
            "details": "23 semantic elements, 91 divs (ratio: 20%)"
          },
          "meaningful_alt_texts": {
            "score": 100,
            "weight": 15,
            "details": "No images found"
          },
          "low_div_nesting": {
            "score": 100,
            "weight": 20,
            "details": "Avg div depth: 2.2, max: 7"
          }
        }
      },
      "contentEfficiency": {
        "score": 60,
        "weight": 25,
        "grade": "C",
        "checks": {
          "token_reduction_ratio": {
            "score": 100,
            "weight": 40,
            "details": "96% token reduction (HTML→Markdown)"
          },
          "content_to_noise_ratio": {
            "score": 0,
            "weight": 30,
            "details": "Content ratio: 4.1% (5933 content chars / 143566 HTML bytes)"
          },
          "minimal_inline_styles": {
            "score": 50,
            "weight": 15,
            "details": "11/590 elements with inline styles (1.9%)"
          },
          "reasonable_page_weight": {
            "score": 80,
            "weight": 15,
            "details": "HTML size: 140KB"
          }
        }
      },
      "aiDiscoverability": {
        "score": 55,
        "weight": 25,
        "grade": "D",
        "checks": {
          "has_llms_txt": {
            "score": 100,
            "weight": 20,
            "details": "llms.txt exists and is valid"
          },
          "has_robots_txt": {
            "score": 100,
            "weight": 10,
            "details": "robots.txt exists"
          },
          "robots_allows_ai_bots": {
            "score": 100,
            "weight": 15,
            "details": "All major AI bots allowed"
          },
          "has_sitemap": {
            "score": 100,
            "weight": 10,
            "details": "Sitemap found"
          },
          "supports_markdown_negotiation": {
            "score": 0,
            "weight": 25,
            "details": "No Markdown for Agents support detected"
          },
          "has_content_signals": {
            "score": 0,
            "weight": 20,
            "details": "No Content-Signal found (robots.txt or HTTP headers)"
          }
        }
      },
      "structuredData": {
        "score": 100,
        "weight": 15,
        "grade": "A",
        "checks": {
          "has_schema_org": {
            "score": 100,
            "weight": 30,
            "details": "JSON-LD found: Organization, WebSite, SoftwareApplication"
          },
          "has_open_graph": {
            "score": 100,
            "weight": 25,
            "details": "All OG tags present"
          },
          "has_meta_description": {
            "score": 100,
            "weight": 20,
            "details": "Meta description: 182 chars"
          },
          "has_canonical_url": {
            "score": 100,
            "weight": 15,
            "details": "Canonical URL present"
          },
          "has_lang_attribute": {
            "score": 100,
            "weight": 10,
            "details": "lang=\"en\""
          }
        }
      },
      "accessibility": {
        "score": 100,
        "weight": 15,
        "grade": "A",
        "checks": {
          "content_without_js": {
            "score": 100,
            "weight": 40,
            "details": "Content available without JavaScript"
          },
          "reasonable_page_size": {
            "score": 100,
            "weight": 30,
            "details": "Page size: 140KB"
          },
          "fast_content_position": {
            "score": 100,
            "weight": 30,
            "details": "Main content starts at 7% of HTML"
          }
        }
      }
    }
  },
  "recommendations": [
    {
      "id": "improve_content_ratio",
      "priority": "critical",
      "category": "contentEfficiency",
      "titleKey": "rec.improve_content_ratio.title",
      "descriptionKey": "rec.improve_content_ratio.description",
      "howToKey": "rec.improve_content_ratio.howto",
      "effort": "moderate",
      "estimatedImpact": 6,
      "checkScore": 0,
      "checkDetails": "Content ratio: 4.1% (5933 content chars / 143566 HTML bytes)"
    },
    {
      "id": "add_markdown_negotiation",
      "priority": "critical",
      "category": "aiDiscoverability",
      "titleKey": "rec.add_markdown_negotiation.title",
      "descriptionKey": "rec.add_markdown_negotiation.description",
      "howToKey": "rec.add_markdown_negotiation.howto",
      "effort": "significant",
      "estimatedImpact": 6,
      "checkScore": 0,
      "checkDetails": "No Markdown for Agents support detected"
    },
    {
      "id": "add_content_signals",
      "priority": "critical",
      "category": "aiDiscoverability",
      "titleKey": "rec.add_content_signals.title",
      "descriptionKey": "rec.add_content_signals.description",
      "howToKey": "rec.add_content_signals.howto",
      "effort": "quick-win",
      "estimatedImpact": 5,
      "checkScore": 0,
      "checkDetails": "No Content-Signal found (robots.txt or HTTP headers)"
    },
    {
      "id": "remove_inline_styles",
      "priority": "medium",
      "category": "contentEfficiency",
      "titleKey": "rec.remove_inline_styles.title",
      "descriptionKey": "rec.remove_inline_styles.description",
      "howToKey": "rec.remove_inline_styles.howto",
      "effort": "moderate",
      "estimatedImpact": 3,
      "checkScore": 50,
      "checkDetails": "11/590 elements with inline styles (1.9%)"
    }
  ],
  "llmsTxtPreview": "# Wexlo\n\n> Automated WCAG 2.1 AA scanning for EU markets: findings with code-level evidence, plain-language fixes, multilingual reports, and a draft accessibility statement. No overlay widgets.\n\n## Documentation\n- [FAQ](https://wexlo.eu/faq)\n\n## Main\n- [Wexlo — EU accessibility compliance scanning](https://Wexlo.eu): Automated WCAG 2.1 AA scanning for EU markets: findings with code-level evidence, plain-language fixes, multilingual re…\n- [Pricing](https://wexlo.eu/pricing)\n- [About](https://wexlo.eu/about)\n- [wexlo](https://wexlo.eu/)\n- [How it works](https://wexlo.eu/how-it-works)\n- [Customer portal](https://wexlo.eu/portal)\n- [NL](https://wexlo.eu/nl)\n- [Free scan](https://wexlo.eu/scanner)\n- [Verify a report](https://wexlo.eu/verify)\n- [Accessibility](https://wexlo.eu/accessibility)\n- [[email protected]](https://wexlo.eu/cdn-cgi/l/email-protection)\n\n## Legal\n- [Privacy policy](https://wexlo.eu/privacy)\n- [Terms & conditions](https://wexlo.eu/terms)\n\n## Support\n- [FAQ](https://wexlo.eu/faq)\n- [Contact](https://wexlo.eu/contact)\n\n",
  "llmsTxtExisting": "# Wexlo\n\n> Automated EU accessibility compliance scanning. Wexlo scans websites against WCAG 2.1 A/AA (the technical basis of EN 301 549 and the European Accessibility Act) using the axe-core rule engine, and delivers findings with code-level evidence, plain-language fix suggestions, multilingual reports (EN/NL/FR/DE), and a draft accessibility statement. No JavaScript overlay widgets.\n\n## What it does\n- Scans pages with a real browser (Playwright) and the axe-core rule engine against WCAG 2.1 A/AA.\n- Findings include the rule ID, WCAG criterion, impact level, and CSS selector of each affected element.\n- AI-generated plain-language explanations and concrete code fixes per finding; the rule engine decides what counts as a finding, the AI only explains.\n- Reports (HTML + PDF) and draft accessibility statements in English, Dutch, French, and German.\n- Scheduled re-scans: monthly (Starter), weekly (Growth/Agency), or daily (Business).\n- Free scan: one page, results by email, no account required.\n- Honest scope: automated checks cover roughly 30-50% of WCAG 2.1 AA success criteria; every report states which criteria require manual review. Automated scanning is not a certification of legal compliance.\n\n## Pricing (EUR, excl. VAT)\n- Starter: €49.00/mo — Monthly automated EAA/WCAG scan for 1 domain, full report with fix suggestions, accessibility statement draft.\n- Growth: €149.00/mo — Weekly scans, up to 5 domains, multilingual reports (EN/NL/FR/DE).\n- Business: €399.00/mo — Daily scans, up to 25 domains, multilingual reports (EN/NL/FR/DE).\n- Starter: €490.00/yr — Starter, billed yearly — 2 months free versus monthly.\n- Growth: €1490.00/yr — Growth, billed yearly — 2 months free versus monthly.\n- Business: €3990.00/yr — Business, billed yearly — 2 months free versus monthly.\n- Agency: €15.00/domain/mo (minimum 20 domains) — Per-domain pricing for agencies, minimum 20 domains.\n- One-time report: €79.00 (one-time) — One-off in-depth accessibility report for one website — full report with fix suggestions and a draft accessibility statement, in EN/NL/FR/DE. No subscription.\n\n## Key pages\n- Free scan: https://wexlo.eu/scanner\n- Pricing: https://wexlo.eu/pricing\n- Customer portal: https://wexlo.eu/portal\n\n## Company\n- Wexlo, KvK 66637694, VAT NL001677588B25, President Allendelaan 263, 1068 VM Amsterdam\n- Contact: [email protected]",
  "emergingProtocols": {
    "oauthDiscovery": {
      "exists": false,
      "url": "https://wexlo.eu/.well-known/oauth-authorization-server"
    },
    "mcpServerCard": {
      "exists": false,
      "url": "https://wexlo.eu/.well-known/mcp.json"
    },
    "a2aAgentCard": {
      "exists": false,
      "url": "https://wexlo.eu/.well-known/agent.json"
    },
    "count": 0
  },
  "snippets": [
    {
      "id": "add_content_signals",
      "title": "Add Content-Signal directives",
      "description": "Content-Signal tells AI agents how they may use your content. The canonical location is robots.txt, but you can also expose it as an HTTP header from any stack.",
      "language": "txt",
      "code": "User-agent: *\nContent-Signal: search=yes, ai-input=yes, ai-train=no",
      "filename": "/robots.txt",
      "stacks": [
        {
          "id": "robots",
          "label": "robots.txt",
          "language": "txt",
          "filename": "/robots.txt",
          "code": "User-agent: *\nContent-Signal: search=yes, ai-input=yes, ai-train=no"
        },
        {
          "id": "nginx",
          "label": "Nginx",
          "language": "nginx",
          "filename": "server block",
          "code": "# Inside your server { } block:\nadd_header Content-Signal \"search=yes, ai-input=yes, ai-train=no\" always;"
        },
        {
          "id": "apache",
          "label": "Apache",
          "language": "apache",
          "filename": ".htaccess",
          "code": "# In .htaccess (or VirtualHost):\nHeader set Content-Signal \"search=yes, ai-input=yes, ai-train=no\""
        },
        {
          "id": "wordpress",
          "label": "WordPress",
          "language": "php",
          "filename": "functions.php",
          "code": "<?php\n// In your theme's functions.php or a small mu-plugin\nadd_action('send_headers', function () {\n    header('Content-Signal: search=yes, ai-input=yes, ai-train=no');\n});\n\n// Optional: also append the directive to the dynamic robots.txt\nadd_filter('robots_txt', function ($output) {\n    return $output . \"\\nContent-Signal: search=yes, ai-input=yes, ai-train=no\\n\";\n}, 10, 1);"
        },
        {
          "id": "nextjs",
          "label": "Next.js",
          "language": "typescript",
          "filename": "middleware.ts",
          "code": "// middleware.ts (Next.js 13+ App Router or Pages Router)\nimport { NextResponse } from 'next/server';\nexport function middleware() {\n  const res = NextResponse.next();\n  res.headers.set(\n    'Content-Signal',\n    'search=yes, ai-input=yes, ai-train=no'\n  );\n  return res;\n}\nexport const config = { matcher: '/:path*' };"
        },
        {
          "id": "cloudflare",
          "label": "Cloudflare Workers",
          "language": "javascript",
          "filename": "worker.js",
          "code": "// Cloudflare Worker that proxies your origin and adds the header\nexport default {\n  async fetch(request, env, ctx) {\n    const res = await fetch(request);\n    const newRes = new Response(res.body, res);\n    newRes.headers.set(\n      'Content-Signal',\n      'search=yes, ai-input=yes, ai-train=no'\n    );\n    return newRes;\n  },\n};"
        },
        {
          "id": "express",
          "label": "Express / Fastify",
          "language": "javascript",
          "filename": "server.js",
          "code": "// Express\napp.use((req, res, next) => {\n  res.setHeader('Content-Signal', 'search=yes, ai-input=yes, ai-train=no');\n  next();\n});\n\n// Fastify\nfastify.addHook('onSend', (request, reply, payload, done) => {\n  reply.header('Content-Signal', 'search=yes, ai-input=yes, ai-train=no');\n  done();\n});"
        }
      ]
    },
    {
      "id": "add_markdown_negotiation",
      "title": "Support Markdown for Agents",
      "description": "Let AI agents request a clean Markdown version of any page via content negotiation, .md alternate URLs, link tags or Link headers.",
      "language": "html",
      "code": "<!-- Mechanism 3: link tag advertising the .md alternate -->\n<link rel=\"alternate\" type=\"text/markdown\" href=\"/page.md\">",
      "filename": "<head>",
      "stacks": [
        {
          "id": "html",
          "label": "HTML <head>",
          "language": "html",
          "filename": "<head>",
          "code": "<!-- Mechanism 3: link tag advertising the .md alternate -->\n<link rel=\"alternate\" type=\"text/markdown\" href=\"/page.md\">"
        },
        {
          "id": "express",
          "label": "Express",
          "language": "javascript",
          "filename": "server.js",
          "code": "// Mechanisms 1 + 4: content negotiation + Link header\napp.get('/page', (req, res) => {\n  res.setHeader('Vary', 'Accept');\n  res.setHeader('Link', '</page.md>; rel=\"alternate\"; type=\"text/markdown\"');\n  if ((req.headers.accept || '').includes('text/markdown')) {\n    res.type('text/markdown; charset=utf-8');\n    return res.send(renderMarkdown('page'));\n  }\n  res.render('page');\n});"
        },
        {
          "id": "fastify",
          "label": "Fastify",
          "language": "javascript",
          "filename": "server.js",
          "code": "// Mechanisms 1 + 4: content negotiation + Link header\nfastify.get('/page', async (req, reply) => {\n  reply.header('Vary', 'Accept');\n  reply.header('Link', '</page.md>; rel=\"alternate\"; type=\"text/markdown\"');\n  if ((req.headers.accept || '').includes('text/markdown')) {\n    return reply.type('text/markdown; charset=utf-8').send(renderMarkdown('page'));\n  }\n  return reply.view('/page.ejs');\n});"
        },
        {
          "id": "nextjs",
          "label": "Next.js",
          "language": "typescript",
          "filename": "app/page/route.ts",
          "code": "// Next.js App Router — Route Handler returning Markdown\nimport { NextRequest } from 'next/server';\nimport { renderMarkdown } from '@/lib/md';\nexport async function GET(req: NextRequest) {\n  const accept = req.headers.get('accept') || '';\n  if (accept.includes('text/markdown')) {\n    return new Response(await renderMarkdown('page'), {\n      headers: {\n        'Content-Type': 'text/markdown; charset=utf-8',\n        'Vary': 'Accept',\n      },\n    });\n  }\n  // Fall through to the page component\n  return new Response(null, { status: 404 });\n}"
        },
        {
          "id": "wordpress",
          "label": "WordPress",
          "language": "php",
          "filename": "functions.php",
          "code": "<?php\n// Mechanism 1: respond to Accept: text/markdown on the same URL\nadd_action('template_redirect', function () {\n    if (!is_singular()) return;\n    $accept = $_SERVER['HTTP_ACCEPT'] ?? '';\n    if (strpos($accept, 'text/markdown') === false) return;\n    header('Content-Type: text/markdown; charset=utf-8');\n    header('Vary: Accept');\n    $post = get_queried_object();\n    echo \"# \" . get_the_title($post) . \"\\n\\n\";\n    echo wp_strip_all_tags(apply_filters('the_content', $post->post_content));\n    exit;\n});"
        },
        {
          "id": "static",
          "label": "Hugo / Jekyll / Astro",
          "language": "txt",
          "filename": "static/page.md",
          "code": "# Mechanism 2: serve .md alongside .html\n# Hugo: place page.md in /static/ — built unchanged\n# Jekyll: drop page.md in /assets/ — copied as-is\n# Astro: src/pages/page.md.ts that exports a GET returning markdown\n\n# Then advertise with mechanism 3 in <head>:\n#   <link rel=\"alternate\" type=\"text/markdown\" href=\"/page.md\">"
        }
      ]
    }
  ]
}

Use our API to get this programmatically (coming soon)

This JSON is for internal use — unlike the Markdown and llms.txt files, it's not meant to be uploaded to your site. Save it as a baseline to track your score over time, share it with your dev team, or integrate it into your CI/CD pipeline.

Want a second opinion?

Cloudflare runs a free scanner too, and it asks a different question. It scores what your site publishes for agents to call — MCP server cards, Agent Skills, API catalogs, DNS records. We score whether an agent can reach, read and understand your content. A site can do well on one and poorly on the other, so expect two different numbers: they are answers to two different questions, and both are worth knowing.

Scan wexlo.eu with Cloudflare

Embed your badge

Add this badge to your site. It updates automatically as your AI-readiness score changes.

AgentReady.md score for wexlo.eu
Script Recommended
<script src="https://agentready.md/badge.js" data-id="32084923-e8bc-4a82-a694-75c55842ba62" data-domain="wexlo.eu"></script>
Markdown
[![AgentReady.md score for wexlo.eu](https://agentready.md/badge/wexlo.eu.svg)](https://agentready.md/r/32084923-e8bc-4a82-a694-75c55842ba62)

Coming soon: Full Domain Analysis

Crawl your entire domain, generate llms.txt, and monitor your AI-readiness score over time. Join the waitlist to be notified.

You're on the list! We'll notify you when it launches.