shivaji

Thanks for your detail reply.

Yes, I noticed that this WAVE tool doesn’t have the capacity like manual testing and include a few hidden elements and shows negative results.

This include for few other plugins also.

Thanks again for the analysis.

Thanks for your reply.

Yes, I saw your website example and tried my best to make it just like your example slider and converted all % to Pixel font size. It didn’t work either.

I sent one support request with ss3 file attached. Please check.

Thanks for your reply. This plugin will jump to a new height if this essential WCAG feature is enabled in the next version release. Any timeframe when this will be added?

Yes, it removed all <script> type attributes but <style> type attributes remains. Please remove this too in next release.

Thanks.

Any timeframe for this implementation? When the next realease will come?

any update on this, please?

I have reported a few issues before in other support tickets which were minor and can be ignored?for the time being but this issue which I reported here is a? Big Violation of Accessibility Issues.

At least Error messages should have focus provided to it. It is necessary Better to provide focus now only in future if error messages changes focus will be still there. It’s a big violation of accessibility.

Please let me know if this can be fixed or any idea on how to put the focus on Error messages?

This is a?little?urgent as we may have to remove the?Formidable form if the focus issues are not fixed from our websites.

Please help.

Thanks for your reply. Ticket created and submitted.

Thanks for your reply.
I have submitted a ticket.

Thanks again for such a prompt reply and for explaining the things in detail.

So what I did is that I cut the description out from its field and pasted the content into Title field and then I have Switched-OFF description and Switched-ON Title and now its all working fine as expected.

I will restructure the landmarks region for slider very soon.

Thank you very much for all your help. For a contribution from my side, I am going to write a blog mentioning the accessibility feature of your plugin in two of our website ?? I will update you once I finish writing the post.

Thanks for your reply Ramona.

I am using JAWS 2021 40 minute session Free edition.

I am also using WordPress 5.6.1 and Smart Slider 3 3.4.1.16.

I will share a few more details on your contact us support page.

Yes. Thank you very much. I have received a reply.

Thank you very much for such a quick response. I am expecting this release to happen quickly. Looking forward to it.

Sorry again, I found an easy fix for this. This file cookie-law-info\public\class-cookie-law-info-public.php, line no. 323 consist of <SPAN>. So rather than removing the code from the plugin, I updated the Privacy text from
Dashboard > GDPR Cookie Consent > Settings> Customize Cookie Bar > Message >

and replaced all DIV with SPAN and its validated HTML.

Temporarily, I have fixed this warning by adding landmark </footer> below wp_footer() on footer.php file in our custom theme.
…….
<?php wp_footer(); ?>
</footer>

One more Error get highlighted by https://validator.w3.org/ : –

Error: Element div not allowed as child of element span in this context. (Suppressing further errors from this subtree.) From line 657, column 80; to line 657, column 123

<!–googleoff: all–><div id=”cookie-law-info-bar” data-nosnippet=”true”><span><div class=”cli-bar-container cli-style-v2″><div class=”cli-bar-message”>

I have noticed one <SPAN> tag get inserted.