Threads Accessibility: What Needs Improvement

Threads, Meta's microblogging platform, launched in July 2023 with glaring accessibility issues, making it difficult for disabled users to fully engage. Despite its rapid growth, the app faced criticism for failing to meet basic WCAG 2.1 Level AA standards, with a 50% failure rate in accessibility tests. Key problems include:

• Alt Text Limitations: Reliance on AI-generated image descriptions and a restrictive 500-character limit for alt text.
• Video Captioning Issues: Auto-generated captions are error-prone, with no option for custom or editable captions.
• Limited Customization: Poor contrast ratios, no text scaling, and lack of in-app display adjustments.
• Mobile-Only Design: Excludes users reliant on desktop assistive tools, with no desktop version or landscape mode support.
• Screen Reader Navigation Problems: Inconsistent navigation and unlabeled buttons disrupt usability.

These flaws create barriers for millions of disabled users, highlighting the urgent need for Meta to address these gaps. While waiting for updates, creators can use external tools for alt text and captions to make their content more accessible.

::: @figure {Threads Accessibility Issues: 5 Major Barriers Affecting Millions of Disabled Users} :::

Main Accessibility Problems on Threads

Tests have shown that Threads falls short on nearly 50% of WCAG 2.1 Level AA criteria, presenting serious barriers for millions of disabled users in the U.S. [1][3]. These issues make the platform difficult - or even impossible - to use for many. Below are the most pressing accessibility concerns impacting Threads.

Missing Alt Text Features for Images

When Threads launched, users couldn't add their own alternative text to images. Instead, the app relied entirely on AI-generated descriptions, which often failed to provide meaningful context for blind or low-vision users [1][2]. For instance, an image of a detailed certificate might be described in vague terms like "May be an image of text" [1][2].

Meta later introduced alt text functionality, but with a 500-character limit on descriptions. This restriction makes it tough to fully describe complex visuals like infographics, charts, or detailed photos [4]. As Allon Mason, CEO and Founder of UserWay, pointed out:

"Insufficient alt text can exclude users, particularly when dealing with complex images." [4]

On top of this, video content poses additional accessibility hurdles.

Poor Video Captioning Options

Threads relies on auto-generated captions for videos, but these often include errors, leading to confusion for deaf or hard-of-hearing users [1][4]. The app doesn’t allow creators to upload their own captions or edit the automated ones, leaving no way to improve accuracy or formatting. This lack of flexibility further limits accessibility.

No Customization Features

Threads also struggles with basic customization options. The app’s text and icon contrast ratios fall below WCAG standards, leaving users dependent on system-wide settings from their operating systems [1][4]. However, these settings often don’t offer the specific adjustments users might need for Threads. At launch, there were no in-app options for text scaling, color contrast tweaks, or other display preferences.

Mobile-Only Platform

From the start, Threads has been a mobile-only app, excluding users who rely on desktop accessibility tools like refreshable Braille displays, advanced screen readers, or alternative input devices [1][2][4]. Chase DiBenedetto, Social Good Reporter at Mashable, highlighted this limitation:

"Threads is currently a mobile-only app, limiting access for users who prefer or only use larger desktop screens. It also inhibits those who use desktop-specific accessibility features, plug-ins, or mobility devices." [4]

Adding to this, the app is locked in portrait mode, which violates WCAG orientation guidelines [1].

Screen Reader Navigation Issues

Navigation is another major challenge for screen reader users. Threads features inconsistent navigation, causing screen readers to skip over crucial details like "verified" badges or even jump back to earlier posts [1]. Many buttons lack proper labeling or roles, making screen readers announce them incorrectly or with significant delays [1]. Even the Threads logo is mistakenly identified as a "Progress bar, in progress" by assistive technology [1]. These flaws disrupt the user experience and prevent equal participation for disabled users.

Paul Speller summed up the gravity of these issues:

"The results are not very kind or friendly. Of around 30 relevant WCAG Success Criteria he tested, he found multiple failures on around half the criteria, creating access barriers for millions of potential Threads users." [1]

How These Problems Affect Users

Threads' technical shortcomings don't just hinder functionality - they directly impact user engagement and inclusivity. These gaps create barriers that prevent equal participation for many users.

Alt Text and Image Descriptions

For blind and low-vision users, images on Threads often lack meaningful context. AI-generated descriptions frequently fall short, missing key details or failing to convey the message the author intended. For example, screen readers may not identify blue "verified" badges, which are crucial for confirming account authenticity. This leaves visually impaired users unable to fully engage in conversations about shared images. Considering that 4.8% of the U.S. population lives with a vision disability [5], this is no small issue. The problem extends to video content as well, further hampering accessibility and engagement.

Video Accessibility and Captioning

Deaf and hard-of-hearing users face similar challenges when it comes to video content. Auto-generated captions are often riddled with errors, making it difficult to follow what’s being said. Adding to the frustration, creators currently can’t edit or replace these inaccurate captions. Allon Mason, CEO and Founder of UserWay, explained:

"This exclusion prevents individuals with hearing impairments from fully engaging with the content and enjoying the digital experience." [4]

The alternative - burning captions into videos using third-party tools - can lead to overlapping text, creating a cluttered and unreadable display. This issue doesn’t just affect the deaf community; it also impacts users who browse without sound, further limiting engagement.

Customization and Cross-Device Support

Threads' mobile-only design poses significant challenges for users who depend on desktop assistive technologies. Many individuals with disabilities rely on specialized tools like refreshable Braille displays, advanced screen readers, or alternative input devices, which are typically designed for desktop use [3]. Additionally, the platform's portrait-only orientation creates obstacles for users who need landscape-oriented touchscreen setups [1].

Desktop users also lose access to browser extensions and plug-ins that help adjust font sizes, colors, or contrast settings. For people with low vision, who benefit from the magnification capabilities of large desktop monitors, the limitations of small mobile screens can make Threads nearly impossible to use [3]. Given that one in four U.S. adults lives with a disability, these design choices exclude a large portion of potential users. Addressing these barriers is critical to making Threads a platform that everyone can use effectively.

How Threads Can Fix These Problems

Threads has the potential to address significant accessibility gaps, taking cues from its sister platforms that already implement better practices. Here’s a closer look at how Threads can tackle the key accessibility challenges identified earlier.

Add Better Alt Text Tools

The current 500-character limit for alt text descriptions on Threads falls short when it comes to describing complex images. Allon Mason points out that this constraint prevents users with visual impairments from accessing detailed image descriptions [4]. Moreover, the alt text feature is tucked away in the interface, requiring users to navigate multiple layers to find it [7].

To improve, Threads could implement pre-post prompts encouraging users to add alt text before publishing. An optional setting could even block posts from being published until all images include alt text. Allowing users to edit alt text after posting - without needing to delete and recreate the post - would also enhance usability.

Another overlooked detail is the lack of a text alternative for the blue "verified" badge. Currently, screen readers don’t announce it. Paul Speller, an Accessibility and Usability Consultant at AbilityNet, highlights the broader issue:

"It's difficult or impossible for an AI engine to understand the intention an author has when they include an image" [1]

Enable Custom Video Captions

Auto-generated captions are helpful but often miss the mark, especially with technical terms or diverse accents. Luke Trower, Design Manager at Purple Goat Agency, notes:

"Threads not letting people customise captions for their videos means that someone who wants to ensure they have accurate captions on their video must use another tool before they are able to post" [2]

To address this, Threads should allow users to upload custom caption files (like .srt files) or edit AI-generated captions directly within the app. Additionally, an option to disable auto-captions when custom captions are provided would prevent overlapping text, ensuring a cleaner and more accessible presentation.

Add More Customization Options

Customization options for text scaling, color contrast, and dark mode are essential for users with visual impairments. Currently, some text elements on Threads have contrast ratios as low as 1.85:1, far below the recommended 4.5:1 minimum [2].

Threads should also respect system-level accessibility settings, like "Reduce Motion." The animated 3D background on the home page, for example, can be disorienting for users with vestibular disorders, yet there’s no way to pause or disable these animations. Including more in-app customization options would reduce reliance on external tools and create a more user-friendly experience.

Create a Desktop Version

Threads’ mobile-only design excludes users who rely on desktop assistive technologies like JAWS, NVDA, refreshable Braille displays, or alternative input devices. The Bureau of Internet Accessibility explains:

"By limiting Threads to mobile devices, the app fails to meet [universal design] benchmarks... This is a barrier for people who use desktop-only assistive technology" [3]

A desktop version would need to incorporate features like proper keyboard navigation and semantic HTML. It should also automatically detect and adapt to OS-level settings, such as high-contrast modes and reduced motion preferences. This would make the platform more inclusive for a broader audience.

Test with Disabled Users

Accessibility improvements can only be effective if they are tested by the people who rely on them. Threads should involve disabled users during both the design and testing phases. Early audits revealed that Threads failed approximately 50% of WCAG 2.1 Level AA success criteria [1]. Including real user feedback throughout development can help identify and address issues that might otherwise go unnoticed.

As Allon Mason, CEO of UserWay, explains:

"Digital platforms have a responsibility to be inclusive, and it is essential that accessibility is at the forefront of their design considerations" [4]

These updates aren’t just about meeting standards - they’re about making Threads a platform that truly works for everyone, especially those who need accessibility the most. By addressing these gaps, Threads can create a more inclusive and user-friendly experience.

sbb-itb-a73accb

Tools and Workarounds for Users

While Threads works on improving accessibility, there are practical steps you can take to make your content more inclusive. These methods can help you connect with a broader audience, including the approximately 25% of U.S. adults with disabilities [3][5]. Until Threads introduces better accessibility features, these tools and strategies can bridge the gap.

External Accessibility Tools

One of the most pressing issues on Threads is the lack of effective alt text for images. The platform's AI-generated alt text often provides vague or unhelpful labels [1][2]. To address this, you can use external tools to create more descriptive and accurate alt text before posting. A great option is TheBlue.social's free alt text generator, which helps craft detailed descriptions for your images.

Once you've generated your alt text, you can manually add it to your Threads post. Simply upload your image, tap the three dots in the lower-left corner, and select "Add Alt Text" [7]. For mobile users, enabling the Alt Text Badge in Profile > Settings > Account > Accessibility ensures these descriptions are visible to everyone, not just screen reader users [7].

Alternative Accessibility Strategies

Since Threads doesn’t currently support uploading custom captions, creators need to rely on third-party tools like CapCut or Adobe Premiere to embed captions directly into their videos [1][4]. Luke Trower, Design Manager at Purple Goat Agency, highlights this issue:

"Threads not letting people customise captions for their videos means that someone who wants to ensure they have accurate captions on their video must use another tool before they are able to post" [2]

For text-based accessibility, consider including detailed descriptions directly in your post. This can be especially helpful when the 500-character limit for alt text isn’t enough or when you’re sharing videos that require transcripts [2][4]. Additionally, adjusting device-level settings - such as text size, contrast, or motion reduction - can help compensate for Threads’ lack of internal accessibility options [2][6]. Screen reader users may also need to tap the "Home" icon to refresh their timeline, as the Threads logo is mistakenly identified as a "progress bar" [1].

While these workarounds aren't perfect, they provide immediate solutions and empower users to create more inclusive content while waiting for Threads to enhance its accessibility features.

Conclusion

Threads launched with several accessibility hurdles that limit how users can interact with the platform. From relying on flawed AI-generated alt text to lacking custom video captioning, poor screen reader navigation, and being restricted to mobile-only access, these issues make it challenging for many individuals to fully engage. These gaps in accessibility affect a significant portion of users and call for urgent attention.

Meta needs to prioritize changes like enabling user-generated alt text, adding custom video captions, improving color contrast to align with WCAG standards, and creating a desktop version [1][4]. As Allon Mason, CEO of UserWay, aptly put it:

"Digital platforms have a responsibility to be inclusive, and it is essential that accessibility is at the forefront of their design considerations" [4].

Threads gained an impressive 100 million users in just five days [1]. Now, imagine the impact if everyone could access and enjoy the platform equally. While Meta works toward these necessary updates, creators can take immediate steps to bridge the gap.

For now, tools like TheBlue.social's free alt text generator can help produce more accurate alt text. Creators can also embed captions directly into videos and include detailed descriptions in their posts. These small but meaningful actions contribute to a more inclusive social media experience, showing that accessibility is not just essential - it’s beneficial for everyone.

FAQs

::: faq

What accessibility issues does Threads have, and how can they be improved?

Threads faces several accessibility challenges that make it difficult for users with disabilities to navigate and engage with the platform. Key problems include poor color contrast, which can strain visibility; inconsistent button labeling, making it harder for screen readers to interpret; flawed navigation structures that disrupt usability; and limited screen-orientation support, which can frustrate users who rely on specific device orientations. Another major drawback is that Threads is currently mobile-only, shutting out users who depend on desktop-based assistive technologies like screen readers or Braille displays. On top of that, the app doesn't allow user-generated alt text for images, relying instead on AI-generated descriptions. These AI descriptions often lack the detail or context needed for blind or low-vision users to fully understand the content.

To address these issues, Threads could take several steps: launching a desktop or web version, improving compatibility with screen readers, enabling user-generated alt text, and refining labeling and navigation systems to make them more intuitive. In the meantime, creators looking to make their content more accessible can turn to tools like TheBlue.social’s free alt-text generator to help bridge the gap and ensure their posts are more inclusive for everyone. :::

::: faq

How can I make Threads more accessible while waiting for updates?

Meta is working on improving accessibility, but there are steps you can take right now to make Threads more inclusive. One simple way is by adding descriptive alt text to your images. This helps screen-reader users understand the visual content. If you're using the desktop version of Threads, you can add alt text by clicking the three-dot menu on an uploaded image, selecting Add Alt Text, and typing a clear description. Keep in mind, though, that alt text can't be edited after publishing, so plan your descriptions carefully.

To improve readability, you can adjust your device’s settings. Enable high-contrast mode, dark mode, or increase text size to make content easier to read. If you rely on a screen reader, such as VoiceOver (iOS) or TalkBack (Android), test how your posts are read aloud to ensure they’re easy to navigate. For additional options, try accessing Threads through Instagram’s desktop site, which supports assistive technologies like refreshable Braille displays.

If you come across issues like low color contrast or the inability to edit alt text, report them through Meta’s accessibility feedback channels. Providing detailed feedback can help highlight areas that need attention, encouraging quicker updates and improvements. :::

::: faq

Why is having a desktop version of Threads essential for accessibility?

A desktop version plays a key role in accessibility because many assistive technologies - like desktop screen readers, refreshable Braille displays, and keyboard-only navigation tools - are specifically designed for use on computers. Without a desktop option, individuals who depend on these tools encounter major obstacles when trying to access Threads, create posts, or engage with content.

Another advantage of a desktop interface is the accessibility features it can offer. For instance, it makes it easier for users to add and review custom alt text for images. On mobile-only platforms, this process can be difficult or even unavailable. With a desktop setup, blind or low-vision users can create detailed image descriptions and ensure they are accurate.

By offering a desktop version, Threads can bridge the gap for assistive technologies, improve functionality for critical features, and make the platform more accessible to all users. :::