Clarable · accessibility checks for Confluence Cloud
Every page your team writes, checked against WCAG 2.2 as you write.
32 checks across 14 WCAG success criteria, inside Confluence Cloud. Write a page below and get a score in seconds.
In plain words
Who we are
Clearwren is a small, independent software company. We make one thing: Clarable, an accessibility checker for Atlassian Confluence.
What it does
It reads your Confluence pages, finds what makes them hard to use for people with disabilities, such as pictures with no description or headings out of order, and shows how to fix each one.
Who it is for
Teams that publish in Confluence Cloud and need to meet accessibility rules: universities, public bodies and the companies that work with them.
What it costs
You install it from the Atlassian Marketplace. It is free for sites of 10 users or fewer, with a 30-day free trial for everyone else. Your pages never leave Atlassian.
Write a page, get a score.
This runs the same checks as the app, in your browser. Write your own page, or step through ten examples. Nothing you type is sent anywhere.
## for headings, **bold**, - for lists,  for pictures and [text](link) for links.Would your colours pass?
Pick any two colours. The ratio is calculated the way WCAG defines it, and the lab can find the nearest text colour that passes.
See the same page the way your readers do.
One Confluence page, five ways of reading it. Then switch on the fixes and see what changes.
Exactly what gets checked.
Every success criterion in a scan, grouped by WCAG principle. Select one to see its checks, or see the full list of checks.
What would a scan of your space find?
An estimate from our study of 1,182 pages across 13 public Confluence sites. Your space will differ; a scan tells you exactly.
pages likely to have at least one level A or AA failure (about 36% in our study, give or take 8 points).
From the first page to the audit, in four steps.
Check a page as you write it
An accessibility score sits in the page byline. Open it to see every issue, why it matters to a real reader, and how to fix it. Missing alt text can be written straight into the page from the panel.
Scan a whole space
One click walks every current page in the space and ranks the worst offenders.
Fix the pattern, not the page
The scan shows which problems are the most common, so hundreds of missing descriptions become one job.
Publish the evidence
Generate a conformance report as a Confluence page, dated and mapped to WCAG success criteria: evidence you can hand to an auditor or add to a procurement file. See a sample report.
Also included
Report across the site
Roll every scanned space into one view: pages checked, pages with no A or AA failure, and where the remaining risk sits.
Keep it from drifting back
Scanned spaces are re-checked automatically every week, so a clean space stays clean and regressions surface on their own.
Tune it to your policy
Target level A, AA or AAA. Switch off checks that do not fit your house style. Mark genuinely decorative images so they stop being reported.
The deadline is real, and it applies to your documentation
Accessibility law has stopped being about public websites only. Under ADA Title II, US state and local government content must meet WCAG 2.1 level AA by 26 April 2027 for populations of 50,000 or more, and by 26 April 2028 below that. The European Accessibility Act has applied since 28 June 2025. Section 508 binds US federal agencies and the contractors who supply them.
Public Confluence spaces, Jira Service Management help centres and Confluence-published documentation can all fall inside that scope. And the content that fails is rarely the template — it is the thousands of pages your teams wrote by hand.
Nothing leaves your Atlassian site
Every check runs inside Atlassian's own Forge platform. Page content is read, evaluated in memory and discarded; only scores, issue locations and a short quoted fragment of each finding are stored, and they are stored in Forge storage inside your tenant. Clearwren operates no servers, and page content is never sent anywhere — including to us.
What it does not claim
No automated tool can certify accessibility. Clarable tests 11 of the 55 level A and AA success criteria in WCAG 2.2: the ones written page content can break and a rule can check. Most of the rest concern the Confluence interface itself, which is Atlassian's to meet; others need a person to judge meaning, reading order or whether a media alternative is adequate. Clarable decides what can be decided from the content, marks the rest for review, and says plainly which is which — in the app and in the report.