Registry · Perceivable
1.3.5 — Identify Input Purpose
Level AA Perceivable
Operational summary
IF a field collects information about the user covered by the WCAG input-purpose taxonomy AND the technology supports identification, encode that purpose programmatically. Check appropriate autocomplete tokens and actual field purpose rather than blindly adding tokens everywhere.
This is an original implementation summary, not replacement normative text. The sources below supply the precise requirement, its definitions and its qualifications.
Primary sources
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": "1.3.5",
"level": "AA",
"name": "Identify Input Purpose",
"rule_definition": "../03-WCAG22-AA-REGISTRY.md#sc-1-3-5",
"normative_source": "https://www.w3.org/TR/WCAG22/#identify-input-purpose",
"understanding_source": "https://www.w3.org/WAI/WCAG22/Understanding/identify-input-purpose.html",
"applicability_status": "NOT_EVALUATED",
"assessment_status": "NOT_TESTED",
"owner": null,
"test_instance_ids": [],
"exception_evidence_ids": []
}