Registry · Understandable

3.3.7 — Redundant Entry

Level A Understandable

Operational summary

IF information already entered by or supplied to a user is requested again within the same process, prefill it OR offer selection. Review essentiality, security and no-longer-valid-information exceptions; unrelated sessions are not automatically one process.

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 3.3.7 — 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": "3.3.7",
  "level": "A",
  "name": "Redundant Entry",
  "rule_definition": "../03-WCAG22-AA-REGISTRY.md#sc-3-3-7",
  "normative_source": "https://www.w3.org/TR/WCAG22/#redundant-entry",
  "understanding_source": "https://www.w3.org/WAI/WCAG22/Understanding/redundant-entry.html",
  "applicability_status": "NOT_EVALUATED",
  "assessment_status": "NOT_TESTED",
  "owner": null,
  "test_instance_ids": [],
  "exception_evidence_ids": []
}

This criterion as JSON →