Channels
Writing for accessibility
Accessible writing helps everyone — and pairs with WCAG AA visual rules in the design system accessibility page.
Plain language
- Short sentences for instructions and errors
- Define verification terms on first use in long-form content
- Reading level: aim for general audience on marketing; product UI may use domain terms from the glossary
Link text
| Don't | Do |
|---|---|
| Click here | View pricing |
| Read more | Read how verification works |
| Link | Download dispute policy (PDF) |
Alt text
- Describe what matters for the message — not "image of runners"
- Decorative images: empty alt or
aria-hidden - Charts: summarize the data point, not only "chart"
Never colour-only meaning in words
When describing ratings or status in prose, include the number and tier word — not only "the green bar". UI must pair icon + text; writing should too.
Questions in forms
Rating and survey questions must be visible legends — not placeholder-only. Matches design system Rating component requirement.
Structure
- Logical heading hierarchy (one h1 per page — the site layout supplies it)
- Lists for sequences; tables for comparable data with headers
Sporting Scouter Content Style Guide
Component-enforceable rules: design-system.sportingscouter.com/voice. Tokens from
packages/config/tailwind/theme.css.