Registry · Operable

2.4.4 — Link Purpose (In Context)

Level A Operable

Operational summary

FOR EACH link, its text alone OR its text plus programmatically determinable context must communicate purpose, except where the purpose is ambiguous for people generally. Stronger standalone link naming may be a product policy, not the A-level minimum.

This is an original implementation summary, not replacement normative text. The sources below supply the precise requirement, its definitions and its qualifications.

Primary sources

• Normative text — W3C WCAG 2.2 Recommendation
• Understanding 2.4.4 — explanatory guidance

Registry record

Applicability and assessment start unset by design — no product has been evaluated. Instantiate the entry for an actual product, assign an owner and retain evidence.

{
  "criterion_id": "2.4.4",
  "level": "A",
  "name": "Link Purpose (In Context)",
  "rule_definition": "../03-WCAG22-AA-REGISTRY.md#sc-2-4-4",
  "normative_source": "https://www.w3.org/TR/WCAG22/#link-purpose-in-context",
  "understanding_source": "https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html",
  "applicability_status": "NOT_EVALUATED",
  "assessment_status": "NOT_TESTED",
  "owner": null,
  "test_instance_ids": [],
  "exception_evidence_ids": []
}

This criterion as JSON →