Purpose of controls

Due to the confusion around the Identify Common Purposes list of common purposes that occurred on the list this morning when we were making final comments about this, I have added an editor’s note to clarify that the user is the focus of the common control purposes.  This was clearly agreed on during the discussion on the call, and a more comprehensive resolution is likely warranted, but I did not want to make such a large change after the CFC has gone out.

The editor’s note emphasizes that the focus is the user:
“Editor’s Note: The intention of the Working Group is to scope the terms and definitions of the Control Purposes to be only about the user of the content. The note above was included to clarify this but some concerns have been raised that this is insufficient and that each definition should clarify this, in order to avoid authors thinking that they need to implement support for more controls than is necessary. The Working Group is interested in feedback on this specific question.”

See: http://rawgit.com/w3c/wcag21/purpose_of_controls_changes3/guidelines/index.html#commonpurposes

From the call this was the discussion notes:
Common Input Control Purposes
awk: is this all about USER INFORMATION
<lisa__> +1
awk: anyone not agree user information
no objections

I’m cc’ing the people who have already responded to the CFC here specifically to ensure that they can re-review this item.

Thanks again for the hard work everyone!


Andrew Kirkpatrick
Group Product Manager, Accessibility


Received on Saturday, 2 December 2017 00:51:19 UTC