Beacon audits your pages for accessibility, content, and discoverability against a versioned policy library — then shows the specific fix for each finding: the copy to paste, or the markup to change.
A Chrome side panel for the page you're on, and a portal at beacon.kandr.io/app for the whole site.
The tools Beacon replaces stop at the flag: “image missing alt text,” “title too long.” Beacon keeps going — to the sentence you should write and the attribute you should add.
Open the Chrome side panel on any page — production, staging, or behind a login — and Beacon reads it as it actually renders, then scores it in seconds.
Add a site and Beacon discovers its pages from the sitemap, renders each one in a real browser, and re-crawls only what changed.
Every finding comes with its rendition: a copy change you can paste into the CMS, or a code change against the markup Beacon actually saw.
Each page gets a 0–100 score with a green, amber, or red band, per category and overall — so a product owner knows where to look first.
Write your content guide once. Its criteria become judged checks, and your term list becomes exact ones — so “sign in, never log in” is enforced on every page.
Send a finding to Linear or Jira with the evidence, the fix, and the page already in the brief. Beacon checks for an open ticket first so nothing files twice.
Three findings from one audit, as the side panel shows them. Each names the problem, shows the evidence, and hands over the change.
A screen reader announces this as “button” and nothing else.
212 → 86 characters. Search results cut off past ~155.
The finding you see in the side panel is the same record the portal scores, the crawl re-checks, and the ticket links back to.
On the page you're reviewing, click Beacon. Grant access to that site once and it stays granted.
Beacon reads the rendered page — text, markup, contrast, layout shift, consent behavior — and checks it against the policy library.
Copy the replacement text, or hand the code change to whoever owns the template. Dismiss what doesn't apply, with a reason.
Add the site in the portal and the crawler keeps every page scored, so a regression shows up before a customer finds it.
Every check has an id, a severity, and a version, so a score from last month means the same thing as a score from today. Turn checks off, tune severities, or add your own through the content guide.
axe-core rules mapped to WCAG success criteria, plus contrast, alt text, and screen-reader tools.
The things that slip through review: placeholder copy, template tokens, thin pages, stale years.
Titles, descriptions, canonicals, Open Graph, and structured data — how the page looks everywhere but the page.
Measured at runtime: what sets cookies and loads trackers, and whether it waited for consent.
Layout shift, legible type sizes, and line height, measured as the page actually runs.
Your content guide's criteria and term list, composed into checks that run alongside everything else.
The full detail is in the privacy policy. The short version:
Beacon never records the address of a page you didn't audit and never reads a page's content unless you run an audit on it. No browsing history.
Sites, findings, guides, and dismissals belong to a workspace, and permissions are enforced on the server. Tracker and repo tokens are stored encrypted.
Page content is used to produce your findings and nothing more. It isn't sold, isn't shared with ad networks, and isn't used to train models.
Still unsure? Ask us directly — Kandr audits its own sites with Beacon, so the answers come from using it.
Those tools tell you what failed. Beacon covers the same ground — and content, privacy, and brand checks they don't — and then writes the change: replacement copy, or the markup edit on the element it found.
Yes. The side panel audits whatever is open in your browser, including pages you're signed in to. The crawler covers public pages it can reach from a sitemap.
No. Dismiss a finding with a reason and it stays dismissed for that page. Workspace admins can switch checks off or change their severity for every site at once.
Yes. Add your content guide's criteria and a term list in the portal. Criteria become judged checks, terms become exact ones, and both score alongside the built-in library.
It asks for access to a site the first time you audit a page there, and only reads a page when you run an audit. It doesn't run in the background on pages you browse.
Sign in to the portal with your work account. If your team isn't set up yet, request access and Kandr will create your workspace.
