-
Notifications
You must be signed in to change notification settings - Fork 70
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
Visible label is part of accessible name indicates that inputs are not applicable because the label is not contained in the input #1500
Comments
Hey @mraccess77 ! The visible label rule does not apply to |
SC 2.5.3. does apply to input though - so it sounds like we need to clarify that and create a different rule for inputs -- is that correct? I'm just thinking that some folks may get confused and assume that 2.5.3 doesn't apply to inputs because of this while it seems like you have just limited the scope of this test to certain situations which I missed. |
The Background section has a note with the list of applicable elements. Another rule for |
Input elements aren't named from content. They were left out of this rule because it is much more difficult to programatically tell which element outside the widget is supposed to be the label. Even if there is a literal A separate rule for labels that aren't part of the control would indeed be necessary. The gap is intentional, because of the difficulty in doing this programatically. |
Suggestion: write a rule that checks that there is a text node on the page that is included in the accessible name of "named from author" elements. |
The rule for visible label https://act-rules.github.io/rules/2ee8b8 seems to indicate that this test is applicable to inputs as the visible label is not contained within it. If I understand that correctly that seems to contradict the intention of SC 2.5.3 Label in Name which applies to user interface elements.
The text was updated successfully, but these errors were encountered: