Accessibility Proposed WCAG 20 Techniques
From MemberWiki
Accessibility Home | Issue Tracker | WCAG 2.0 Rules | Rules Format 1.0 | Cache | Proposed WCAG 2.0 Techniques | Rule Review | Testsuite | Evaluation Results | Reporting Practices
Contents |
Proposed WCAG 2.0 Rules
2.4.4 Link Purpose (In Context)
Problem with WCAG Techniques
The current WCAG techniques document makes this requirement very easy to pass and in general will have very little impact on improving accessibility. It puts most of the burden on the AT user to figure out the context (if any) that helps identify the purpose of a link based on context of the link.
Proposed Improvement in WCAG 2.0 Techniques
Authors should be required to identify the context used to identify the link by using one of the following techniques:
| Number | Technique |
|---|---|
| 1 | title attribute |
| 2 | aria-label attribute |
| 3 | aria-labelledby attribute |
Assistive technologies could use this information about a link. Preference order for more information:
- aria-labelledby computed label
- aria-label attribute value
- title attribute value
Proposed Additions to HTML 5
- Provide a context-value attribute for links
- Provide a context attribute for links that would function the same as aria-labelledy
Benefits to Authors and Users
- Provide a computational method to identify the context being used for a link
- The computational method can help authors identify link context accessibility problems
- Improved experience for users with disabilities to not have to try to guess what context if any is being used to help identify a link
- Link context is especially important since link 2.4.9 Link Purpose (Link Only) is a AAA requirement making one of the biggest usability problems for everyone on the web, including people with disabilities, a very low priority of implementation.
