fix: 🐛 make validation more accessible in all form elements

[Vahid1919]

Description:

Closes #1483

@solid-design-system/core-development There is a disclaimer that changes made here will affect all other form-related components. In code, the fieldset element is defined inside sd-radio-group. I do not see how it has an effect on the other components since the only relation to the formController is referencing the id to link the labels.
Please let me know, if I am incorrect here.

Definition of Reviewable:

• relevant tickets are linked

[github-actions]

🚀 Storybook has been deployed for branch fix_sd-radio-group-a11y

• View Storybook

[karlbaumhauer]

@Vahid1919 the issues mentions a problem about missing labels on icon only templates. Did you check that (as I am missing changes on this topic)?

I also would like to clarify in the daily, if someone remembers what exactly we wanted to accomplish with the mentioned note/caution hint in the ticket. I second that I don't see a problem with the changes in any other component but we added it for some reason...;)

[Vahid1919]

@solid-design-system/core-development I have addressed the recommendations regarding reporting errors on screen readers.

I managed to get error messages to be communicated in almost all form elements except sd-radio-group (does not work on Chrome but works fine on Safari -- both tested with VoiceOver).

I found some forum discussions regarding what to do in case of screen-reader differences while testing: https://club.ministryoftesting.com/t/why-do-screen-readers-behave-so-differently-from-one-another/69298

How would you suggest we handle these differences right now? @mariohamann @smfonseca @karlbaumhauer

PS: I tried some "hacks" using aria-labelledby that allow screen reader error reporting in Chrome, but those cause duplicate readings on Safari.

[mariohamann]

Apparently there seems to be an issue with how radio-button then handles some stuff in comparison to radio? Did you make a comparison on what's the difference? I would be fine if you would extract that issue in a new ticket, if you could properly document, what's happening and what you did.

[Vahid1919]

VoiceOver issues for sd-radio-group will now be handled here: #1648