Slack

Before you start

• The Slack integration is a Pro feature, the same gate as the rest of the audit surface. Holding one qualifying website lets you connect the workspace; each website posts only if it is on Pro itself.
• You need permission to install apps in your Slack workspace. Some workspaces require an admin to approve new apps, in which case your install becomes a request.
• Alerts about regressions come from daily monitoring, so the website needs at least one monitored page for there to be anything to report.

Connecting the workspace

Public channels need nothing further. To use a private channel, invite Inclusify to it in Slack first (/invite @Inclusify) — a private channel the app is not in does not appear in the picker at all.

What gets posted

Four switches per website, set on that website’s page. Quiet by default: only the first is on when you connect.

Every message also carries a Mute for a week button, which stops that website posting without changing any of the switches.

Alerts close themselves. When every page a new-issues alert named is back to the score it held before the regression, Inclusify replies in that alert’s own thread to say so. Returning to a previous score is not the same as being accessible, and the reply says exactly that — it means the regression is undone, not that the page is fine. An alert nobody resolves within a fortnight is dropped rather than followed up on a message that has long scrolled away.

Filing a Jira ticket

Alerts carry a Create Jira ticket button. It files exactly what the panel’s own export files: the website’s open findings from the current scan, grouped one entry per issue pattern rather than one per element, on the board that website is configured for.

Jira is connected separately, in the same Integrations page, and the board is chosen per website. If either is missing, the button replies privately with what to set up rather than failing silently. See the integrations overview for the rest of what Inclusify connects to.

Commands

• /inclusify score — the accessibility score for the website this channel is bound to, with when it was measured.
• /inclusify issues — the worst failing checks on that site, worst first, one entry per rule.
• /inclusify pages — which pages are monitored and when each was last scanned.
• /inclusify sites — every website in your account with its score.
• /inclusify scan — starts a full-site scan, capped at three a day per website.
• /inclusify ticket — files a Jira ticket for that site’s open findings.
• /inclusify mute and /inclusify unmute — pause and resume that site’s alerts.
• /inclusify help — lists the commands.

Every command except sites takes an optional website, so one ops channel can ask about any site in the workspace: /inclusify issues example.com. Because they are slash commands they also work inside anything that can send one — a reminder, a scheduled post, or a workflow somebody else built.

Replies are visible only to whoever ran the command. Anyone in the connected Slack workspace can run them, for any website in the linked Inclusify workspace, so treat the install as the trust boundary it is.

Asking questions

Open Inclusify from your Slack sidebar and ask about your own sites in plain language: where a site stands, what is failing, whether the score moved, what is stopping a scan. The answer comes from your latest scans, not from a general explanation of WCAG.

It also knows its way around Inclusify, so “where do I set that?” gets the actual page rather than a shrug. Ask why something is not working and it checks that website’s setup — plan, Jira board, Slack channel, monitored pages — and tells you what is missing and where to fix it. Name a Jira board and it will set it for that site.

Ask for a ticket covering only the critical and serious issues and it will file exactly that; ask for everything and you get everything.

Ask it to file a Jira ticket and it will, on the board that website already uses — the same ticket the panel and the alert buttons create. Everything else it does is read-only by construction rather than by instruction: it reaches your data through the same tools an AI assistant uses over MCP, as a service caller, and that caller is refused every tool that writes. It cannot start a scan or change a setting however it is asked; starting a scan stays /inclusify scan, where a person typed it. It will also not tell you a site is compliant or accessible, because automated checks cannot establish that.

The Inclusify tab

Opening Inclusify from the Slack sidebar shows every website in your workspace with its score, the channel it reports to, which alerts are on, and whether it is muted. Websites that are not posting anywhere are listed last, so the tab doubles as the list of what is left to set up. It is read-only: the switches live in the Inclusify panel, and having two places to set one switch is how they start disagreeing.

Links

Pasting an Inclusify website link into a channel unfurls it into that site’s current score. Only websites in your own account unfurl; somebody else’s link produces nothing at all.

Permissions

Inclusify asks for the narrowest set that does the job. It can post messages, post to a public channel without being invited, list your channels for the picker, receive the /inclusify command, unfurl its own links, and read the questions you type to it directly — that last one is how the assistant answers, and a question it cannot read is a question it cannot answer.

It requests no history permission for channels, private channels or group messages, so it never sees what your team writes to each other. It also holds no token that acts as you: it posts as itself.

When something is wrong

• Nothing is arriving. Check the website’s Slack row: it names the channel and the events that are on, and shows the last delivery error if there was one. A muted website says so there too. Every attempt to post is recorded, successes included, so “it never tried” and “it tried and failed” are told apart rather than guessed at.
• “Inclusify is not in that channel.” The channel is private and the app has not been invited. Run /invite @Inclusify in it, then save the channel again.
• Needs reconnecting. The authorization was revoked, or the app was removed from the workspace. Reconnect from the Integrations page; channel choices survive a reconnect into the same workspace.
• Connecting to a different Slack workspace. One Inclusify workspace connects to one Slack workspace. Installing from a second one replaces the first and clears the channel choices, because those channel IDs mean nothing in the new workspace.

Removing it

Disconnect on the Integrations page removes the authorization, uninstalls Inclusify from Slack and unlinks every channel in the workspace. Removing the app from the Slack side does the same thing from the other direction: Inclusify notices, stops posting and shows the connection as needing reconnection, keeping your channel choices in case it was a reinstall.