Hi @Jannis a website I’m working on has flagged up ‘errors’ with a WAVE audit report, I can manually address these, but will take a long time as I would have to do it on many pages. Before I do this I’ve got two questions if you could help me with this please?
I’ll explain the issues first. On the WAVE accessibility report a blog search is highlighted as an error bacause it does not have a descriptive label.
I see that this has the custom attribute already included that is name=‘Search’
However if I manually add an ARIA lebel as custom attribute aria-label=‘Search’ it satisfies the WAVE audit.
As you can see it no longer is flagged as an issue.
The same also happens for hidden form fields of the editor for blog posts. These show as errors, although not front facing to the viewer as they are only seen logged in with those, they still flag up as errors and start the questions within a government audit. If I add individual aria-label to each field they dissappear as a flagged ‘error’.
The website I have is made up from multiple blogs (12 in total) so that is many custom attributes to add for ARIA labels.
The two questions I have is:
-
If I add manual ARIA labels across the site to all form fields would these be overidden and removed by the default in a 1.x update or a future upgrade to version 2?
-
Or could aria-label=‘name of the field’ be added to form fields in Volt in an update?
Thanks
Ben