You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2023. It is now read-only.
I feel the intro discussion of the React to EU talk is slightly misguiding.
Passing aria-required as true would only make it required for a11y users but would not change the behavior of the input to actually be required. it is better to use the html required attribute
In the checkbox example, since you are using the html checkbox, there is no need to use the aria-checked attribute, and since the checkbox is already nested inside the label there is no need to use the aria-labelledby. the usage of aria-labelledby is also incorrect as it only works with IDs but you are referring to a classname.
You slightly touch on the native a11y capabilities of the input type checkbox while building the common component later.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I feel the intro discussion of the React to EU talk is slightly misguiding.
Passing aria-required as true would only make it required for a11y users but would not change the behavior of the input to actually be required. it is better to use the html required attribute
In the checkbox example, since you are using the html checkbox, there is no need to use the aria-checked attribute, and since the checkbox is already nested inside the label there is no need to use the aria-labelledby. the usage of aria-labelledby is also incorrect as it only works with IDs but you are referring to a classname.
You slightly touch on the native a11y capabilities of the input type checkbox while building the common component later.
The text was updated successfully, but these errors were encountered: