-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Form fields for Mobile #529
Conversation
|
||
## Form field controls for mobile | ||
|
||
HTML5 form field controls should be used to automatically show the virtual keyboard. Placing labels above form fields is ideal for mobile layouts. On smaller screens, field labels may drop completely. Ensure that fields have text descriptions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HTML5 form field controls should be used to automatically show the virtual keyboard.
change to:
When HTML5 form fields are used, a virtual keyboard that allows easier input of the data is shown automatically: For example, a
number
field shows a numeric keyboard, adate
field a native date picker.
On smaller screens, field labels may drop completely.
Either say “visual field labels” or drop the sentence altogether (my preferred way). We could even say: “While some designs want visual field labels to be dropped, users prefer visible labels as they make the form easier to understand.”
Ensure that fields have text descriptions.
Unsure what this is referring to aria-describedby
sections? Might be confusing to have labels and descriptions in one paragraph and not to define both.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agree with "users prefer visible labels as they make the form easier to understand"
Also confused by "Ensure that fields have text descriptions." - aren't these form labels?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- @yatil's edit is clearer even though it adds length, prefer the suggested sentence.
- +1 to putting more detailed label guidance for responsive/mobile design on a labels page (and point to it)
- Agree precision is needed in reference to the option to "drop" labels
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to Eric's version. Would drop last sentence. Agree it is confusing.
I wonder if that should go to the labels page (as not everything has to do with labels). |
I agree with suggestions from @yatil for HTML5 form field use and virtual keyboard examples. For these two sentences:
We may need to provide more context about the design choice of hiding ("dropping") the labels on small screens and the responsibility to ensure the form remains usable and accessible with examples of 1) how to reflow labels visually to be above their fields, or 2) visually hide the labels and use other methods to describe the fields. Putting more detailed label guidance for responsive/mobile design on a labels page may make more sense than adding it to this page, too. |
Another note: In the WCAG 2.0 definition of labels, they are presented to all users.
I don’t know if we make that distinction throughout the tutorial, but when we talk about “dropping labels”, we probably want to be precise. |
Agree that additional clarification is needed. |
I’ll take a pass to use this great information and make a proposal (in the new design). |
Pulling together the suggested updates: I am happy with this and can make a new PR unless there are other comments. |
+1 to: "When HTML5 form fields are used, a virtual keyboard that allows easier input of the data is shown automatically: For example, a number field shows a numeric keyboard, a date field a native date picker. While some designs want visual field labels to be dropped, users prefer visible labels as they make the form easier to understand.” or with just a bit of wordsmithing : "When HTML5 form fields are used, a virtual keyboard appears making it easier to input data. While some designs want visual field labels to be dropped, users prefer visible labels as they make the form easier to understand.” I'm ok either way. |
Updates covered in #721. Closing PR. |
Proposed new subhead ("Form field controls") to improve mobile coverage for responsive design of forms.
If confirmed, add note "Developed with support from WCAG TA Project"
Could also add in resource section:
https://www.w3.org/TR/mobile-accessibility-mapping/#set-the-virtual-keyboard-to-the-type-of-data-entry-required