Jackpot casino sign up bonus.Claim Your Free 999 Pesos Bonus Today

Follow-Up on WCAG Accessibility Issues – Urgent Attention Needed

kim.oj — Thu, 20 Mar 2025 09:17:05 +0000

Hi,

Around 10 months ago, I reached out regarding accessibility issues (WCAG) with your plugin, specifically about adding support for tab navigation and keyboard navigation for expanding elements. Here is the original thread: https://www.ads-software.com/support/topic/accessibility-issues-wcag-2/.

At the time, I received a response stating that these issues would be addressed soon. However, I still notice that the problem persists, and with the upcoming enforcement of EU accessibility laws, we will be required to ensure compliance. If these issues aren’t resolved soon, we may need to consider switching to an alternative plugin.

I would appreciate any updates on when this will be addressed. Your prompt attention to this matter is crucial.

Best regards,
Kim

focus styles are not visible

kmbrlyb — Mon, 17 Mar 2025 03:06:17 +0000

I am tasked with creating a website that is 100% accessible. A few months ago I downloaded your plugin and realized that everything was working well accept the focus states weren’t visible with keyboard navigation. So I used some CSS to make this work (I’m no expert, but Chat GPT helped me come up with something.) However, with the latest upgrade, the added CSS is no longer working. And I’ve run out of ideas. Can you please help me? Keyboard navigation is a requirement to be WCAG compatible and ADA compliant.

WCAG compatibility

docleads — Mon, 24 Feb 2025 14:26:42 +0000

I have integrated the plugin on several customer websites. I am currently making the website accessible as part of the WCAG. Unfortunately, with this plugin, the “read more” and also the date in the integration of the widget are displayed with insufficient contrast as errors. The “read more” and the date are formatted in light gray on white, which is not easy to read. The contrast should be higher in order to comply with the WCAG 2.2 AA guidelines. Can you please adjust this or tell me how I can format the two affected areas in a different color myself?

Accessability (WCAG) compliant

Johan Jonk Stenstr?m — Mon, 17 Feb 2025 09:55:25 +0000

The search form is missing a label and is not accessible to screen readers.

So I’d suggest adding this:

The “screen-reader-text” class will make sure that the label is only accessible by screen readers: https://make.www.ads-software.com/accessibility/handbook/markup/the-css-class-screen-reader-text/

Accessibility Improvements request

simplesteps — Thu, 13 Feb 2025 14:29:36 +0000

Hi the plugin is great but some options on it lack accessibility, I am referring to the “live search feature”, first issue is the focus order when a user types in the search input field, it popout the suggested link or drop downs, when the user presses the tab key the focus jumps to the list of links that are been suggested, this breaks the Success Criterion 2.4.3 (Focus Order) since most search has the submit or search button next to the field the focus should go directly to the object next to the input search field, a fix would be to keep the focus order correct when usign the tab key or do not focus inside the suggested box by tab instead by arrow keys.

The other issue I see is that this dropdown should be announced to screen readers so I suggest an aria-live=”polite” for this 4.1.3: Status Messages

Hope this helps

Need to change h4 to h3 for proper heading architecture

kmbrlyb — Mon, 27 Jan 2025 00:03:22 +0000

My testimonial’s author designation is given an h4 class which breaks my heading architecture and thus does not meet WCAG 2.1 Accessibility criteria. I need to change it to an h3. How would I do that?

Great BUT… Needs to be Accessible

Frank Gomez — Thu, 23 Jan 2025 21:01:23 +0000

I tried using my keyboard to navigate through the reviews and I wasn’t able to. Also the contrast for the read more links (maybe should say “read review”) is insufficient.

Disable “New Window Warning” Info on the Backend?

aklpl — Thu, 23 Jan 2025 16:16:50 +0000

This is actually a backend question, not a frontend question:

I currently use the “Accessibility New Window Warnings” plugin by Equalize Digital in an effort to meet accessibility standards for alerting users when a link will be opening in a new tab or window. I understand this importance for website users on the frontend, but the icons and notifications on the backend can be frustrating and confusing (especially when they cover up what we staff are trying to work on). Is it possible to disable the icons and pop-ups on the backend/admin side?

Thanks!

Disable “New Window Warning” Info on the Backend?

aklpl — Wed, 22 Jan 2025 20:22:47 +0000

This is actually a backend question, not a frontend question:

Thanks!

Need help adding padding to radio buttons

kmbrlyb — Thu, 16 Jan 2025 22:54:15 +0000

I need help adding padding to the Forminator radio buttons. I currently have 20 px radio buttons but want to add 12px padding so that the targetable area is increased to 44px to meet WCAG 2.1 standards. I’m working on a Medical office that needs to be compliant. I am happy to add CSS in Appearance in Forminator but don’t know the correct coding.