Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(multiple): remove label for attribute on non-native elements #2258

Merged
merged 1 commit into from
May 7, 2024

Conversation

mhaertwig
Copy link
Collaborator

Adds an option to remove the for attribute from the <label> inside the form field from elements that can't be labeled. Also applies the new option to sbb-select and sbb-textarea. This isn't an accessibility regression, because those elements were already being labeled using aria-labelledby. Fixes #1918

Adds an option to remove the `for` attribute from the `<label>` inside the form field from elements that can't be labeled. Also applies the new option to `sbb-select` and `sbb-textarea`. This isn't an accessibility regression, because those elements were already being labeled using `aria-labelledby`.
Fixes #1918
Copy link
Collaborator

@kyubisation kyubisation left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@mhaertwig mhaertwig merged commit 1032655 into main May 7, 2024
18 checks passed
@mhaertwig mhaertwig deleted the feature/label-attribute branch May 7, 2024 15:08
sbb-design-systems-bot bot pushed a commit that referenced this pull request May 7, 2024
Adds an option to remove the `for` attribute from the `<label>` inside the form field from elements that can't be labeled. Also applies the new option to `sbb-select` and `sbb-textarea`. This isn't an accessibility regression, because those elements were already being labeled using `aria-labelledby`.
Fixes #1918
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Page error "Incorrect use of <label for=FORM_ELEMENT>"
2 participants