Update: We are closing this case due to a lack of further information. If you have additional details, please share them, and we’ll be happy to reopen and continue assisting you.
Hi Hudson,
Can you please share what tool you used to verify this issue? If you check the produced DOM in DevTools source view you will find out that the browser has already stripped the duplicate span (since it is not allowed inside a select element) and only the external one continues to be available. Since there are no duplicate span elements, the content is validated fine with an accessibility checker like AXE, and the screen readers work fine with the produced content:
Regards,
Rumen
Progress Telerik