This is an unpublished draft preview that might include content that is not yet approved. The published website is at w3.org/WAI/.

SC 1.3.5 Identify Input Purpose in WCAG 2 Videos

Background

Notes

Script

Scene Time Audio Visual
1 0:00 - 0:@@ Preety has dyslexia and dyscalculia, which makes it difficult for her to type things like a phone number, email address, username, and passwords. We see Preety using a tablet computer at her desk at home (see SC-1.3.2).
2 0:@@ - @:@@ For example, she previously had difficulty logging into the online learning platform of her school. It is not a memory issue, she just confused the numbers and letters when she was typing her username and password because they are not real words. We see a form asking for “Username” and “Password”, and she seems to have trouble typing in the username (possibly a long student ID number).
3 @:@@ - @:@@ Preety now uses a browser that allows her to store information that she types into input fields, and provide her an option to automatically complete the input fields when the information is requested again. We see the form, with the browser showing different usernames (email addresses) that Pretty can select from to auto-complete the input field (these email addresses are collected from previous entries on this website).
4 @:@@ - @:@@ Fortunately the websites and applications of her school use the correct code to identify the purpose of input fields, so that they can be stored and automatically completed when Preety wants. We see the form, then the underlying code is shown illustratively (not intended to be actually read), and the relevant attributes in the code highlighted (also illustratively).
5 @:@@ - @:@@ Preety loves this feature because it saves her a lot of time and effort having to re-type the information each time it is requested. It also works on other websites that use correct coding of input fields. We see Preety using the auto-complete for username (and maybe also password) on a different log-in page (for another website).
Back to Top

This is an unpublished draft preview that might include content that is not yet approved. The published website is at w3.org/WAI/.