[QUESTION]: SKOs change to modern HTML or not..?

[Timo-Breumelhof]

Is there an existing issue for this?

• [X] I have searched the existing issues

Description of problem

I was working on the Language SKO and one of the issues with these is that they are based on classic webforms controls. As an example this SKO can render a dropdown list (<select>) to switch the language. That is wrong in many ways but mainly Accessibility. Now do you leave this the way it is or just remove the legacy / non compliant options? For this SKO you can also create UL with the other rendering option the SKO offers (using a template), which would be much better. I know I know, scope-creep, but still. Opinions?

Description of solution

Not sure yet

Description of alternatives considered

No response

Anything else?

No response

Do you be plan to contribute code for this enhancement?

• [X] Yes

Would you be interested in sponsoring this enhancement?

• [ ] Yes

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[sachatrauwaen]

It's surrly not a problem to start only without legacy option. You can for exemple just generate a text "legacy not implement" in of use of legacy option.

[Timo-Breumelhof]

Actually I did integrate it for this one but I think I'll skip the legacy option for the other ones. A message sounds like a good idea..