Accessibility Issue – Missing Accessible Name for <select> Element
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Hello Pablo,
An accessibility audit using Google Lighthouse and axe DevTools identified the following issue:
The <select> element below does not have an accessible name, which violates accessibility requirements (WCAG 2.1):
<select id="woof_tax_select_product_cat" class="woof_select woof_select_product_cat" name="product_cat">
Error Message:
“The
<form>element has a<label>, which is not visible.”“
<select>elements must have an accessible name.”
Impact:
Screen reader users cannot identify the purpose of this dropdown field, creating a significant barrier for people with disabilities.
Can you help me?
Thank you for your support and assistance.
Hello
Please drop me exact link to the issue
Hello, I've added the URL to the hidden area.
All the tests I've done, including with other tools, give the same error.
Thanks for the help.
Hello
I checked your site - https://share.pluginus.net/image/i20250611110609.png docs - https://share.pluginus.net/image/i20250611110807.png
Hello Pablo, Is it possible that the second label (for="woof_....") refers to a non-existent or hidden element and that is why the accessibility error is triggered?
Thanks for Support
Hello
You can check it here - https://share.pluginus.net/image/i20250611110609.png
Hello Pablo,
I don’t want to display a visible label, but I would like the <select> element to be accessible.
Could you please add aria-label="" to the <select> element so that screen readers can properly recognize it?
Thank you very much for your support!
Hello
In the screenshot I showed that the select already has a label
We will add this in the next version.
Great, thank you very much!
Welcome;)
Hi Pablo, did the last update already include the extension? Because the Google test still displays this message even in the latest version.
And one more question: Can you also enter schema markup in the SEO extension for titles, text, etc.? That would be very important for our FAQ.
Unfortunately, using Wp-Bakery in the SEO texts is not possible at the time, despite your code.
Thanks for the support
Hello
Yes, we added aria-label as you asked, although it didn't make sense because we already have label. I'm not sure if we can do anything else and I don't understand why you get this error, regardless of the fact that the plugin doesn't have these problems.
Can you also enter schema markup in the SEO extension for titles, text, etc.? That would be very important for our FAQ. - Please describe in more detail what you want to get. I think this can be fixed with hooks.
Hello Pablo, to achieve a better ranking in the category, it would be important to be able to enter schema markup.
If I enter the code, I get errors and <script> etc. are removed.
<script type="application/ld+json">
{
"@context":"https://schema.org",
"@type":"FAQPage",
"mainEntity": {
"@type":"Question",
"name":"Test 1",
"acceptedAnswer": {
"@type":"Answer",
"text":"Test test"
}
}
}
</script>
The WPBakery design can't be adopted either.
It would be a huge boost for all websites if that were possible.
Regarding Google, I have no idea. I can't get any further with accessibility either.
axe Dev Tool also reports:
Ensure that <select> elements have an accessible name.
#woof_tax_select_product_cat
<select id="woof_tax_select_product_cat" class="woof_select woof_select_product_cat" name="product_cat">
To resolve this issue, you must fix the following:
The <form> element has a <label> that is not visible.
Thanks for the support
Hello
You can use this hook
add_filter('woof_seo_text', function($text){
return"Your text";
});
Or
add_filter('woof_seo_h1', function($title){
return"Title";
});
Hello, thanks for the feedback. Where should I add or adjust the hook?
Hello
Typically, custom PHP functionality is added to functions.php of a child theme. But if you have no experience in programming, it is better to consult with the developer about this customization.