[Waiting for user confirmation] Form field label for= attribute not meeting accessibility standards

[Author]

Posts

[susanW-2]

We're using custom types and a custom archive pages for those type built with Blocks and custom search filters that are generating form attributes that are causing errors in our accessibility compliance tools.

An example of one of these archives is here:
hidden link

This page is generating source code like so:
----------------------------------------------------------------
<div class="form-group">

<label class="wpv-custom-search-filter__label" for="wpv-relationship-filter-department">

Departments

</label>

<span class="wpv-custom-search-filter__input">

<select id="wpv_control_select_wpv-relationship-filter" name="wpv-relationship-filter" class=" js-wpv-filter-trigger form-control" data-currentposttype="department">
----------------------------------------------------------------

Our University accessibility office tools call out that the label for= value should match either the name or the id. it currently matches neither.

This is an example and while we might be able to force a fix by hiding the field labels and inserting our own manually with HTML blocks, we're hoping that there is a more holistic approach through Toolset, or that you might put this in as a bugfix in an upcoming release.

Thanks,
Steve Segedy
UNC Chapel Hill LIbrary

[Minesh]

Hello. Thank you for contacting the Toolset support.

This is a known issue to us and I do not have any official workaround for now.

For now, you can add the solution as required and I've raised your voice to our internal ticket and I will get in touch with you as soon as I have any update on this.