Hi there - when I run enlace oculto through the WAVE accessibility checker (enlace oculto ), it says the search filters are missing labels. The input and selects do have names that match the "for" on the labels, but they ideally need to match an ID specifically (enlace oculto ).
I'm adding the filters to the view like this:
<div class="form-group">
<label for="wpv_post_search">[wpml-string context="wpv-views"]Keyword[/wpml-string]</label>
[wpv-filter-search-box output="bootstrap"]
</div>
<div class="form-group">
<label for="wpv-resource-category">[wpml-string context="wpv-views"]Categories[/wpml-string]</label>
[wpv-control-post-taxonomy taxonomy="resource-category" type="select" default_label="All categories" url_param="wpv-resource-category"]
</div>
<div class="form-group">
<label for="wpv-resource-audience">[wpml-string context="wpv-views"]Audiences[/wpml-string]</label>
[wpv-control-post-taxonomy taxonomy="resource-audience" type="select" default_label="All audiences" url_param="wpv-resource-audience"]
</div>
<div class="form-group">
<label for="wpv-access-type">[wpml-string context="wpv-views"]Access types[/wpml-string]</label>
[wpv-control-post-taxonomy taxonomy="access-type" type="select" default_label="All access types" url_param="wpv-access-type"]
</div>
Is there a different way I could be doing this so the fields get added with IDs, and/or could adding the ID become an automatic part of the shortcode output?
thanks!
Sarah
Nigel
Colaborador
Idiomas:
Inglés (English )
Español (Español )
Zona horaria:
Europe/London (GMT+01:00)
Hi Sarah
We already have some requests about modifying the markup of the generated form inputs in this way.
I'm adding this thread to the internal ticket about this to try and raise the priority.
When I have some time later I'll take a look at the source code myself to see if I can help expedite a solution for this issue.
Nigel
Colaborador
Idiomas:
Inglés (English )
Español (Español )
Zona horaria:
Europe/London (GMT+01:00)
Just a note that I wasn't able to identify a way to make any changes to the form controls output without directly edited the plugin itself. But, having discussed with the developers, they have added it to the board for the current development sprint, so it will hopefully receive some attention before too long.
Thank you, Nigel - much appreciated!
-Sarah
Minesh
Colaborador
Idiomas:
Inglés (English )
Zona horaria:
Asia/Kolkata (GMT+05:30)
I've a news to share. We just released new version for Toolset plugins. Please check the following blog post for more details about bug fixes and new features:
- https://toolset.com/2026/06/toolset-1-7-complete-support-for-full-site-editing-with-blocks-and-views/
You can download the latest plugin version from the Downloads page:
- Toolset Type v3.6.2
=> https://toolset.com/download/toolset-types/#changelog
- Toolset Blocks v1.6.22
=> https://toolset.com/download/toolset-blocks/#changelog
- Toolset Forms v2.6.24
=> https://toolset.com/download/toolset-cred/#changelog
- Toolset Maps v2.2.2
=> https://toolset.com/download/toolset-maps/#changelog
- Toolset Access v2.9.5
=> https://toolset.com/download/toolset-access/#changelog
Can you please try to update all Toolset plugins and check if the issue you raised with this ticket is resolved.