F20 incorrectly maps to SC 4.1.2
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.5k
- Forks
- 533
- Avg merge
- 12h 3m
- Merged PRs (30d)
- 2
Description
F20 currently maps to both SC 1.1.1 and SC 4.1.2.
But SC 4.1.2 applies specifically to user interface components and requires that their name, role, and value be programmatically determinable. It does not require that an accessible name be meaningful or appropriate. The meaningfulness of an accessible name is addressed by other SC, such as SC 1.1.1 (for non-text content), SC 1.3.1, SC 2.4.6, ...
Since F20 concerns the use of text alternatives that do not adequately describe the purpose or meaning of the content, it does not necessary represent a failure of SC 4.1.2. Therefore 4.1.2 should be removed from the mapping for this failure technique.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the F20 failure technique at the linked WCAG Techniques page and inspect how its success-criterion mappings are represented in the repository. Remove the SC 4.1.2 mapping while retaining SC 1.1.1, then verify that the generated or rendered technique entry shows only the intended mappings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 74/100