hmsproducts

Wondering if there is any insight on this problem. Three weeks is a long time with no response.

Thanks.

Tom,

I definitely can see your point. Thanks for the consideration. We can certainly work around this, but, I wanted to see if you thought it was possible.

Thanks again,
HMS Products

Tom,

Thanks for the quick response. You are definitely correct that zoom should work, but, the sufficient techniques for meeting WCAG 2.0 AA (1.4.4 Resize text Level AA) indicate to use relative font sizes:

Ensuring that text containers resize when the text resizes AND using measurements that are relative to other measurements in the content (future link) using one of the following techniques:
C28: Specifying the size of text containers using em units
Techniques for relative measurements (future link) using one of the following techniques:
C12: Using percent for font sizes
C13: Using named font sizes
C14: Using em units for font sizes

https://www.w3.org/WAI/WCAG20/quickref/?showtechniques=144#qr-visual-audio-contrast-scale

We are using SortSite by PowerMapper for our accessibility scans.

Thanks for a great plugin!
HMS Products

Thanks for being so responsive!

Keep up the great work,
HMS Products

Curtis,

Actually, I think that I found it. It wasn’t the banner, but, the third-party “find a car” widget. Could have sworn I checked that.

Sorry for the trouble. Thanks for your help and keep up the good work!

Sincerely,
HMS Products

That’s interesting. I have tried it on three different machines and it doesn’t work. Also, when looking at the console, I am seeing the following:

Uncaught TypeError: jQuery.jAlert is not a function
at HTMLAnchorElement.exit_notifier_leave_now (frontend.js?ver=1.4.3:14)
at HTMLDocument.dispatch (jquery.js?ver=1.12.4:3)
at HTMLDocument.r.handle (jquery.js?ver=1.12.4:3)

Thoughts?

Thanks,
HMS Products

I found the remaining issue. It was from Lightbox Evolution plugin (removed from WP Plugin repository) that was using obfuscated code. Removed it and the Sucuri scan is now coming up clean. Still, thought, Wordfence still didn’t find that either, which is a bit concerning.

Good luck!

It’s finding the following. The payload was in the plugin files that I deleted, but, I am not finding it anywhere else in the site.

malware.generic_jsobfuscator

Thanks!

First, great plugin, easy for clients to use and understand. I agree with PXMstaff if the pause/play options could be added to be turned off/on, that would be a huge enhancement. WCAG/508 is the elephant in the room for web dev/design. More industries are getting compliance pressure to meet the WCAG and are getting sued if they don’t.

I definitely want to add my vote to have this included in a future release.

Thanks
hmsproducts

Tom,

Actually, after looking at this again, I am still seeing the CSS content property and I am getting an error on my WCAG scan. I do have Version 2.4.0.3 installed.

Sorry for the oversight. Looks like this isn’t resolved.

Thanks!

Tobias,

First, you have a great plugin that’s easy for users to manage. The import/export feature is especially helpful.

Thanks for the quick response. Adding the option to apply the table role might be good for a future release. For many industries, WCAG adherence is becoming more and more important and since some use tables for layout rather than HTML (because it’s easy for them), there needs to be a way to apply the role.

Thanks for a great plugin and keep up the good work.

Tom,

Excellent! Changes confirmed. Thanks for fixing this so quickly!

maspegren,

I can definitely see how that would work for the title attribute, but, WCAG requires a label on any form control.

However, I used a combination of the “.on(‘load’…” and the code I had and it seems to be working:

var label = ('<label for="targetLang" class="offscreen">Search</label>');
$(window).on('load', function() { 
  $('#google_language_translator select.goog-te-combo').attr('id', 'targetLang');
  $('#google_language_translator select.goog-te-combo').before(label);
});

Thanks for the “.on(‘load’)” idea!

We have run into the exact same issue. Last major issue for WCAG 2.0 AA we have on the board. I, too, have tried to add it with JS/jQuery and the timing of the Google API just doesn’t match up with the setTimeout to get it to load properly.

Please add the label for the SELECT dropdown. It could even be added off screen, we just need it there so that screen readers and other assistive technology can access it.

Or, as maspegren says, “tell me if there is another way to add this…”

Thanks!