As I told you there is too many things to do on the widget to be accessible, I regret but it is lot’s of time for me to explain all… and I’m french so sorry for the mistakes
And in final, it will be only a version of the widget which will be accessible, depend on the options the user of the widget is going to take…, not the widget at all.
So, you have to add the option alt for images: if deco => alt =“”
About the text: linkedin provide you a text with double ( and with ugly and inaccessible links) => that’s not accessible, that the reason I didn’t wanted all the text in my widget ( and your js works visually but there is still a problem: the text is trim but only hide. I just don’t want the text). After reflexion that’s also the reason I said the widget is “not readable without css” .
Also, the text must be a text only and the “Action on Post Click” must be an “Action on the read more” instead.
And about this link ( read more ), if it opens a new tab or window : add a title with “open in new tab/window” in it, H33: Supplementing link text with the title attribute | Techniques for WCAG 2.0) , if it a fake link it must have tabindex=“0” role=“link” so it can be open with the keyboard with “Tab + enter”, (and maybe but i’m not sure on “role=link” : rel=noopener, rel=noreferrer.)
Maybe there is more, but now that’s all I have . ( And I tested the widget so often so I have nearly no views left with the free plan to continue the tests ( 185/200)…
@Ccile A huge thank you for taking time to share the details!
I’ve moved your comment to the dedicated thread in the Wishlist, where we are discussing the accessibility enhancements that should be implemented to our widgets.
We’ll try to consider your suggestions too and I’ll make sure to update you here in case of any changes
By the way, I’d like to tell you about the way to keep your own views from being counted. You just need to be logged in to your Elfsight account on the same device and browser that you use to work with your website
The key point below, states that overlay should not be used, so to the team at Elfsight, please spend that time making all your widgets compliant to WCAG 2.1 it would make more sense in the long term for your business.
Le point clé ci-dessous indique que la superposition ne doit pas être utilisée. Donc, à l’équipe d’Elfsight, veuillez-vous consacrer à rendre tous vos widgets conformes aux WCAG 2.1, cela aurait plus de sens à long terme pour votre entreprise.
4.6.3. Using Accessibility Overlay Tools
The European Disability Forum (EDF) and International Association of Accessibility Professionals (IAAP) issued a joint statement67 clarifying the limitations of a technology known as ‘accessibility overlay’. They warned that this technology does not make websites accessible or compliant with European accessibility legislation.
Absolutely. Overlays do not make sites accessible or compliant. We use them to “enrich” certain sites but accessibility must be native. We hope that Elfsight will make their widgets natively accessible.
