Accessibility statement
Accessibility
Last updated
Our goal
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We treat accessibility as part of every change, not as a final check.
What we do
- Every page works with a keyboard. A "Skip to content" link comes first and focus is always visible.
- Text and links use colors that meet the WCAG contrast ratios for their size.
- Pages reflow at 200% text size and on narrow screens without sideways scrolling.
- Animations switch off when your device asks for reduced motion.
- Forms and tools have visible labels. Tool results are announced to screen readers as they change.
- Content pages work without JavaScript. The writing tools need it and say so when it is off.
- Images that carry meaning have text alternatives. Decorative ones are hidden from screen readers.
How we test
Before bigger releases we check pages with keyboard only, at phone, tablet and desktop widths, at 200% text size and with reduced motion turned on. We also run automated accessibility audits, which currently score 100 out of 100 on our main pages.
Known limits
- The Discord widget is made by Discord, so we cannot control its accessibility. Everything it shows is also reachable through the "Join" button.
- Our publications and guides live on Medium, which has its own accessibility work and limits.
- The writing tools read words, not grammar, so some explanations are best guesses. The result is always plain text you can check.
Feedback
Found something hard to use? Please tell us at mj@sweet.pub. Describe the page and what got in the way. We will reply and fix what we can.
Community
Join 2,000+ Writers on our Discord
Ask questions, share your latest story and cheer each other on. Our editors hang out there too. It is free and open to everyone.
Short link to share: sweet.pub/discord
Sweet Publications on Discord
2,000+
Writers and editors in the chat