Part of Item:
Comment Type: TE
Comment (including rationale for proposed change):
I am doing final copy editing of a book chapter on forms.
I had talked about how clear the January version of WCAG20 was about forms:
SC 4.1.3 The label of each user interface control in the Web content that accepts input from the user can be programmatically determined and is explicitly associated with the control.
But now that has apparently been replaced by:
SC 4.1.2 For all user interface components, the name and role can be programmatically determined, values that can be set by the user can be programmatically set, and notification of changes to these items is available to user agents, including assistive technologies.
The problem is that 4.1.2 is absolutely inadequate. The \"Role\" of text input field is \"text input\"; the name could be \"keyinput\". 4.1.2 is basic software accessibility - leaving to the AT the process of figuring out what the prompt (label) is.
I just talked with John (who sounds terrific) and he pointed out that -
1.3.1 Information and relationships conveyed through presentation can be programmatically determined, and notification of changes to these is available to user agents, including assistive technologies.
Served the same purpose as 4.1.3 - I agree. But it is abstract. It requires interpretation.
With the Last Call version of WCAG 2.0 there is no success criterion that specifically addresses labeling forms and I think that is a very serious mistake.
Please reinstate 4.1.3.
The WG feels this requirement is properly covered under 4.1.2 and did not wish to reinstate a SC that would be redundant with that. However, we agree that it's difficult for users to understand that form labeling is part of 4.1.2. We have added a failure and an advisory technique to SC 1.3.1 and 4.1.2:
F68: Failure of 1.3.1 and 1.4.2 due to the association of label and user interface controls not being programmatically determinable
Providing labels for text input or item selection form controls (future link)