@purpose

Hi All,
Earlier this afternoon, Charles and I were looking at the edits I made in
GitHub (I was struggling to be sure I did it all correctly), and during our
call we landed on something else, which I believe we also noted on today's
call, which is that we need to re-review our prose to ensure that
everything still 'syncs up' after the many minor edits we've made.

The current issue:
Currently, our 'description' for the @purpose attribute reads:


3.3.1 Description

The purpose attribute provides the context of a *text input field such as a
text box*. *It is typically used on an input of type text, or an element
with a corresponding role.*
A personalization agent may add a symbol, replace the text with a more
familiar term, or give it a specific presentation. Note that there is no
default value.
The user experience may include filling in the field (autocomplete) or
adding an icon to augment the input label.
The purpose values that would typically be on form inputs should provide
context for the user. For example tel would relate to the user's telephone
number.
*Note that there is no default value, and there can be more than one
space-separated value for a field.*

The concerns:

   1. I thought our attribute *could be used on more than just an input
   type of text* - in fact, that is one of the primary benefits to me,
   as @autocomplete cannot be applied to <select>, <legend> (or an aria
   grouping for radio buttons or check-boxes), nor radio buttons or
   checkboxes. As such I believe we need to re-author or modify the opening
   paragraph to better explain that the @purpose attribute can be applied to
   *ANY* form input. (Open question: can it be applied to a div marked as
   content editable?)

   2. The last paragraph - do we really anticipate a space
   separated collection of values for @purpose? Can anyone bring forth a
   use-case? (I can't), and so we may have to remove that final sentence
   (which also restates that there is no default value - so we need to tighten
   that text up anyway).

JF
-- 
*John Foliot* | Senior Industry Specialist, Digital Accessibility

"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"