Skip to content

Social Media Accessibility Checklist

General Guidelines

Links

  • Any self-descriptive or short links are published without the use of a link-shortener. If you do use a link shortener, you need to describe what the link does in the post e.g. "RegSign up here: 0ny.cc/XYZ"

Hashtags

  • Hashtags are written in PascalCase (a.k.a StudyCase), #LikeThis, not #likethis. You can also use camelCase hashtags #likeThis, not #likethis.
  • Hashtags are ideally placed at the end of the post, not in the middle as that interrupts the flow of screen readers.
  • There are no large blocks of hashtags. If "hashtag cloud' must be used, place them in the first comment instead of in the primary content area.

Tags

  • Tags are relevant and contextual. Don't tag accounts solely based on special requests or to reach a larger audience.
  • If the tag doesn't clearly indicate the account it links to, it is ideal to name the person or organization directly and then place the tag in parentheses after that, or simply place the tags at the end of the post.

Emojis

  • Limited and relevant emojis are used — no more than 3 in the entire post.
  • No color or symbol is solely relied upon to convey meaning — don't use emojis in place of text.
  • Emojis are placed at the beginning or the end of posts. Emojis in the middle of posts disrupt the flow of screen readers and confuse the meaning of sentences.
  • Emojis are not used as bullet points.
  • Emojis do not repeat multiple times.
  • All emoji descriptions are checked on emojipedia.org before use.

Additional Actionable Guidance for Social Media Accessibility

1. Images and Visuals (Alternative Text)

The most important action for image accessibility on social media is providing a text description for every image, chart, or graphic.

Action Requirement Why It Matters
Always Use Alt Text Use the platform's built-in feature (e.g., Twitter/X, Facebook, Instagram) to add descriptive alt text to every image. Screen readers cannot interpret visual content without a text alternative.
Describe Purpose, Not Just Content Alt text should describe what the image is and, if it's informative, what its purpose is. (e.g., "Infographic showing 75% of users prefer mobile access.") Users understand the context and value of the image, not just the literal objects in it.
Keep it Concise Limit alt text to approximately 125 characters. If the image is complex (like a chart), provide a summary in the alt text and the full data/explanation in the post body. Screen readers may cut off long alt text, and concise descriptions improve user experience.
Avoid Text in Images Do not use images to display critical text. If you must, ensure the verbatim text is included in the alt text or the main post body. Text in images is inaccessible to screen readers and cannot be translated or resized by the user.

2. Video and Audio Content

All multimedia content must be accessible to users who are deaf, hard of hearing, or have cognitive disabilities.

Action Requirement Why It Matters
Provide Accurate Captions All videos must include accurate, synchronized captions. Do not rely solely on auto-generated captions, as they are often inaccurate. Essential for users who are deaf or hard of hearing, and for the 85% of users who watch video with the sound off.
Include Audio Descriptions (If Needed) If the video contains visual information essential to understanding the content (e.g., a silent demonstration, text on screen), provide an audio description track or describe the visuals in the post text. Users who are blind or have low vision can understand the visual context.
Provide Transcripts For longer videos (over 60 seconds) or audio-only content (e.g., a podcast clip), provide a link to a full text transcript. Offers an alternative way to access the content and is searchable.
Avoid Flashing Content Do not use video or GIFs that flash or blink more than three times per second. Flashing content can trigger seizures in users with photosensitive epilepsy.

3. Post Structure and Language

How you write the post itself impacts readability and screen reader flow.

Action Requirement Why It Matters
Use Plain Language Write clearly and concisely. Avoid unnecessary jargon, complex sentence structures, and obscure acronyms. Supports users with cognitive disabilities, reading disabilities, and non-native speakers.
Use Line Breaks for Readability Break up large blocks of text into short paragraphs (2-3 sentences max). Use two line breaks to create visual separation. Improves readability for all users, especially those using screen magnification or with cognitive disabilities.
Avoid ASCII Art and Special Characters Do not use complex character arrangements or non-standard symbols for decoration (e.g., fancy fonts, borders). Screen readers often read these characters literally, resulting in confusing and disruptive noise.