Form Best Practices<\/h2>\r\nProvide clear instructions<\/h3>\r\nStart your form with clear instructions. Include information about:\r\n\r\n \t- Number of questions.<\/li>\r\n \t
- Time limit (if applicable).<\/li>\r\n \t
- Due date (if applicable).<\/li>\r\n \t
- How to complete the questions.<\/li>\r\n \t
- What the survey is about.<\/li>\r\n \t
- How required fields will be indicated\r\n
\r\n \t- o Plain text \u201crequired\u201d in the visible form label is the best method.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Instructions for form fields that require specific formatting or other requirements.<\/li>\r\n \t
- Help or contact information.<\/li>\r\n<\/ul>\r\nClear instructions help respondents budget their time, manage their expectations, and understand the purpose of the survey.\r\n
Use Plain Language<\/h3>\r\nUse simple and direct language that everyone can understand. Avoid jargon, abbreviations, and acronyms or when you use them, explain them when they first appear. Avoid negative questions that might confuse respondents by requiring a \u2018Yes\u2019 to confirm a negative.\r\nIndicate Required Fields<\/h3>\r\nIndicate required fields in plain text labels or question prompts. Don\u2019t rely on colour alone to indicate a required field.\r\nInclude Field Labels<\/h3>\r\nEvery field should have visible labels and example placeholder text in the fields. Add meaningful labels above or to the left of each field.\r\nNumber Questions<\/h3>\r\nNumber each question and add a progress indicator to help respondents to understand the survey\u2019s length.\r\nAllow Saving Progress<\/h3>\r\nIf the platform allows, give respondents the option to pause, save, and resume the survey later.\r\nAvoid Time Limits<\/h3>\r\nDo not impose a time limit on respondents unless essential to the purpose.\r\n\r\nIf a time limit is needed:\r\n\r\n \t- Clearly communicate the time limit in the instructions.<\/li>\r\n \t
- Provide a warning before time runs out.<\/li>\r\n \t
- Offer a method to extend time at least once.<\/li>\r\n \t
- Make sure the timer is obvious and accessible without being intrusive.<\/li>\r\n<\/ol>\r\n
Avoid Space Constraints<\/h3>\r\nUse long text or rich text fields that allow respondents adequate space to answer. Ensure forms display properly on a mobile device. Pay attention to the layout of multiple-choice and radio buttons.\r\nError Messages<\/h3>\r\nIf respondents make mistakes or enter invalid data, show accessible error messages that specify the incorrect field and provide guidance on the required formatting. For example: \u201cDates should all be entered in the format mm\/dd\/yyyy, (as in 06\/29\/2023)\u201d or \u201cPasswords must contain at least 8 letters and\/or numbers.\u201d\r\nCheck Focus Order<\/h3>\r\nTest the keyboard functionality of your form to ensure the focus order follows the visual layout. Use Tab<\/strong> to move between fields, Space<\/strong> to open a menu and select checkboxes, and arrow keys to navigate menus and radio buttons.\r\n\r\nEnsure there is an obvious visual indicator when a form field has keyboard focus, such as a noticeable ring around the field.\r\nAdd Submission Confirmation Message<\/h3>\r\nAfter clicking the submit button, include a confirmation dialogue to prevent accidental incomplete submissions.","rendered":"
![\"\"](\"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-content\/uploads\/sites\/1155\/2023\/08\/My-project-1-47-2-300x300.png\")
<\/p>\n
Online forms are useful for data collection and surveys. Accessible forms are designed to meet the access needs of all respondents. Accessible forms increase inclusivity, usability, and the number of people who can participate.<\/p>\n
There are different online tools available, but it’s essential to consider the content and structure of your form or survey to make it accessible.<\/p>\n
Here are some best practices to improve accessibility, usability, and effectiveness of online forms:<\/p>\n
Suggested Platforms<\/h2>\n
At Langara, we support Microsoft Forms<\/a>, Brightspace Surveys<\/a>, and Zoom polls<\/a>. These platforms offer various question types and features. Consider that Zoom polls must be set up before the meeting begins.<\/p>\nAvoid SurveyMonkey and Wufoo as they present many accessibility barriers to users.<\/p>\n
Form Best Practices<\/h2>\nProvide clear instructions<\/h3>\n
Start your form with clear instructions. Include information about:<\/p>\n
\n- Number of questions.<\/li>\n
- Time limit (if applicable).<\/li>\n
- Due date (if applicable).<\/li>\n
- How to complete the questions.<\/li>\n
- What the survey is about.<\/li>\n
- How required fields will be indicated\n
\n- o Plain text \u201crequired\u201d in the visible form label is the best method.<\/li>\n<\/ul>\n<\/li>\n
- Instructions for form fields that require specific formatting or other requirements.<\/li>\n
- Help or contact information.<\/li>\n<\/ul>\n
Clear instructions help respondents budget their time, manage their expectations, and understand the purpose of the survey.<\/p>\n
Use Plain Language<\/h3>\n
Use simple and direct language that everyone can understand. Avoid jargon, abbreviations, and acronyms or when you use them, explain them when they first appear. Avoid negative questions that might confuse respondents by requiring a \u2018Yes\u2019 to confirm a negative.<\/p>\n
Indicate Required Fields<\/h3>\n
Indicate required fields in plain text labels or question prompts. Don\u2019t rely on colour alone to indicate a required field.<\/p>\n
Include Field Labels<\/h3>\n
Every field should have visible labels and example placeholder text in the fields. Add meaningful labels above or to the left of each field.<\/p>\n
Number Questions<\/h3>\n
Number each question and add a progress indicator to help respondents to understand the survey\u2019s length.<\/p>\n
Allow Saving Progress<\/h3>\n
If the platform allows, give respondents the option to pause, save, and resume the survey later.<\/p>\n
Avoid Time Limits<\/h3>\n
Do not impose a time limit on respondents unless essential to the purpose.<\/p>\n
If a time limit is needed:<\/p>\n
\n- Clearly communicate the time limit in the instructions.<\/li>\n
- Provide a warning before time runs out.<\/li>\n
- Offer a method to extend time at least once.<\/li>\n
- Make sure the timer is obvious and accessible without being intrusive.<\/li>\n<\/ol>\n
Avoid Space Constraints<\/h3>\n
Use long text or rich text fields that allow respondents adequate space to answer. Ensure forms display properly on a mobile device. Pay attention to the layout of multiple-choice and radio buttons.<\/p>\n
Error Messages<\/h3>\n
If respondents make mistakes or enter invalid data, show accessible error messages that specify the incorrect field and provide guidance on the required formatting. For example: \u201cDates should all be entered in the format mm\/dd\/yyyy, (as in 06\/29\/2023)\u201d or \u201cPasswords must contain at least 8 letters and\/or numbers.\u201d<\/p>\n
Check Focus Order<\/h3>\n
Test the keyboard functionality of your form to ensure the focus order follows the visual layout. Use Tab<\/strong> to move between fields, Space<\/strong> to open a menu and select checkboxes, and arrow keys to navigate menus and radio buttons.<\/p>\nEnsure there is an obvious visual indicator when a form field has keyboard focus, such as a noticeable ring around the field.<\/p>\n
Add Submission Confirmation Message<\/h3>\n
After clicking the submit button, include a confirmation dialogue to prevent accidental incomplete submissions.<\/p>\n","protected":false},"author":1655,"menu_order":13,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-4347","chapter","type-chapter","status-publish","hentry"],"part":62,"_links":{"self":[{"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/chapters\/4347","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/wp\/v2\/users\/1655"}],"version-history":[{"count":17,"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/chapters\/4347\/revisions"}],"predecessor-version":[{"id":9570,"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/chapters\/4347\/revisions\/9570"}],"part":[{"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/parts\/62"}],"metadata":[{"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/chapters\/4347\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/wp\/v2\/media?parent=4347"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/chapter-type?post=4347"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/wp\/v2\/contributor?post=4347"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/wp\/v2\/license?post=4347"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- \r\n \t
- Number of questions.<\/li>\r\n \t
- Time limit (if applicable).<\/li>\r\n \t
- Due date (if applicable).<\/li>\r\n \t
- How to complete the questions.<\/li>\r\n \t
- What the survey is about.<\/li>\r\n \t
- How required fields will be indicated\r\n
- \r\n \t
- o Plain text \u201crequired\u201d in the visible form label is the best method.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Instructions for form fields that require specific formatting or other requirements.<\/li>\r\n \t
- Help or contact information.<\/li>\r\n<\/ul>\r\nClear instructions help respondents budget their time, manage their expectations, and understand the purpose of the survey.\r\n
Use Plain Language<\/h3>\r\nUse simple and direct language that everyone can understand. Avoid jargon, abbreviations, and acronyms or when you use them, explain them when they first appear. Avoid negative questions that might confuse respondents by requiring a \u2018Yes\u2019 to confirm a negative.\r\n
Indicate Required Fields<\/h3>\r\nIndicate required fields in plain text labels or question prompts. Don\u2019t rely on colour alone to indicate a required field.\r\n
Include Field Labels<\/h3>\r\nEvery field should have visible labels and example placeholder text in the fields. Add meaningful labels above or to the left of each field.\r\n
Number Questions<\/h3>\r\nNumber each question and add a progress indicator to help respondents to understand the survey\u2019s length.\r\n
Allow Saving Progress<\/h3>\r\nIf the platform allows, give respondents the option to pause, save, and resume the survey later.\r\n
Avoid Time Limits<\/h3>\r\nDo not impose a time limit on respondents unless essential to the purpose.\r\n\r\nIf a time limit is needed:\r\n
- \r\n \t
- Clearly communicate the time limit in the instructions.<\/li>\r\n \t
- Provide a warning before time runs out.<\/li>\r\n \t
- Offer a method to extend time at least once.<\/li>\r\n \t
- Make sure the timer is obvious and accessible without being intrusive.<\/li>\r\n<\/ol>\r\n
Avoid Space Constraints<\/h3>\r\nUse long text or rich text fields that allow respondents adequate space to answer. Ensure forms display properly on a mobile device. Pay attention to the layout of multiple-choice and radio buttons.\r\n
Error Messages<\/h3>\r\nIf respondents make mistakes or enter invalid data, show accessible error messages that specify the incorrect field and provide guidance on the required formatting. For example: \u201cDates should all be entered in the format mm\/dd\/yyyy, (as in 06\/29\/2023)\u201d or \u201cPasswords must contain at least 8 letters and\/or numbers.\u201d\r\n
Check Focus Order<\/h3>\r\nTest the keyboard functionality of your form to ensure the focus order follows the visual layout. Use Tab<\/strong> to move between fields, Space<\/strong> to open a menu and select checkboxes, and arrow keys to navigate menus and radio buttons.\r\n\r\nEnsure there is an obvious visual indicator when a form field has keyboard focus, such as a noticeable ring around the field.\r\n
Add Submission Confirmation Message<\/h3>\r\nAfter clicking the submit button, include a confirmation dialogue to prevent accidental incomplete submissions.","rendered":"
<\/p>\nOnline forms are useful for data collection and surveys. Accessible forms are designed to meet the access needs of all respondents. Accessible forms increase inclusivity, usability, and the number of people who can participate.<\/p>\n
There are different online tools available, but it’s essential to consider the content and structure of your form or survey to make it accessible.<\/p>\n
Here are some best practices to improve accessibility, usability, and effectiveness of online forms:<\/p>\n
Suggested Platforms<\/h2>\n
At Langara, we support Microsoft Forms<\/a>, Brightspace Surveys<\/a>, and Zoom polls<\/a>. These platforms offer various question types and features. Consider that Zoom polls must be set up before the meeting begins.<\/p>\n
Avoid SurveyMonkey and Wufoo as they present many accessibility barriers to users.<\/p>\n
Form Best Practices<\/h2>\n
Provide clear instructions<\/h3>\n
Start your form with clear instructions. Include information about:<\/p>\n
- \n
- Number of questions.<\/li>\n
- Time limit (if applicable).<\/li>\n
- Due date (if applicable).<\/li>\n
- How to complete the questions.<\/li>\n
- What the survey is about.<\/li>\n
- How required fields will be indicated\n
- \n
- o Plain text \u201crequired\u201d in the visible form label is the best method.<\/li>\n<\/ul>\n<\/li>\n
- Instructions for form fields that require specific formatting or other requirements.<\/li>\n
- Help or contact information.<\/li>\n<\/ul>\n
Clear instructions help respondents budget their time, manage their expectations, and understand the purpose of the survey.<\/p>\n
Use Plain Language<\/h3>\n
Use simple and direct language that everyone can understand. Avoid jargon, abbreviations, and acronyms or when you use them, explain them when they first appear. Avoid negative questions that might confuse respondents by requiring a \u2018Yes\u2019 to confirm a negative.<\/p>\n
Indicate Required Fields<\/h3>\n
Indicate required fields in plain text labels or question prompts. Don\u2019t rely on colour alone to indicate a required field.<\/p>\n
Include Field Labels<\/h3>\n
Every field should have visible labels and example placeholder text in the fields. Add meaningful labels above or to the left of each field.<\/p>\n
Number Questions<\/h3>\n
Number each question and add a progress indicator to help respondents to understand the survey\u2019s length.<\/p>\n
Allow Saving Progress<\/h3>\n
If the platform allows, give respondents the option to pause, save, and resume the survey later.<\/p>\n
Avoid Time Limits<\/h3>\n
Do not impose a time limit on respondents unless essential to the purpose.<\/p>\n
If a time limit is needed:<\/p>\n
- \n
- Clearly communicate the time limit in the instructions.<\/li>\n
- Provide a warning before time runs out.<\/li>\n
- Offer a method to extend time at least once.<\/li>\n
- Make sure the timer is obvious and accessible without being intrusive.<\/li>\n<\/ol>\n
Avoid Space Constraints<\/h3>\n
Use long text or rich text fields that allow respondents adequate space to answer. Ensure forms display properly on a mobile device. Pay attention to the layout of multiple-choice and radio buttons.<\/p>\n
Error Messages<\/h3>\n
If respondents make mistakes or enter invalid data, show accessible error messages that specify the incorrect field and provide guidance on the required formatting. For example: \u201cDates should all be entered in the format mm\/dd\/yyyy, (as in 06\/29\/2023)\u201d or \u201cPasswords must contain at least 8 letters and\/or numbers.\u201d<\/p>\n
Check Focus Order<\/h3>\n
Test the keyboard functionality of your form to ensure the focus order follows the visual layout. Use Tab<\/strong> to move between fields, Space<\/strong> to open a menu and select checkboxes, and arrow keys to navigate menus and radio buttons.<\/p>\n
Ensure there is an obvious visual indicator when a form field has keyboard focus, such as a noticeable ring around the field.<\/p>\n
Add Submission Confirmation Message<\/h3>\n
After clicking the submit button, include a confirmation dialogue to prevent accidental incomplete submissions.<\/p>\n","protected":false},"author":1655,"menu_order":13,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-4347","chapter","type-chapter","status-publish","hentry"],"part":62,"_links":{"self":[{"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/chapters\/4347","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/wp\/v2\/users\/1655"}],"version-history":[{"count":17,"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/chapters\/4347\/revisions"}],"predecessor-version":[{"id":9570,"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/chapters\/4347\/revisions\/9570"}],"part":[{"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/parts\/62"}],"metadata":[{"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/chapters\/4347\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/wp\/v2\/media?parent=4347"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/pressbooks\/v2\/chapter-type?post=4347"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/wp\/v2\/contributor?post=4347"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/accessibilityhandbook\/wp-json\/wp\/v2\/license?post=4347"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}