DOCUMENTATION

AccessLens for Confluence

A practical workflow for finding, prioritising and tracking accessibility issues in Confluence Cloud content.

1. Open AccessLens

After an administrator installs the app, open AccessLens from the Confluence Apps menu. The dashboard starts with no scan data until you choose the spaces to assess.

2. Choose scope

Open Spaces, enable the spaces you want to include, and save. Start with a representative space before enabling a large knowledge base.

3. Run a scan

Choose an incremental scan for routine checks or a full scan after a major content migration. AccessLens queues pages and records progress in the run history.

4. Review findings

Filter by severity, space, rule or status. Each finding includes evidence, a location and a recommended remediation so content owners can act without interpreting raw markup.

5. Govern exceptions

When a finding is accepted temporarily, add a reason and expiry. The exception is retained in the audit history and returns to the active workflow when it expires.

6. Export evidence

Use CSV or JSON export to share a time-stamped view of current findings with governance, accessibility and platform teams.

What AccessLens checks

Checks include image alternatives, heading sequence, link clarity, table headers, media context and common content-governance gaps. The app analyses selected pages read-only; it never edits pages or permissions.

Data and privacy

AccessLens processes page bodies in memory and stores the minimum operational data needed to track findings: page and space identifiers, finding fingerprints, limited evidence, timestamps and approved exceptions. See the Privacy Policy for data categories, retention and request handling.

Need help?

For installation, access or product questions, use the support page.