Control Semantics Subgroup

Updates

Midpoint update, 21 November 2023

Subgroup members

​

• Jaunita George
• Azlan Cuttilan
• Chuck Adams
• Francis Storr

​

Goal

Write an exploratory version of the guideline and outcomes for Control Semantics. This work does not include writing how-to pages or methods.

​

Research

• 1.1.1 Non-Text Content
• 1.3.1 Communicate Semantic Info and Relationships
• 1.3.2c Dynamic elements inserted in reading sequence
• 1.3.5 Identify Input Purpose
• 1.4.11 Non-Text Contrast
• 4.1.2 a Name, Role, Value
• 4.1.2 b Programmatic identification of labels (Name)
• 4.1.2 c Programmatic identification of type of element (Role)

• 4.1.2 c Programmatic identification of state (State)
• 4.1.2 d Programmatic identification of values of user interface controls (Value)
• 4.1.3 Status Messages
• 4.1.3 a Programmatic status messages
• 4.1.3 b Status interrupt level
• 4.1.3 c Appropriate areas identified as messages

• COGA’s Use Clear, Unambiguous Formatting And Punctuation (Pattern)
• COGA’s Support A Personalized And Familiar Interface (Pattern)
• WebAIM discussion about Identify Input Purpose (specifically, the John Foliot email)

​

WCAG 2.x criteria

Other

Research - help needed

• We’re not finding much original research for this subject area—blogs and papers mostly link back to, or reference as the reason / requirement, WCAG 2.x.
• If you have, know of, or can help find, original research for this, please get in touch by emailing Jaunita George or any of the Control Semantics subgroup members.
• Groups we may need to hear from: HTML, Browsers, screen reader developers, universities engaged in digital accessibility research, AI experts.

User Needs And Structured Tests

• We’ve identified 16 user needs and 34 structured tests.
• We have noted areas where it felt as if we were going out of the scope of our goal. These may be useful for future work, so we’ve left them in our working documents.

Next Steps

• Continue to work on creating Test, Outcomes, and Methods.
• Create final PR