WCAG Radar: 50 accessibility checks in your own browser

Free · 29 of the 50 checks

WCAG Radar is free tooling from accessibility audit agency Proper Access: 29 of its 50 WCAG checks on the page you have open, including behind a login and on localhost. Not sure what a finding means? Every check has a link straight to an auditor.

That is where you manage your licence, hand seats to colleagues and put a question to an auditor.

runs locally
no account
works on localhost
sends nothing

Install the Radar

WCAG Radar
Drag it to your bookmarks bar
Install for Chrome (opens in a new tab)
Edge, Brave and Vivaldi too
Install for Firefox (opens in a new tab)
Windows, macOS and Linux
Get my key
Licence through work? Sign in with your work address

Don't click it, drag it. No bookmarks bar in sight? Press CtrlShiftB on Windows, or ⌘⇧B on Mac. After that you click it on any page you want to test.

Four ways to install the Radar

All four run the same checks and carry the same version number. The bookmarklet installs nothing, so it also works on a computer where you are not allowed to install anything. The three extensions put a button next to your address bar and also work on sites that block a bookmarklet, such as Google Docs. You are welcome to install them side by side.

Bookmarklet
Bookmarks bar
- installs nothing, so it works on a work computer where you may not install anything
- works on someone else's computer, during a workshop for instance
- a site with a strict Content Security Policy blocks it; take an extension there
WCAG Radar
Drag it to your bookmarks bar. Clicking it here does nothing.
Chrome
Chrome Web Store
- also works in Edge, Brave and Vivaldi
- Windows, macOS and Linux
- the browser keeps it up to date
Install for Chrome (opens in a new tab)
Firefox
Firefox Add-ons
- Windows, macOS and Linux
- the browser keeps it up to date
Install for Firefox (opens in a new tab)
Safari
App Store
- macOS only
- without the paid checks: Apple requires In-App Purchase for paid features, and that leaves us unable to send an organisation an invoice
Submitted to Apple and under review. The button appears here once it is approved.

The stores can lag a version behind: Chrome, Firefox and Apple review every new version first. The bookmarklet fetches its bundle from us, so it is always current.

Stuck on a finding? Put it to an auditor.

Every check in the panel carries a link to an expert. It takes you to the Proper Access audit portal, with the tab, the theme, the check and the page you were on already filled in. The question itself is yours to write: what you are unsure about and what you already tried. A senior auditor answers it.

One credit is one question about one subject. Follow-up questions in that same conversation cost nothing extra.
You get an answer within 3 to 5 working days.
The credit is only spent when we answer. If your question falls outside what we can answer, it costs you nothing.
No licence needed. Anyone can buy credits, including without an audit from us.

A question costs one credit: one question on one topic. How it works and what a bundle costs

Ask your question in the portal

You log in with your own email address.

One tool. Your licence decides how many checks run.

All 50 checks ship inside it. Without a licence 29 of them run, spread across all three tabs. Those 29 stay free, including when we add more checks later. Checks marked Pro stay visible, so you can see what else is there. In the extension you enter your key once, on the options page; you get it by email from whoever manages the licence.

See the pricing

29/ 50

checks free, no account

freewith a licence

Checks are added every month. Everything we add is part of the licence.

Bookmarklet with every check

Paste your licence key and we build you a bookmarklet here with every check switched on. Useful at a workplace where you are not allowed to install extensions.

Your key goes nowhere from here: it is put into the bookmarklet inside your own browser. If the seat is withdrawn later and you get a new key, drag the button again.

One tool, three tabs

At the top of the panel you switch between Content writer, Designer and Developer. Each tab has its own set of checks, matched to the work you actually do.

Content writer: what the Radar shows you

Alt text, headings, link text, tables and language. Plus “styling off”: all design stripped away, so you read your own page in the order a screen reader walks through it.

Page title: Shows the title of the page. A clear, unique title helps visitors tell tabs and search results apart.
Styles off (reading order): One click turns all styling off: no colours, no columns, no images in place. You are left with the bare text, in the order screen reader software goes through it. Read it that way. Does your story still hold up, or does the answer suddenly come before the question?
Page structure Pro: How the page is built up, as a clickable list: the areas (menu, main content, sidebar), the headings, the links, the buttons and the form fields, in the order they appear in the code. Read the list from top to bottom. Does it tell you what the page is about and what you can do there? Click a row to jump to that spot on the page.
Show hidden parts Pro: Some parts are in the page but you cannot see them. Often that is fine, such as a menu that only opens when you click it. Sometimes it is a mistake, and then screen reader software reads out something that should be gone, or the same thing twice. WCAG Radar makes those hidden parts visible and notes how they were hidden. Check whether anything is in there that should have been removed long ago.
Headings and structure: The Radar draws every heading with its level and warns when you skip a level. A logical heading structure helps everyone who scans the page or has it read aloud.
Heading quality Pro: Marks empty headings and headings with uninformative text such as “Go to” or “Read more”. Anyone navigating by headings should be able to tell from the heading what the section is about.
References to place, colour or shape: Marks references to position and shape, such as “top left” or “the round button”, and every colour name, including inside alt text. For each one you decide whether the text still makes sense to someone who cannot see where things are or what colour they have.
Difficult language: WCAG Radar flags long sentences, words from our list of difficult words and sentences in the passive voice, and reports the average number of words per sentence. Meant for anyone writing in plain language. The Radar does not hand out a level: reading level is a WCAG AAA criterion, and a level such as B1 describes a reader rather than a text.
Line breaks used as layout Pro: Two blank lines in a row look like space between two paragraphs. To screen reader software it is one long paragraph: you cannot move through it paragraph by paragraph and the short pause between paragraphs is gone. Lines that start with a dash or a bullet are a list in disguise, so they do not count as a list either. WCAG Radar flags both. Single line breaks, as in an address or a poem, are left alone.
Strong emphasis (strong) Pro: WCAG Radar marks every piece of text with strong emphasis, the strong element. Strong emphasis means: this matters. It is not a way to make letters thicker, that is a styling choice. When a whole sentence or a whole paragraph sits inside it, the emphasis lands on everything and therefore on nothing, so those get flagged. Save emphasis for the word or few words that carry the point.
Emphasis (em) Pro: WCAG Radar marks every piece of text with emphasis, the em element. Emphasis puts the stress on a word, the way your voice does in conversation. It is not a way to slant letters, that is styling. A whole sentence or a whole paragraph in emphasis gets flagged, because then you can no longer hear where the stress falls.
List structure: Marks real lists, so you can see whether bullet points are actually marked up as lists rather than loose lines with dashes.
Images and alt text: Every image needs alt text: the words someone hears or reads instead of the picture. WCAG Radar shows you what is there for each image. There are three possibilities: there is alt text, the alt text is deliberately empty because the image is decoration only, or there is nothing at all. That last one is an error. You also get a warning when your alt text starts with “image of”; you do not need that, because screen reader software already says it is an image. What the text should say is your call: only you know whether the picture tells the reader something or just looks nice. Drawings that live in the page itself (svg) are included.
Clickable images: Sometimes an image is itself a link or a button, such as a logo that takes you to the home page. It then needs a name that says where you end up or what happens, not what the picture looks like. So “To the home page”, not “round blue logo”. WCAG Radar shows that name for every clickable image and flags it in red when there is none.
Images off: All imagery is blurred: photos, drawings, videos and background images. A dotted outline stays where each one was, so you can see what you are missing. Now read the page again. Does the story still make sense without the imagery? If not, there is information in the picture that belongs in the text as well. Note: a logo is often a drawing inside the page itself, so it blurs along with the rest.
Tables Pro: Marks tables without header cells or a caption. Header cells tell assistive software which row or column a cell belongs to. A caption gives the table a title.
Names of links and buttons: Every link, button and form field has a name that screen reader software reads out. Usually that is simply the text you can see, but not always: for a button with only an icon, a magnifying glass say, the name sits in the code. WCAG Radar puts that name on screen for every element. That shows you whether someone who cannot see the page gets the same information you do. Links, buttons and fields without a name are flagged in red.
Link text: Marks vague links such as “read more” and links without text. Good link text tells you on its own where you will end up.
All links Pro: All links on the page in a single list in the panel, the way a screen reader announces them: just the link text, without surrounding context. Empty and vague texts stand out. Click a row to jump to that link on the page.
Links that open a new tab Pro: When a link opens a new tab, there is often a small icon after it: two overlapping windows, or an arrow pointing to the top right. That icon is the warning, and anyone listening to the page never sees it. WCAG Radar finds the links that carry such an icon and checks whether the announcement also exists in text. Links without an icon are left alone: that is the site’s own choice, not a defect.
Titles on embedded videos and maps Pro: A YouTube video or a Google map sits in a small frame that comes from another website. That frame needs a title, so that someone having the page read aloud knows what is inside it. Without one, all they hear is that there is “a frame”. WCAG Radar flags the frames without a title.
Page in shades of grey: One click turns the page grey. Check that information such as links or error messages is still recognisable without colour.
Text contrast: Text has to stand out enough from its background, otherwise it is unreadable for anyone who sees less sharply or is looking at a screen in bright sunlight. WCAG Radar automatically flags text that does not stand out enough from a plain background. When the text sits on a photo or a colour gradient, you measure it yourself: click the colour of the letters first, then the colour of the background. You see straight away whether it is enough. Large text has a lower requirement than small text, and the Radar works that out for you.
Contrast of input fields and focus: This is not about text but about the things around it: the border of an input field, and the outline that appears when you move through the page with the Tab key. Those have to stand out from the background too, otherwise you cannot see where to type or where you are. WCAG Radar walks the page and reports when the difference is too small, or when no outline appears at all. Fixing it is usually up to the designer or the developer, but it helps to know it is there.
Page language: See whether the page language is set and which parts have their own language. The right language makes a screen reader pronounce words correctly.
Language of parts Pro: When a piece of text is in a different language from the page, the code needs to say so. Without that, a screen reader reads an English sentence with the sounds of the page language, and what comes out is nonsense. WCAG Radar marks the pieces of text that look like they are in another language than the page itself. It guesses that language from common words, so a quotation, a brand name or a short heading can throw it off: look for yourself before you change anything.
Filling in details automatically Pro: A browser can fill in fields like name, address and email address by itself, using details the visitor saved earlier. For that to work, the code has to say what kind of detail belongs in the field. When it does, it saves typing, which helps people who find typing hard or who forget things quickly. WCAG Radar shows you per field whether it is there and warns when it is missing. Changing it is a developer's job.
Labels on input fields: Every input field needs a label: the word next to it that says what to fill in, such as “Email address”. Screen reader software announces that label as soon as someone lands in the field. Without one, all they hear is “input field” and they have no idea what to type. WCAG Radar flags those fields in red. Watch out for fields where the wording only sits inside the field as pale grey example text: that text disappears the moment you start typing, so you can no longer check what was being asked. Those get a warning. Visible text beside a field does not count by itself either; it has to be tied to the field in the code. So if it looks right but is flagged anyway, pass it on to a developer.
Error messages on form fields: Fill a form in wrongly and submit it. WCAG Radar then marks every error message that appears and lists them together, so you can read them side by side. You judge the wording: does it say what went wrong and what the visitor should do, or only “invalid input” or an error code? Name the thing itself, for example “Your postcode has four digits and two letters, like 1234 AB” instead of “Wrong format”. Messages that are not linked to their field get a red marker: someone using a screen reader never hears those, however good your wording is. Fixing that is a developer's job, but do pass it on.

Designer: what the Radar shows you

Measure contrast, take colour away, force focus into view, point out targets smaller than 24 by 24 pixels, and see what breaks at 200 percent text.

Text contrast: Automatically marks text on a solid background with insufficient contrast. For text on a photo or gradient you measure two colours yourself with the two pickers. You immediately see the contrast ratio and whether it meets the requirement for normal and large text. A glyph from an icon font is a drawing, not text: the Radar measures those separately against the 3:1 requirement.
Contrast of borders and focus: Measures the contrast of input field borders and of the focus style (WCAG 1.4.11). The Radar briefly focuses each element and warns below 3:1, or when a visible focus style is missing entirely.
Links by colour alone: Finds links in running text that are distinguished from the text by colour alone (no underline) and shows the colour difference with the surrounding text. Underlining is the safest fix.
Colours on this page Pro: WCAG Radar lists every colour the page uses in the side column: as text, as a fill and in borders, with the hex code, how often it occurs and a swatch to see it. Click a line to jump to the first element that uses it. Below the list are the text-on-background combinations with the measured contrast, as far as the background is solid.
Colour that carries meaning Pro: WCAG Radar looks for the places where colour carries information: a legend (two or more colour swatches with a label next to them), a chart, a map and a canvas. They appear in the side column with their swatches. The Radar does not say whether it is right or wrong, because a tool cannot see that: a legend with four colours is fine as long as the lines also carry a label or a pattern. You judge whether the same information is visible without colour.
Grayscale (colour-blindness check): One click turns the page grey. Check that information such as links or error messages is still recognisable without colour.
Dark mode Pro: Force-applies the site's own dark mode (the prefers-color-scheme: dark styles), so you can check contrast and readability in dark mode. If the site has no dark mode styles, the Radar says so honestly.
Make focus visible: The Radar forces a clear focus outline. Tab through your design to see whether every interactive layer has visible focus.
Target size (24px) Pro: Every clickable element shows its dimensions; elements smaller than 24 by 24 pixels get an orange mark. Note: a small target can still pass, for example a link within a sentence or a target with enough space around it. Use the marks as a starting point.
Gestures and mouse-only controls Pro: Marks elements that can only be operated with a mouse or touch: script-clickable elements without keyboard focus, drag and drop without a clear alternative, and fake buttons with only a mouse cursor.
Resize text only (200%): The Radar sets all text to 200%, the way a visitor with low vision would. Check whether text disappears, overlaps or falls off screen, and whether everything still works.
Page zoom 200%: Shows the page the way someone sees it with their browser at 200%. A normal-sized window holds a frame of half the width, scaled up twice. Inside that frame the same media queries and the same reflow apply as with real browser zoom, and the text really is the size your visitor gets. You do not have to zoom anything yourself, so the Radar stays where it is.
Zoom blocked in the code Pro: Reads the page's viewport meta tag. If it carries user-scalable=no or a maximum-scale below 2, people cannot zoom to 200 percent on a phone (WCAG 1.4.4). The check names the value that blocks it; that value can go, the tag itself can stay.
Text spacing (1.4.12): Applies the WCAG text spacing values. Check whether text disappears, overlaps or is cut off when a visitor increases the space between letters and lines.
Reflow (320 px): Checks for horizontal scrolling at page level, marks the elements extending off screen, and shows the same page at 320 pixels wide in a side column (WCAG 1.4.10).
Images off: Images are dimmed. Check whether your design still makes sense without imagery and whether the text can carry the story on its own.
Automatic motion Pro: Finds motion that starts by itself and lasts longer than 5 seconds: CSS animations, autoplay videos and marquees. The Radar also watches script-driven motion, such as carousels and tickers, for 5 seconds.
Ruler and guides: A horizontal and vertical guide follow your mouse and show the x and y position in pixels, so you can verify alignment and distances precisely.

Developer: what the Radar shows you

ARIA, accessible names, tab order and iframes.

Element info on hover: Move your mouse over the page and get a card per element showing what assistive technology makes of it: the accessible name and where it comes from, the role, the heading level, whether you can reach it with Tab, states such as hidden, disabled or required, and, where the background is reliably measurable, the text contrast with colour swatches. The card deliberately leaves out classes and ids: they say nothing about accessibility and push the lines that do matter out of view. Also works in embedded frames from the same domain; frames from other domains are technically out of reach.
Show accessible name: Every interactive element (links, buttons, form fields) shows its accessible name: the name a screen reader announces. Elements without a name are marked as errors.
ARIA roles and attributes: Shows all roles and aria attributes and marks four kinds of errors: broken references to non-existent ids, unknown roles (typos), roles missing a required attribute (such as checkbox without aria-checked), and aria-hidden on focusable content. Below the result you get links to the ARIA reference, to look up what a role requires, and to the quiz for developers.
Iframes (title): Iframes without a title or aria-label stand out. A title is needed so a screen reader user knows what is inside the frame.
Autocomplete on personal data Pro: Fields asking for personal data should have an autocomplete attribute with a valid value (WCAG 1.3.5). The Radar shows the value per field and warns about missing or unknown values.
Groups and visible labels: Fieldsets without a legend and groups (role=group) without a name are marked as errors. You also see which fields only have an aria-label and no visible label. That is sometimes fine, for example a magnifying glass icon on a search field, but usually visible text belongs there.
Accessible names of form fields: Marks input fields without an accessible name and fields that only have a placeholder. Visible text next to a field only counts when it is linked to the field via <label for>, aria-label or aria-labelledby.
Required fields: Shows which fields are marked as required for assistive software (required or aria-required) and warns about fields with an asterisk or 'required' in the label that lack this marking.
Error messages on form fields: The Radar looks for visible error messages in four ways: role=alert or aria-live, a class or id like error/invalid, a field that points at the message itself (aria-errormessage, or aria-describedby on a field set to aria-invalid="true"), and red text right next to an input. That last one catches sites whose framework emits numbered class names and no ARIA at all; the summary tells you how many messages were recognised by colour alone. Unlinked messages are an error: a screen reader will not announce them. Linked messages without aria-invalid="true" on the field get a warning, and a field that is set to aria-invalid="true" without a linked message gets an error.
Paste blocked Pro: Marks elements that block pasting, copying or dragging via inline code (onpaste, oncopy, oncut, ondrop). Blocked pasting forces retyping and is a barrier, for example with passwords and email confirmations. Blocks added through scripts are invisible to the Radar; also test pasting yourself.
Make focus visible: The Radar forces a clear focus outline on every element. Tab through the page to see whether focus is always visible and moves logically.
Tab order Pro: Every focusable element gets a number in the order you reach it with Tab. Positive tabindex values jump ahead of the rest and are marked as errors, because they disturb the logical keyboard order.
Target size (24px) Pro: Every clickable element shows its dimensions; elements smaller than 24 by 24 pixels get an orange mark. A small target can still pass, for example a link within a sentence.
Gestures and mouse-only controls Pro: Marks elements that can only be operated with a mouse or touch: script-clickable elements without keyboard focus, drag and drop without a clear alternative, and fake buttons with only a mouse cursor.
Resize text only (200%): The Radar sets all text to 200%, the way a visitor with low vision would. Check whether text disappears, overlaps or falls off screen, and whether everything still works.
Page zoom 200%: Shows the page the way someone sees it with their browser at 200%. A normal-sized window holds a frame of half the width, scaled up twice. Inside that frame the same media queries and the same reflow apply as with real browser zoom, and the text really is the size your visitor gets. You do not have to zoom anything yourself, so the Radar stays where it is.
Zoom blocked in the code Pro: Reads the page's viewport meta tag. If it carries user-scalable=no or a maximum-scale below 2, people cannot zoom to 200 percent on a phone (WCAG 1.4.4). The check names the value that blocks it; that value can go, the tag itself can stay.
Text spacing (1.4.12): Applies the WCAG text spacing values: line height, letter and word spacing and paragraph spacing. You immediately see whether text disappears, overlaps or is cut off.
Reflow (320 px): Checks for horizontal scrolling at page level, marks the elements extending off screen, and shows the same page at 320 pixels wide in a side column (WCAG 1.4.10).
Text contrast: Automatically marks text on a solid background that drops below 4.5:1 (normal text) or 3:1 (large text). A character from an icon font sits in a text node but is a drawing: it is measured against 3:1 (non-text content) and counted separately in the summary. For text on an image or gradient you measure two colours yourself with the two pickers.
Contrast of borders and focus: Measures the contrast of input field borders and of the focus style (WCAG 1.4.11). The Radar briefly focuses each element and warns below 3:1, or when a visible focus style is missing entirely.

What these checks are based on

Every check measures one or more WCAG 2.2 success criteria at level A and AA. The panel says what each check covers and links to the explanation. The standard itself is public and free to read, and for the European Accessibility Act it applies through the European standard EN 301 549.

Questions about WCAG Radar

What does WCAG Radar cost?

29 of the 50 checks are free and stay free, with no account and no trial period. The other 21 and the report export need a licence: € 119 per year or € 11,95 per month for one person, excluding VAT. Teams pay per seat on a scale that gets cheaper as you take more.

Does the Radar work behind a login or on localhost?

Yes. Every check runs in the browser you already have open, on the page that is in it at that moment. No server of ours has to reach your page, so a staging server, a test environment and localhost all work as well as a live site.

Does anything from my page reach your servers?

No. The checks run locally and the report is written in your own browser. We only count how often the bundle is fetched per day, with no IP address and no cookie. What you test stays with you, which is exactly why it is usable behind a login.

What is the difference between WCAG Radar and the scan?

The Radar tests one page at a time, in your own browser, and marks the problems in the page itself while you work on it. The scan walks up to 10 pages of a public address and emails you a report with a score. The Radar is for while you build, the scan for a first picture of a whole site.

Which browsers does it work in?

The extension is in the Chrome Web Store and on Firefox Add-ons; a Safari version is in preparation. The bookmarklet works in any browser with a bookmarks bar, including Safari and Edge, and is the route for anyone who is not allowed to install software at work.

Does the Radar replace a manual audit?

No, and it is not meant to. An automated check finds 30 to 40 percent of the problems on a page. The Radar helps you fix that part yourself before an auditor looks at it, so an audit report is about the hard cases instead of about buttons without a name.

What it costs

The browser extension and the bookmarklet stay free, with 29 checks, no account and nothing sent anywhere. If you want all 50 checks or a report from your test session, there is a licence.

All amounts exclude VAT. This is a tool you use for work, so you reclaim the VAT. If you buy as a private individual, you see the price including VAT at checkout.

Where we are now

29 checks are free and will stay that way. 21 checks need a licence: you still see them in the panel, with a link back to this page. You enter your key in the extension; the bookmarklet for licence holders comes with it. On 4 August 2026 we fixed something that was wrong: the extension wiped your key the moment our server said no once, and that also happened when a subscription was renewed a day late. One administrative hiccup and everyone at that office lost their key, with no way back, because all we keep of a key is a fingerprint. The key now stays put and everything works again by itself once the problem is resolved.

Free, and staying that way

The browser extension for Chrome, Firefox and soon Safari. This part will never be locked.

€ 0

Install the Radar

29 checks for content, design and code
No account, no sign-up
Everything runs in your own browser, nothing is sent
Asks for no access to the sites you visit

Most chosen

Personal licence

For the freelance auditor, developer or editor.

€ 119per year

€ 11,95 per month

Paying monthly costs more per year than paying at once. Twelve payments simply cost us more than one.

Buy a personal licence

Every check in the extension
The same bookmarklet, but with every check in it
Report export from your test session
Support: if something does not work properly, we change the tool
In your own name, paid by card or iDEAL

What it does not include

No invoice on account and no purchase order number
No VAT reverse charge
No handing out seats to colleagues
Not transferable to someone else

Organisation subscription

For teams. From two seats up, handed out by you in the portal.

from€ 350per year

Buy seats for your team

Everything in the personal licence, for everyone with a seat
Hand out and withdraw seats whenever you want
Support for everyone with a seat, not just the administrator
One invoice a year, with a purchase order number
VAT reverse charged with a valid VAT number outside the Netherlands

The scale

Price per seat per year. More seats, lower rate.

The scale
Seats	Per seat per year	Example
2 to 4	€ 175	3 seats: € 525
5 to 9	€ 150	8 seats: € 1.200
10 to 19	€ 130	12 seats: € 1.560
20 to 49	€ 110	25 seats: € 2.750
50 or more	€ 90	60 seats: € 5.400

You never pay more than the entry total of a higher tier. Nine seats therefore cost the same as ten.
You can add seats mid-term, in proportion to the time left in your year. You arrange that yourself in the portal.
You can cancel at renewal. Reducing seats also happens at renewal.
Have a personal licence and want to add colleagues? Whatever is left of your year comes off the price.

What does it cost for you?

Number of seats

€ 1.200per year, excluding VAT

That works out at € 150 per seat.

What a licence gets you

The free extension keeps doing exactly what it does now. A licence opens this up on top of it.

Every check: The extension gives you 29 checks for free. A licence unlocks all 50. And that is not the end of it: the Radar is under active development, we add checks every month, and every check we add is part of the licence.
The bookmarklet with everything in it: A button in your bookmarks bar that works on any page, including behind a login and on localhost. Built for managed workplaces where IT allows no extensions, which at government bodies and large retailers is the rule rather than the exception. Note: on sites with a strict Content Security Policy the bookmarklet is blocked and the extension is not.
Report export: Your test session as a report, per element: which checks you had on, the summary per check, and per finding the status, a pointer to the element and the text it contains. One HTML file that opens anywhere and prints to PDF, built in your own browser. Not a conformance statement, but something your team can act on.
Support from the people who build it: Does a check misbehave, flag something that is not true, or miss something you expected? Tell us and we change the tool. You talk to the auditors who wrote the Radar, not to a helpdesk that passes you on. We read what free users send us too, and the Radar grew up on it. What a licence adds: you get a reply, and your report goes first.

Workshops

A day with your team, using your own site. Twelve participants at most. Separate from the licence.

€ 1.950 per day

Ordering a licence

Log in with your email address, fill in your organisation's details and pick your licence. You pay by card or iDEAL and get the invoice by email straight away. Prefer to pay on account or against a purchase order? Email us and we will sort it out.

Signing in is the first step of the checkout. You create an account, pick your licence and pay, all in one go. There is no sales call in between.

What's new

v2.46.12 · 12 September 2026

Colour that carries meaning now also finds a line chart: there the colour sits on the line instead of in the fill, and that is exactly the chart a legend belongs to. An element with the Dutch word for card in its name no longer counts as a map.

The Radar now runs version 2.46.12, released on 12 September 2026. You never need to reinstall: the bookmarklet fetches the latest version itself, within an hour of an update. The version you are running is shown at the bottom of the panel.

See every change, per version

Buy your licence right now.

A personal licence costs € 11,95 a month or € 119 a year, excluding VAT. You arrange it yourself: sign in with your email address, pick a licence, pay by card or iDEAL. The key and the invoice are in your inbox within a minute. Teams pay per seat on a sliding scale.

Turn on every check

Buy a licence See the pricing

The Radar is not a replacement for an audit.

WCAG Radar helps you find and fix the most common problems yourself. For a full audit, with findings per element, user stories and concrete solutions, you end up at Proper Access.

From here Proper Access takes over

Request a quote

Free accessibility scan

Give us a URL and get a report back within 90 seconds. axe-core 4.11 in a real Chromium browser, multi-page crawl, overlay detection.

Also on this site

Go to the scanner

Last updated: 7 August 2026