twitterchat

Writing

How to make an X chat accessible to everyone

Short answer

Use a CamelCase hashtag, put every question in text (with alt text on any image), share questions in advance, leave enough minutes between questions, avoid emoji clutter, and in a Space remind listeners that live captions are available and post a written summary.

Key takeaways

  • CamelCase hashtags (#BookClubChat) let screen readers read the words; all lower case reads as one long word.
  • Every question goes in the post text, never only inside an image.
  • X allows image descriptions up to 1,000 characters, and everyone can read them.
  • Eight minutes per question gives slower typists and screen-reader users a fair chance to join in.

A live chat is fast, text-heavy and full of symbols, which makes it harder than it needs to be for many people: screen-reader users, people with dyslexia, people typing with one hand or by voice, and anyone reading in their second or third language. Small choices by the host fix most of it, and they make the chat nicer for everyone else too.

Why does accessibility matter in a live chat?

Because a chat rewards speed, and anything that slows someone down quietly removes them from the conversation.

In a normal post, someone who needs three extra minutes can still reply. In a chat, three minutes means the next question has arrived and their answer lands in the wrong place. Accessibility here is mostly about time and clarity: enough of both that people using assistive technology can keep up.

How should you write the hashtag?

Capitalize each word, so #BookClubChat instead of #bookclubchat.

Screen readers try to pronounce a tag as words. In all lower case, a long tag often becomes one garbled word. With capitals, the reader can split it. Sighted readers parse it faster too, and you avoid accidental words appearing where two words meet.

X search is not case-sensitive, so capitalizing costs nothing. Keep the tag short as well: every participant types it in every answer. The hashtag checklist flags all-lower-case tags, look-alike letters and long tags.

Can you post questions as images?

Only if the full question is also in the post text, and the image has a description.

Branded question cards look good, but text inside an image is invisible to screen readers, to people with images turned off and to search. Put the question in the post itself. Then add an image description: X allows up to 1,000 characters, and its Help Center points out that the description is the only guaranteed place to describe an image, and that everyone can read it.

For a question card, the description can simply repeat the question and name the visual: "Question card: Q3: Which character would you most like to argue with? Purple background, chat logo."

How fast should a chat move?

Leave at least seven or eight minutes per question, and say so at the start.

Five minutes per question suits fast typists with a keyboard. It does not suit someone using voice input, a switch device or a screen reader that has to read every new post aloud. Eight minutes is a fairer default. If you want more questions, run a longer chat, or drop one question.

Tell people the pace in your welcome post ("A new question every 8 minutes, answer whenever you like, late answers welcome"). It takes the pressure off. The question builder spaces questions automatically from your start time.

What about emoji, abbreviations and slang?

Use emoji sparingly at the end of a post, spell out abbreviations once, and avoid in-jokes in the questions.

Instead of Try
"🔥🔥🔥 Q3 🔥🔥🔥" "Q3: ..." with one emoji at the end, if any
"PM, ICYMI, TL;DR" "project management (PM)", spelled out once
"Q4: thoughts on the thing from last wk?" name the thing; link to it
ALL CAPS for emphasis normal case; some screen readers spell caps out

X's image-description guidance makes a similar point about acronyms: capitalize them so screen readers don't read them as words, and spell out abbreviations where you can.

How do you make a Space more accessible?

Remind people that live captions exist, introduce speakers by name each time they start, and post the key points as text.

X's Help Center says Spaces serve automated live captions that listeners can view with a few seconds of delay. Automated captions struggle with names, jargon and crosstalk, so:

  1. Ask speakers to say their name before speaking.
  2. Keep one person talking at a time.
  3. Pin a post with the topic and any links mentioned.
  4. Publish a written summary afterwards; see the recap guide.

What should go in your chat's pinned post?

The day, time with time zones, hashtag, number of questions and pace, plus a line saying questions are shared in advance on request.

A pinned post with this information lets people plan around their needs before the chat begins. It's also the place to say late answers are welcome. That one sentence tells everyone who needs more time that they still belong in the conversation.

Frequently asked questions

Does capitalization change how a hashtag works?

No. Hashtag search on X ignores case, so #BookClubChat and #bookclubchat find the same posts. Capital letters only change how people and screen readers read the tag, so there is no reason not to use them.

How should I use emoji in chat posts?

Sparingly and at the end. Screen readers announce each emoji by name, so a row of five emoji becomes a long string of words. One emoji after the text is fine; emoji used as bullet points or in place of words are not.

Are X Spaces accessible to deaf and hard-of-hearing people?

Partly. X's Help Center says Spaces serve automated live captions that listeners can turn on, with a few seconds of delay. Automated captions miss names and jargon, so post the key points and any links as text during or after the Space.

Should I share questions before the chat?

It helps a lot of people: those who type slowly, use voice input or switch access, read in a second language, or need time to think. Sharing the questions a day ahead costs you little surprise and widens who can take part.

Sources

  1. X Help Center: How to write great image descriptions
  2. X Help Center: How to host a Space (live captions)
  3. X Help Center: How to use hashtags
  4. W3C WAI: Web Content Accessibility Guidelines (WCAG) 2.2

Platform details checked as of November 2026. X changes features often; if something here no longer matches the app, tell us.