I'm developing an application where accessibility is very high priority, and I'm finding that every time I try to use one of your controls within the application, there is some sort of issue with its usability, mostly with screen readers. While I know that you are working on trying to make the controls more accessible, this appears to be slow going.
Further, I'm not seeing any options for workarounds. For example, most of the controls are missing certain aria labels that would make them viable to use with screen readers, but because you have deciding not to implement allowing arbitrary attributes / attribute splatting within your controls I can't do anything to get these controls working for screen reader users. As a result, I keep having to roll my own controls instead of using yours, even though in most cases your control is 90% there.
Take the Multi-select control. It has keyboard support, which is great, and it does read the options when navigating through the dropdown, but once you have selected an option, there is no way to get a screen reader to read any of the selected tags.
Another example is with your checkbox control. I need a way to set an aria-invalid attribute on the control, but I can't do so because your controls don't support attribute splatting: http://https://feedback.telerik.com/blazor/1416978-support-arbitrary-attributes?_ga=2.192430378.1005614243.1645625246-1187442152.1626202564
Other examples include:
I know that you are working on some of these things, but this is not something that I can wait months for to be released. So I'm asking are there any work arounds for some of these issues? If you had chosen to support arbitrary attributes, it would ease the frustration of waiting for a fix because we could have used that method as a workaround. Is there anything that I can do now to mitigate my issues short of writing the controls from scratch?