[Resolved] search input field does not have a matching label

[Author]

Posts

[judeH-2]

I am trying to: To be ADA compliant, I tested my site with the Chrome WAVE extension. On page like hidden link, the extension reports that the search field on the left and the min/max date don't have the matching label.

To be more specific, the Search label field looks like <label class="wpv-custom-search-filter__label" for="post-search">Modify your search</label>. So it's for "post-search". But the input field below, it looks like <input type="text" name="wpv_post_search" class="js-wpv-filter-trigger-delayed form-control">. As you can see there is no id field. According to the compliance document, the label for field should match the input ID field.

For the date min field, the label is <label class="wpv-custom-search-filter__label" for="wpcf-publish-date_min">From</label>, while the input field looks like <input type="text" id="wpv_control_textfield_wpv-wpcf-publish-date_min" name="wpv-wpcf-publish-date_min" value="" class="js-wpv-filter-trigger-delayed form-control" placeholder="mm/dd/yyyy"> As you can see the for field and ID field don't match.

I don't believe I can change these values in the UI.

Link to a page where the issue can be seen: hidden link

I expected to see: For compliance details, please see example 2 on hidden link

Instead, I got:

[judeH-2]

The Tag dropdown on the left has a similar problem.

[Minesh]

Hello. Thank you for contacting the Toolset support.

Making Toolset plugins ADA compliant needs lots of work but first of all let me first dive into this and check and I'll report this to concern department and file a ticket for improvements. I'll update you here as soon as possible when I work on this latest by tomorrow.

[Minesh]

I've escalated the issue to our next level support and please note that there is no ETA on it when the fix will be offered.

There is no alternate workaround for now, maybe you can use JS but it will be extensive work again to apply custom Javascript everywhere. Hopefully our Devs will have eye on it and they should plan to make it ADA compliance but no promises on when or how long it will take.