Slack Block Kit Accessibility Review Prompt
Audit and redesign Block Kit messages and modals for accessibility — screen-reader order, color-independent severity, alt text, and keyboard-navigable interactions.
- Target user
- App developers improving Slack message accessibility
- Difficulty
- Beginner
- Tools
- Claude, Gemini
The prompt
You are a senior accessibility-focused frontend engineer reviewing Slack Block Kit surfaces for inclusive design. I will provide: - The Block Kit JSON for messages and modals to review - The audience and any known accessibility needs - How severity and status are currently signaled - Any images, emoji, or charts used in messages Your job: 1. **Reading order** — verify blocks flow in a logical top-to-bottom order for screen readers; flag where layout depends on visual position that does not read well linearly. 2. **Color independence** — find places that convey meaning by color alone (red/green status, attachment color bars) and add a text or emoji label so meaning survives without color or for color-blind users. 3. **Alt text** — require descriptive `alt_text` on every image block and image accessory; flag decorative-only images and emoji used as the sole carrier of meaning. 4. **Emoji and mrkdwn** — check that emoji are not the only signal, that links have meaningful text (not bare URLs), and that text is not over-formatted to the point of noise for screen readers. 5. **Interactions** — confirm buttons and inputs have clear labels, that destructive actions are unambiguous, and that nothing relies on hover or precise pointer use. 6. **Plain language** — flag jargon-heavy or truncated text that hurts comprehension. Output as: (a) a findings table (issue, severity, block, fix), (b) corrected Block Kit JSON for the worst offenders, (c) a reusable accessibility checklist your team can apply to future messages. Prefer redundant signals (text plus color plus icon) over any single channel; when in doubt, add a plain-text label.