{"id":291,"date":"2019-06-04T15:46:58","date_gmt":"2019-06-04T19:46:58","guid":{"rendered":"https:\/\/pressbooks.library.ryerson.ca\/iwacc\/?post_type=chapter&p=291"},"modified":"2019-07-31T15:41:47","modified_gmt":"2019-07-31T19:41:47","slug":"3-3-input-assistance-level-a","status":"publish","type":"chapter","link":"https:\/\/pressbooks.library.torontomu.ca\/iwacc\/chapter\/3-3-input-assistance-level-a\/","title":{"raw":"3.3 Input Assistance (Level A)","rendered":"3.3 Input Assistance (Level A)"},"content":{"raw":"
\r\n

Guideline 3.3<\/strong> Input Assistance<\/h2>\r\nHelp users avoid and correct mistakes.\r\n\r\n<\/div>\r\nWhat is \u201cinput assistance?\u201d How does it support understandability?<\/strong>\r\n\r\n\u201cInput assistance\u201d is WCAG 2.1 jargon for techniques that help people avoid mistakes, especially when filling out forms. When people do make mistakes, it refers to the techniques that help them recover from errors.\r\n
\r\n\r\nDefinition<\/strong>\r\n\r\nInput assistance:<\/strong> Techniques that encourage users to understand the process<\/i> of entering information. These techniques include providing clear instructions, a chance to check work before submitting it, and context-sensitive help.\r\n\r\n<\/div>\r\nEveryone makes mistakes, but some people with disabilities may be more prone to input errors than people without disabilities. For example, someone with a tremor may press keys by accident. An individual who is blind may have trouble determining which fields are mandatory and which are optional. A person who relies on speech recognition software may produce words that are different than the dictated words.\r\n\r\nThis guideline seeks to reduce the number of serious errors that users make, increase the likelihood that users will notice their errors, and help users understand what they must do to correct errors.\r\n
\r\n

<\/a>Success Criterion 3.3.1<\/strong> Error Identification<\/h3>\r\nLevel A\r\n\r\nIf an input error<\/a> is automatically detected, the item that is in error is identified and the error is described to the user in text.\r\n\r\n<\/div>\r\n

Error Identification Explained<\/h4>\r\nWhen designing a website or online form, use text to indicate and describe errors.\r\n\r\nIt is okay to signal errors with images and colour changes provided there are also text descriptions.\r\n\r\nExample:<\/strong> A bank encourages customers to apply for loans online. A customer submits a form with his or her name, address, phone number, email address, and account number. If the customer does not complete the form correctly, the form is re-displayed with an alert \u2014 three question marks ???<\/strong> displayed after the prompt \u2014 for all missing or incorrect fields.\r\n\r\nIn addition, the fields in error are highlighted yellow to make them easier to spot.\r\n\r\nSC 3.3.1<\/strong> is a special benefit to screen reader users. Since screen readers only read text, screen reader users may have trouble understanding non-text error messages.\r\n
\r\n\r\nSuggested Reading:<\/strong>\r\n