Bootstrap
form-floating accessibility? #39343
-
|
Are there any accessibility concerns when the label for an input comes after the input, like all of the examples for the form-floating feature? I really like how the fields are presented, but can't afford to sacrifice accessibility and put ourselves at risk of lawsuits. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
@patrickhlauke could confirm but I don't think there are any accessibility concerns with the form floating feature when the label for input comes after the input since they are "linked" with the |
Beta Was this translation helpful? Give feedback.
-
|
The one quirk with these is that if you're just using virtual cursor to read though the page, you will get a slightly odd order (matching the source order), but yes when navigating in forms mode, the form controls will be announced correctly based on their associated labels. Randomly, was thinking that for the next iteration of Bootstrap, we could experiment with using |
Beta Was this translation helpful? Give feedback.
-
|
for fun, I had a little play with how the |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for confirming "when navigating in forms mode, the form controls will be announced correctly" |
Beta Was this translation helpful? Give feedback.
The one quirk with these is that if you're just using virtual cursor to read though the page, you will get a slightly odd order (matching the source order), but yes when navigating in forms mode, the form controls will be announced correctly based on their associated labels.
Randomly, was thinking that for the next iteration of Bootstrap, we could experiment with using
:has()and the parent container to work around the need for the unusual sibling selector that requires this particular back-to-front ordering...