PROBIE
Fix these issues
Report readyDispatch 18

We found 4 issueson slack.comworth fixing.

Probie inspected slack.com the way a new customer would. 5 pages, desktop and phone, 19 minutes. Sep 15, 2026.

5 pages visited480 controls found57 clicked
slack.com's report cardSep 15, 2026

The accessibility page shifts content during load.

0 serious4 minor
See the breakdown
Probie doesn't stop at the report.Sign up and turn these findings into tested pull requests.
Fix these issues →
Probie on site

Watch the inspection.

We navigate your site the way customers would. Idle time is skipped.

Inspect your own site
the grades
B-VisualThe accessibility page shifts content during load
AAccessibilityNo contrast or readability problems turned up.
AButtons and linksEverything we clicked did something.
BUnder the hoodThree security response headers are missing on the homepage
AMobileEvery page fit the phone screen.
the issues
Minor/accessibility

The accessibility page shifts content during load

On /accessibility at desktop width, content moves under the reader while the page finishes loading. Cumulative layout shift measures 0.305, above the 0.25 boundary Google classes as poor, and the largest shift is attributed to the hero content container div.o-content-container.o-hero__content. The measurement was taken before any scrolling or clicking, and the same value came back on a fresh load.

slack.com/accessibility
Captured during the scan: The accessibility page shifts content during load
from the scan · /accessibility · desktopopen full capture ↗

Try it: Open /accessibility on desktop with a cold cache and DevTools Performance or the web-vitals CLS overlay recording, then reload and watch the hero block jump as late assets land.

Minorhome page

Three security response headers are missing on the homepage

The response from https://slack.com/ is missing Content-Security-Policy, X-Content-Type-Options: nosniff, and Cross-Origin-Resource-Policy.

slack.com
Captured during the scan: Three security response headers are missing on the homepage
from the scan · / · desktopopen full capture ↗

Try it: Run curl -sI https://slack.com/ and check the response for Content-Security-Policy, X-Content-Type-Options, and Cross-Origin-Resource-Policy.

Minor/acceptable-use-policy · phone

The chat launcher covers policy body text on mobile

On /acceptable-use-policy at a 390px wide viewport, the circular purple chat launcher is painted over the paragraph that begins "The AUP may change as Slack grow". The button covers the end of that line and the middle of the following line, so "check back regul... or" is unreadable. The launcher sits inline with the text column rather than clear of it, and the occlusion is present on a fresh load of the page at the initial scroll position.

slack.com/acceptable-use-policy
Captured during the scan: The chat launcher covers policy body text on mobile
from the scan · /acceptable-use-policy · mobileopen full capture ↗

Try it: Open /acceptable-use-policy on a phone or a 390px wide window and read the paragraph just below the "Acceptable Use Policy" link; the chat launcher covers two lines of it.

Minor/about · phone

The chat launcher covers text on the About page

On /about at a 390px wide viewport, the circular chat launcher sits on top of the body copy and covers part of the line "Slack was acquired by Salesforce in ...", so the digits of the year are hidden behind the purple button. The launcher is anchored over the text column rather than clear of it, and the same overlap appears at the same spot on repeat loads. The rest of the paragraph renders normally, so only the characters under the button are lost.

slack.com/about
Captured during the scan: The chat launcher covers text on the About page
from the scan · /about · mobileopen full capture ↗

Try it: Open /about on a phone or a 390px wide window and look at the line "Slack was acquired by Salesforce in ..." near the chat launcher button.

from report to pull request

Probie fixes this for you.

This report came from one visit. When installed on your project, Probie watches real sessions, reproduces failures, and opens tested fixes as pull requests.

Sign up and get this fixed
PRFix: The accessibility page shifts content during load
probie/fix-1+12−4checks passing

Free inspection

What should Probie inspect next?

Enter a project URL. There is nothing to install.

Probie checks every issue twice, respects robots.txt, and backs off at bot challenges.