AccName: label vs contents

F2F Session — 1 hour

Chair: jnurthen

Objectives

  • Clarify whether AccName should split "label/name" from descendant content (#2623)
  • Revisit whether labels should override content and define precedence (#2569)
  • Produce decisions or concrete next steps (owners, tests, timelines)

Agenda (60m)

  1. 0:00–0:05 Welcome & objectives
  2. 0:05–0:30 Issue #2623: split name/label from contents (25m)
  3. 0:30–0:32 Transition (2m)
  4. 0:32–0:57 Issue #2569: label overrides content (25m)
  5. 0:57–1:00 Wrap-up: decisions, owners, next steps (3m)

Issue #2623 — Overview

Should AccName split name/label from contents (descendent text node contents)?

  • Current AccName concatenates descendant text and generated content
  • Some engines expose generated content as separate nodes
  • AT use cases differ

Options:

  1. Keep single computed AccName; add guidance/clarity
  2. Introduce explicit dual value (name/label vs contents)
  3. Hybrid: keep computed name but expose structured parts

Examples & snippets: snippets.md

Issue #2569 — Overview

"the age old question about whether a label should override content"

  • Precedence for aria-label / aria-labelledby vs content
  • Need clear precedence rules and author guidance

Examples: snippets.md

Decision capture & next steps

  • Record decision & rationale
  • Assign owners: spec editor, WPT author, implementer contact
  • Suggested timeline: prototype/WPTs within 6 weeks

Links & pre-reads