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)…
Have a good day,
Cécile
