When you type a hashtag on Mastodon, the platform automatically preserves the capital letters you use. A hashtag like #AccessibleTech displays with the same capitalization in the post text but remains case-insensitive for search and filtering. This feature is called CamelCase or PascalCase hashtag formatting. It directly improves accessibility for screen reader users because the software can pronounce each word boundary correctly. This article explains why CamelCase hashtags matter for inclusive communication and how to apply the practice consistently.
Key Takeaways: Writing Accessible Hashtags on Mastodon
- Capitalize the first letter of each word: Screen readers announce #SocialMedia as “Social Media” instead of a run-together string.
- Check hashtag readability before posting: Use the compose box preview to verify that each word boundary is visually clear.
- Do not rely on underscores or dots: Mastodon treats underscores and dots as part of the word, which can break screen reader interpretation.
Why CamelCase Hashtags Improve Accessibility
Screen readers such as JAWS, NVDA, and VoiceOver parse hashtags as single tokens. If a hashtag is written in all lowercase, the screen reader attempts to pronounce the entire string as one word. For example, #accessibilitytips becomes “accessibilitytips” — a long, unrecognizable sound. Capitalizing each word, as in #AccessibilityTips, lets the screen reader detect word boundaries and announce “Accessibility Tips” clearly.
The Web Content Accessibility Guidelines WCAG 2.1 Success Criterion 1.1.1 Non-text Content and Success Criterion 3.1.4 Abbreviations both encourage text that can be programmatically interpreted. CamelCase hashtags meet this intent by providing visual and auditory cues for word separation. Mastodon does not enforce any capitalization rule, so the responsibility falls on the author.
Mastodon’s search and discovery features treat all hashtags as case-insensitive. A search for #accessibilitytips returns the same results as #AccessibilityTips. This means you can use CamelCase without losing discoverability. The only change is improved readability for people using assistive technology.
How Screen Readers Interpret Hashtags
Screen readers rely on capital letters as word boundary markers. When they encounter #SocialMedia, they pause at each capital letter and speak the word separately. Without capitals, the reader attempts to blend all characters together. For compound hashtags longer than three words, the result is often unintelligible. Using CamelCase eliminates this problem entirely.
How to Write CamelCase Hashtags on Mastodon
Writing CamelCase hashtags requires no special tools or settings. You simply type the hashtag with the first letter of each word capitalized. The Mastodon compose box preserves the capitalization exactly as you type it. Follow these steps to create accessible hashtags every time.
- Type the hash symbol and the first word
Start with the hash symbol # followed by the first word of your hashtag. Capitalize the first letter of that word. Example: #Mastodon. - Capitalize the first letter of each subsequent word
Continue typing the next word without a space. Press the Shift key to capitalize the first letter of each new word. Example: #MastodonTips becomes #MastodonTips. - Check the preview in the compose box
Before posting, look at the hashtag in the compose box. Each capital letter should mark the start of a new word. If the hashtag looks like a single block of text, delete and retype with correct capitalization. - Post and verify the appearance
After posting, view your toot in the timeline. The hashtag should display with the capital letters you used. Tap or click the hashtag to confirm it links to the correct search results.
You can apply CamelCase to any hashtag, including those with numbers. For example, #Web3Guide is acceptable because the number acts as a natural separator. Avoid using underscores or periods inside hashtags, as Mastodon treats those characters as part of the word and screen readers may not interpret them correctly.
Common Mistakes to Avoid with Hashtag Capitalization
Even experienced Mastodon users sometimes make errors that reduce accessibility. The following issues are the most frequent and can be fixed easily.
Using All Lowercase for Multi-Word Hashtags
Writing #socialmediaaccessibilitytips instead of #SocialMediaAccessibilityTips forces screen readers to attempt pronunciation of a 30-character run-together string. The result is garbled speech that provides no useful information. Always capitalize the first letter of each word.
Inserting Underscores or Periods Between Words
Some users add underscores or periods to separate words, such as #social_media_tips. Mastodon treats the underscore as part of the word, so the hashtag becomes #social_media_tips. Screen readers read the underscore as “underscore” or pause awkwardly. Periods cause similar issues. CamelCase is the only reliable method for word separation in hashtags.
Capitalizing Only the First Word
Writing #Socialmediatips capitalizes the first word but leaves the rest lowercase. Screen readers treat the string after the first capital as a single block, producing “Socialmediatips.” Capitalize every word boundary, not just the first one.
Assuming the Platform Will Auto-Format
Mastodon does not automatically capitalize hashtags. If you type #socialmediatips, it stays that way. The platform provides no autocorrect or suggestion feature for hashtag formatting. You must manually type the capital letters.
| Item | All Lowercase | CamelCase |
|---|---|---|
| Screen reader output | Garbled single word | Clear separated words |
| Visual readability | Difficult to parse | Easy to read |
| Search functionality | Works but less usable | Works identically |
| User effort to type | Low | Minimal extra effort |
| Compliance with WCAG intent | No | Yes |
Writing CamelCase hashtags is a small change that makes a large difference for people who rely on screen readers. The practice requires no additional software, settings, or plugins. It costs nothing and takes only a second longer to type.
Start using CamelCase in your next toot. Review your recent posts and edit any hashtags that are entirely lowercase. Encourage others in your community to adopt the same standard. The more Mastodon users apply CamelCase, the more accessible the platform becomes for everyone.
For advanced accessibility, combine CamelCase hashtags with alt text on images and descriptive link text. Mastodon’s preference for plain text and open federation makes it an ideal platform for inclusive communication, but only when users actively choose accessible formatting.