Clarify requirements for 1.3.5 Input purpose

[jfhector]

The content of the 'Requirements' section needs to be clarified in the detail page

A form may be written in a way where its purpose or the purpose of some of the components is not clear. This can be passed by using the
HTML 5.2 autocomplete attributes, on fields that collect information about the user.

Possible mis-alignment about what this particular success criterion requires, and what that means on iOS and Android

@KaneCheshire @geftimov:
I don't yet understand what the equivalent requirement is for iOS and Android. So I'm not sure 100% sure whether we're on the same page about what this particular WCAG success criterion is about.

• In HTML, the autocomplete attribute should only be used on input fields that collect information about the user themselves (as browsers will that attribute – eg autocomplete="given-name" – to suggest the auto-suggest the user's given name every time).
• Is this the same in iOS and Android?
  • In particular, I believe that in iOS and Android we can specify the type of information an text input field needs to collect (e.g. email, phone number). These 'types', I believe, are much broader that the possible values of the HTML autocomplete attribute, and don't trigger autocomplete.

On Android:

@geftimov:
I'm not sure that the current 'how to' for Android on the page matches this specific WCAG success criteria. :android:contentDescription="label", android:hint="label" and android:labelFor="@id/edit_text" seem to relate to Success Criteria 3.3.2 'Label and instructions' instead.