Accessibility of social media overview: LinkedIn – automatic image alternative text problem

Note: This post is older than two years. It may still be totally valid, but things change and technology moves fast. Code based posts may be especially prone to changes...

(Loaded 818 times)

Social media is one of the most used internet services. And people with difficulties are users too. And as they should have the right to work as well – they do use LinkedIn. So it must really be accessible. But, is it?

I have seen that LinkedIn has done quite a lot on improving accessibility and it looks like they have a dedicated team of accessibility experts that is working continuously on this important matter.

Social media must me accessible too. If you only think abundance of users that are using social media channels on a daily basis – then it is maybe one of the most important services, next to government services and banking.

just in my opinion.

LinkedIn, known for it’s professional mission is maybe even more important than other social media – people with disabilities must have a right to work too. And everybody should be able to use social media today.

I found a small bug that is actually very annoying for a screen-reader user:
when a user makes a new post and writes a valid URL LinkedIn page tries to automatically extract the image that is coded into Open Graph meta data of the page (opens in new window).

This is a superb functionality – user does not need to do anything, LinkedIn is – by default – showing the picture that website creators defined as main social media picture.

But – here comes the problem – the image needs alternative text and LinkedIn is currently just using “No alt text provided for this image” instead of showing a description or maybe allowing the author to add alternative text manually.

This would not be a problem if LinkedIn would maybe marked the image as decorative (as they are also showing the Title and URL in text form), but problem is that image is wrapped in a link and missing any other text which means that assistive technology user gets “No alt text provided for this image, Link” every time (s)he focuses on every image that was parsed automatically.

I’ve really verified this, at first I thought I have to define the text via their user interface (UI), but I was unable to find such option. Then I tried to find the documentation for the Open Graph meta tags and made a test case just to test what happens when using exactly the same data that they define in the documentation – still the same problem.

I tried to describe the problem on their Twitter account but was a bit misunderstood (opens in new window), but then I was asked to open a case on their help site (opens in new window) which was closed almost immediately – their Product Team will look into it, they said.

Decent suggestion from them but as I tested with copy-pasting the code to a test page I was able to verify that they are not actually parsing alternative text from open graph data.

So – I will now wait a bit and hope that they fix this annoyance. Otherwise I will try again, maybe even escalating this into a public debate on twitter. If I can make a web just a bit more accessible it is worth it.

Author: Bogdan Cerovac

I am IAAP certified Web Accessibility Specialist (from 2020) and was Google certified Mobile Web Specialist.

Work as digital agency co-owner web developer and accessibility lead.

Sole entrepreneur behind IDEA-lab Cerovac (Inclusion, Diversity, Equity and Accessibility lab) after work. Check out my Accessibility Services if you want me to help your with digital accessibility.

Also head of the expert council at Institute for Digital Accessibility A11Y.si (in Slovenian).

Living and working in Norway (🇳🇴), originally from Slovenia (🇸🇮), loves exploring the globe (🌐).

Nurturing the web from 1999, this blog from 2019.

More about me and how to contact me: