Hi @shivaji
Are you using PX or % values at the Text bar’s font size? The PX values are fix, so if they don’t have sizing problem on desktop, then they shouldn’t have problem on mobile either.
If you’re using % value, either increase it or use PX.
I’ve run a test on our site where we have a slider with Text bar control, and I didn’t see any errors connected to that:
https://wave.webaim.org/report#/https://smartslider3.com/flickr-slider/
at this template we’re using PX font size.
On mobile size, the only errors I’m seeing is related to the mobile menu and the contrast of the links in the blue box:
https://imgur.com/WIv88km
If changing the font size to PX didn’t help (or you’re already using that), can you send me a link to your site? If you don’t want to put the link to a public forum, you can share it privately here:
https://smartslider3.com/contact-us/support/?topic=Other&platform=WordPress&version=Free&website=website-yes&ref=https://wordpress.org/support/topic/low-resolution-wcag-issue-for-text-bar-controll
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.
Hi @shivaji
Thanks for the link. I checked your site and what I can tell you that these reports have no connection to the Text bar.
In fact, I do think the test is wrong. Why? Because these warnings are connected to the hidden slide title what we placed the way it’s placed now, because it only needs to be accessible for screen readers, but not for normal users.
See: https://imgur.com/ssnpBI3
So this element is behind every element of the slide, it’s invisible, but it’s there for screen readers, and tests like this should ignore it, simply because the element is not visible at all. We’re only using this element so screen readers could properly introduce the slide on slide switching.
For some reason this wave tester doesn’t ignore this invisible element, even if it should. So you should just ignore the test, because it identified the issue false positively.
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.