Currency Selector Associated Label Elements

[T.A. Garrison, LLC]

The "Currency Selector" and all else function just fine.
However, Lighthouse throws a warning for "each" instance where there is no "label" for the element.

I'm trying to find the file(s) for Currency Selector so that I can add the label for the "Select" which is default in the drop-down list.
Specifically, the file that generates the HTML is the file I'm trying to find.

Working with AI on other areas of VM that throw warnings to Lighthouse, I found the correct method to label things in order for the visually impaired using screen readers to have the screen reader call out what the user cannot see.
As VM is coded now, there no label for "Select", and the visually impaired cannot read that with their reader.

This is part of SEO and can be significant if left unresolved in a site with thousands of products, each of which has no label for "Select".

[T.A. Garrison, LLC]

For those who have been "reading", since we've had no response, I've spent the last 3 days with AI to overcome the issues.

This was NOT a simple fix, although if I were to provide the answer here it would be...for you.

Suffice it to say that I will add the resolve here if anybody would like. I'm just too burned out today to write it all.

This fix will allow you to get all the warnings for each product select drop-down and Currency Selector drop-down select too, completely gone.
I raised my Accessibility in Lighthouse from 69 to 92 (still have to deal with the pagination that is too close together and the text is too small to satisfy Lighthouse).

Leave a note if you want the solution.

By the way. In the class tag of "bs4-customfields.php", the CSS is "display:none;" which directly effects the label that is in that file.
That label is also in every product. Therefore, I have 300 products (will soon be thousands) and each one has the Lighthouse warning (at least before I fixed all of them).

That label "must NOT" be display:none;
That not only hides the label from visually displaying in the site, but it also blocks the label for screen readers. So what's the point of it being there?
I'm guessing the developer didn't know that and thought display: none; would suffice.