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.

Sign up for GitHub

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

Update Form field has non-empty accessible name [e086e5]: Added secondary requirements for 1.3.1 and 2.5.3 #2188

Merged
merged 5 commits into from
Aug 1, 2024
Merged

Update Form field has non-empty accessible name [e086e5]: Added secondary requirements for 1.3.1 and 2.5.3 #2188

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6023633
Added secondary requirements
giacomo-petri May 3, 2024
1e00400
Update _rules/form-field-non-empty-accessible-name-e086e5.md
giacomo-petri May 23, 2024
851413f
Update _rules/form-field-non-empty-accessible-name-e086e5.md
giacomo-petri May 23, 2024
3d774f1
Update _rules/form-field-non-empty-accessible-name-e086e5.md
giacomo-petri Jul 11, 2024
3864c98
Merge branch 'develop' into giacomo-petri-e086e5-added-secondary-requ…
Jym77 Aug 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions _rules/form-field-non-empty-accessible-name-e086e5.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,10 @@ accessibility_requirements:
failed: not satisfied
passed: further testing needed
inapplicable: further testing needed
wcag20:1.3.1: # Info and Relationships (A)
secondary: This success criterion is **more strict** than this rule. This is because 1.3.1 Info and Relationship requires that information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text, while 4.1.2 Name, Role, Value only requires an accessible name.
wcag20:2.5.3: # Label in Name (A)
secondary: This success criterion is **more strict** than this rule. This is because 2.5.3 Label in Name requires that if a label is visible, the accessible name contains the label that is presented visually, while 4.1.2 Name, Role, Value only requires an accessible name.
input_aspects:
- Accessibility Tree
- CSS styling
Expand Down
Loading