Guides
Written for the people who own the content: documentation leads, knowledge managers, Confluence admins, and whoever ended up answering the accessibility question in a procurement form.
Confluence and WCAG: what Atlassian covers and what is yours
Atlassian's VPAT covers the product. It says nothing about the pages your teams wrote. Where the line sits, and why it matters in an audit.
Does ADA Title II apply to your Confluence knowledge base?
The 2027 and 2028 deadlines, who is covered, and how to work out whether your spaces are in scope.
Alt text in Confluence: how to add it, and how to write it well
The mechanics in the Cloud editor, what makes a description useful, and the cases where empty alt text is the right answer.
Tables a screen reader can actually read
Header rows, merged cells, layout tables, and how to restructure the table that has been growing sideways since 2021.
The outline a screen reader hears
Skipped heading levels, bold text standing in for headings, hand-typed lists, and the H1 Confluence already gave you.
The European Accessibility Act for documentation teams
In force since June 2025. What it covers, the micro-enterprise limit, and why “disproportionate burden” is a document rather than a shrug.
A WCAG 2.2 checklist for Confluence authors
The dozen things an author actually controls, ordered by how much harm each one removes.
Section 508, VPATs and the procurement questionnaire
What a VPAT actually is, why Atlassian's own document does not answer the question about your content, and what a defensible response looks like.
The six checks behind most Confluence accessibility failures
In a study of 1,182 pages, six mechanical checks accounted for most of what failed. What each one is, and how an author closes it.
How to audit a Confluence space for accessibility
A practical order of work for thousands of pages: measure first, sort by check rather than by page, and route the fixes to whoever wrote them.
Universities and the April 2027 deadline
Why a university's population is read as its state's, which puts almost every US public university in the earlier group, and where the work actually sits.
What a screen reader actually does with your documentation
How a page written for the eye sounds to someone listening at 300 words a minute, and the five habits that decide whether it works.
Study: the accessibility of documentation published in Confluence
1,182 pages across thirteen public Confluence sites. Nearly two in three carried no level A or AA failure, no site was clean, and six checks accounted for most of what failed. Recounted 7 October.