---
name: confluence-accessibility-check
description: Check Confluence Cloud pages and spaces for accessibility problems (missing image alt text, vague link text, tables without header rows, empty or skipped headings, untitled embeds, unnamed buttons) with the Accessible Pages MCP tools, and explain each fix in plain words. Use when someone asks whether a Confluence page or space is accessible, screen-reader friendly, WCAG compliant, or what to fix.
---

# Confluence accessibility check (Accessible Pages)

Accessible Pages is a Forge app for Confluence Cloud. Its two tools are served by the Atlassian MCP server.

## Setup (once)
1. A Confluence site admin installs Accessible Pages and turns its tools on: Atlassian Administration > Apps > Sites >
   your site > Connected apps > Accessible Pages > View app details > Tools > Enable tools.
2. Add the MCP server to your assistant: `https://mcp.atlassian.com/forge/6c6aae79-7b8d-4c4c-a544-1caa07f83528`
   (HTTP transport), for example `claude mcp add --transport http accessible-pages <that URL>`. The first connection
   opens Atlassian's sign-in and consent screen: choose the site and accept. The server lists exactly two tools.
3. The tools act as the signed-in person. They can only read pages that person can already see.

## The tools
- **check-page-accessibility** (input `pageId`, the numeric page ID). Returns the page title, `totalProblems`, and
  `findings`: for each kind of problem, the plain description, how many times it happens, the WCAG criterion, `howToFix`,
  and `example`, the first matching piece of HTML.
- **scan-space-accessibility** (input `spaceKey`, for example `HANDBOOK`). Checks up to 60 current pages and returns
  `pagesChecked`, `pagesNeedingWork`, `truncated`, and `worstFirst`: each page's ID, title, problem count, number of kinds,
  top issue and link.

## Finding the inputs
- Page ID: the number after `/pages/` in a page URL, for example `.../wiki/spaces/HANDBOOK/pages/655384/New+starter+guide`
  has page ID `655384`.
- Space key: the part after `/spaces/` in the URL, for example `HANDBOOK`.
- If the person gives only a page title, ask for the link. Do not guess IDs.

## How to answer
1. Call the tool. Never describe a page's accessibility without running it.
2. Lead with the count ("5 problems of 4 kinds"), then go through the findings most frequent first.
3. Make every fix concrete. Use `example` to point at the exact item:
   - image with no alt text: propose alt text based on what the surrounding page says the image shows, or say it can be
     marked decorative if it adds nothing;
   - vague link ("click here", "read more"): propose link text that names the destination, using the link's URL and the
     sentence around it;
   - table with no header row: say which row to make the header (usually the first) and how: select it and turn on
     "Header row" in the table toolbar;
   - skipped heading level: say which heading to change and to what level.
4. For a space, name the worst pages first and suggest the order to fix them. If `truncated` is true, say only the first
   60 pages were checked.
5. End with what automation cannot check: colour contrast, keyboard use and reading order.

## Rules
- Never say a page is "fully accessible" or "compliant". If there are no findings, say the automated checks passed and
  that a person still needs to check contrast, keyboard use and reading order.
- Never edit the page. Propose changes for the person to make.
- Results are guidance, not legal advice.