Does #CapitalisingHashtags Help Screen Readers? The Sources

You are writing the hashtag and emoji lines of a social style guide, and the line you want is “capitalise each word in a hashtag, so #LikeThis rather than #likethis.” Someone will ask where that comes from, and “everyone says so” is not a citation. This post goes looking for the citation.

The method is a reading of published documents, each fetched and dated on 10 October 2026. No screen reader was run for this post and nobody was interviewed. Everything below is what the pages say, what they leave out, and where the gap is filled by the reader’s own inference. Sources fall into three kinds: those that say it explicitly, those that imply it, and those that say nothing. The third group matters as much as the first, because a style guide that cites a silent document is citing nothing.

The one source that says it outright

The clearest explicit statement found is on the social media page of Section508.gov, which shows “Reviewed/Updated: July 2026”. The hashtag passage reads:

Hashtags are useful in directing users to your posts. However, hashtags containing multiple words can present accessibility issues for users of screen readers. These programs may see a multiword hashtag as being one word and they will read it as such, which can result in a confusing or unintelligible pronunciation. Therefore, always capitalize each word in a multiword hashtag. For example: #FourthOfJuly.

Read the hedges. Screen readers “may see” a multiword hashtag as one word, and that “can result in” a confusing pronunciation. The page describes a risk. It does not report a test, name a screen reader, or say which products behave this way. The instruction itself is firm (“always capitalize”), but the reason given for it is a possibility.

The page’s own text says it is aimed at federal communicators: the section 508 requirement it cites applies to information and communication technology created by the federal government, including what agencies and departments post to social media. The site carries General Services Administration (GSA) branding, and the U.S. Access Board is listed as a contributing organisation. So this is guidance for that audience. It is not a law, and it is not a platform rule.

The same instruction is repeated in the page’s per-platform notes. The X, LinkedIn and Facebook sections each end their emoji and hashtag checklist with the line to “ensure each word in a multiword hashtag has been capitalized”. The page also lists Instagram, Snapchat, Tumblr and Flickr under other platforms, and this reading did not take any hashtag instruction from those entries.

What the standard itself says: nothing about hashtags

Many people reach for WCAG at this point, so the full text of WCAG 2.2 (W3C Recommendation, 12 December 2024) was fetched and searched for “hashtag” and “emoji”. Neither word appears.

The distinction that matters here is normative versus informative. The success criteria in the Recommendation are normative: they are the requirements. The Understanding documents and the WAI tips are informative: they explain and advise, but they do not add requirements. No normative text found requires hashtag capitalisation.

A reader might reach for two nearby criteria, both Level AAA: 3.1.6 Pronunciation (Understanding page updated 17 November 2025) and 3.1.3 Unusual Words (updated 5 April 2026). Neither Understanding page contains the word hashtag, emoji or CamelCase. Applying them to hashtags is an inference you would be making. It is not something the W3C text states.

The WAI writing tips page (dated “Minor update 16 July 2024”) was fetched as well. It has no hashtag or emoji statement.

The vendor documents: Apple, Google, Microsoft

The next place to look is the people who build the screen readers and operating systems. Each page below was fetched and its text searched for hashtag, camel, emoji and capitalis(z)ation.

“No mention on this page” is a finding about that page only. It is not evidence that the behaviour does not occur, and it is not evidence that it does. The Apple VoiceOver page is a welcome and contents page, so it is a thin test in any case.

The practical conclusion is narrow. The pages checked do not document how any screen reader pronounces a multiword hashtag. This post therefore cannot say how VoiceOver, TalkBack or any other reader behaves, and it will not.

What the platforms’ own help pages say about hashtags

Two platform help pages about hashtags were checked for any link to accessibility. The YouTube Help page Find playlists & videos using hashtags returned readable text. It does not mention capitalisation, CamelCase or screen readers.

The Instagram help page numbered 351460621611097 returned HTTP 200, but the response was a client-rendered shell with no article text I could read. It is listed as could not be checked, and nothing is claimed about its contents. The X help pages could not be fetched (HTTP 403) and are likewise unchecked.

Emoji strings are a different question

Capitalising hashtags and limiting emoji are unrelated questions with unrelated mechanisms, and they should get separate lines in a style guide.

On emoji, Section508.gov says that too many in one post can be confusing or annoying for screen reader users, “as these programs will individually describe each emoji, which can take a lot of time.” Several in a row cause the same problem. It adds that emoji “in between sentences in the text of a post can be disorienting and distracting,” and advises placing them “at natural stopping points in the text of a post, such as at the end of a paragraph or prior to a link that concludes a post.”

The same page also tells writers to avoid special characters, defined as letters or symbols not on a QWERTY keyboard, with the section symbol as its example. Its per-platform checklists repeat that advice alongside the hashtag line. It does not tie the point to hashtags specifically.

What a style guide can honestly say

Each line below is paired with the source it rests on and how strong that source is.

• “Capitalise each word in multiword hashtags.” Source: Section508.gov, reviewed July 2026. Strength: explicit guidance, hedged on the reason, aimed at U.S. federal communicators.
• “Keep emoji to a few, not in a row, and put them at the end of a paragraph or before a closing link.” Source: the same page, emoji passage. Strength: explicit guidance, with the stated reason that screen readers describe each emoji.
• “Hashtag capitalisation also serves WCAG pronunciation criteria.” Source: none. Strength: an inference from AAA criteria that do not mention hashtags. Leave it out.

It would be false to write that WCAG requires capitalised hashtags, that every screen reader reads lowercase hashtags as one word, or that any test cited here shows capitalisation fixing the problem. None of those is in a fetched source.

There is a fair reason to follow the guidance anyway. Capitalising costs nothing in the text of a post, and the one source that speaks to it speaks consistently across platforms. That is a reason to adopt the habit. It is not proof of how any given reader behaves.

Where the sources run out

The fetched sources do not establish how any screen reader, in any product or version, pronounces a multiword hashtag in lowercase or in capitals. They do not establish any measured effect on users either. Section508.gov states a possibility and a rule, and nothing else found adds evidence to it.

Anyone who needs that answer should test with real assistive technology and with the people who use it. This post did not do that. Related reading on the same documentary method: what YouTube and W3C say about auto-captions, alt text on image posts, and WCAG contrast for text on a graphic.

FAQ

Does WCAG require capitalised hashtags?

No normative text in WCAG 2.2 (W3C Recommendation, 12 December 2024) mentions hashtags or emoji. The AAA pronunciation and unusual words criteria are only a possible inference by the reader.

Can I say screen readers mispronounce lowercase hashtags?

Only as the cited source words it, as a possibility. This post has no test evidence, and you should not add any.

Sources

• Section508.gov, Social Media, fetched 2026-10-10 (HTTP 200)
• W3C, Web Content Accessibility Guidelines (WCAG) 2.2, fetched 2026-10-10 (HTTP 200)
• W3C WAI, Understanding SC 3.1.6 Pronunciation, fetched 2026-10-10 (HTTP 200)
• W3C WAI, Understanding SC 3.1.3 Unusual Words, fetched 2026-10-10 (HTTP 200)
• W3C WAI, Writing for Web Accessibility tips, fetched 2026-10-10 (HTTP 200)
• Apple, VoiceOver User Guide for Mac, fetched 2026-10-10 (HTTP 200)
• Google, Get started on Android with TalkBack, fetched 2026-10-10 (HTTP 200)
• Android Developers, Build accessible apps, fetched 2026-10-10 (HTTP 200)
• Microsoft, Make your Word documents accessible to people with disabilities, fetched 2026-10-10 (HTTP 200)
• YouTube Help, Find playlists & videos using hashtags, fetched 2026-10-10 (HTTP 200)