Ada compliance

Please consider a way to for screen readers such as NVDA, Jaws, or Vox Chrome plugin to read the content for the Instagram Feed with alt text for each image, and have the widget be better accessible with keyboard tabbing. The idea with keyboard tabbing is that it is easy to tab through all the content inside the widget with a keyboard. Currently it skips the hidden content that users with seeing abilities can click through to with the carousel arrows.

Original comment from Janice Stanford transferred from the previous Wishlist portal:

Blind users with screen readers and other keyboard users are not able to access the social share buttons. A very simple change would be required to make the buttons keyboard accessible. It is required to meet WCAG guidelines and you’re risking legal action if you don’t fix this. tags must have an href value or a tabindex=-1 to be keyboard accessible. It’s so easy.


Can you please make Form Builder (or any other widgets) compliant to the WCAG requirements? More and more countries and governments are requiring it and it is impossible for us to use Elfsight on websites under those jurisdictions.


Original comment from Matthew Gonzalez transferred from the previous Wishlist portal:

For greater accessibility please make sure all popup buttons and elements have sufficient color contrast by default, WebAIM: Contrast Checker. There’s a hidden ‘share’ button that doesn’t meet WCAG AA contrast criteria and I was getting an error in my site until I correct it via styles (see below).

.eapps-widget-toolbar-panel-share-button {background-color: #0c7bc0 !important;}

Thank you for your assistance!

Please make your widgets Ada compliant

Folks, our former Wishlist portal, where our users shared their requests and suggestions, was transferred to this forum. You’re most welcome to vote, add new ideas, and leave your comments here — we surely will consider them all! :star_struck:

Original Votes: 5

Royal National Institute of Blind People (RNIB) accessibility text to speech and size of font personalization for accessibility for people with hearing difficulties

1 Like

@Adam9 thanks a lot for your suggestion!

Yes, this is surely important to make your website accessible for any user, and we’ll try to speed up the process of making it possible.

Thank you very much for your help!

I don’t care much about the ADA compliancy as an EU citizen but I recently tried to make the Instagram widget more accessible. With a lot of !important overrides and simply hiding some elements I could improve it, but it’s still not great.

The focus outlines are hidden by overflow: hidden on .eapps-instagram-feed-posts-item. Removing this seems like an easy fix that would benefit everyone, not just blind people or users who have to navigate websites with the keyboard.

Looking at the “Load more” button: using <div> elements as fake buttons is a practice to be avoided due to various accessibility concerns.

If you want to go the extra mile, aria attributes for certain elements would be great. But getting the basics sorted out is obviously more important.


Hi there and welcome to the Community @thomasguenther :wave:

I see that my colleague Natalia has already responded to your request in a support ticket.

As she mentioned, our developers are constantly working on new feature requests. However, due to the heavy workload, this one is not the top priority at the moment. We closely monitor user votes, and the most wanted features are usually considered first.

However, we’ve forwarded your request regarding the “Load more” button syntax to our devs. Natalia will keep you updated :slightly_smiling_face:

We have to comply to WCAG 2.0 AA Standards.

Which widget is and which isn’t?

Would it be possible to have VPAT or other reports on them?


1 Like

Hi @Mario_L_Ecuyer :wave:

I have to say that our apps don’t fully meet WCAG requirements. I am really sorry!

We do realize that it’s crucial to make the widgets accessible for all users and we’ll try our best to consider this opportunity in our future updates.

As for now, would it be an option for you to contact our Support Team and specify what widgets you need to be WCAG accessible most? They’ll be happy to check things and see what can be done with the compliance situation :slightly_smiling_face:

Thanks a lot for sharing your feedback and pointing us in this direction!