Accessible Forms

Here are 5 things accessible forms need:  #

• Required fields, fields with special formatting, or other unique parts of the form have clear instructions. 
• Clear navigation order using just the Tab key to go through the form. 
• The entire form can be completed using only a keyboard. 
• One accessible label is associated with each input and is readable by screen readers. 
• Usable and accessible form validation for form errors (the messages you get if a field is incorrect). 

Source: A beginner’s complete guide to form accessibility: the 5 things accessible forms needs and how to fix common errors

Three success criteria are especially important here: 

1. Under WCAG SC 1.3.1, “Info and Relationships,” labels must also have correct markup to identify them programmatically.  
2. WCAG 2.1 SC 4.1.2, “Name, Role, Value” requires that names and roles can be programmatically determined. 
3. WCAG 2.1 Success Criterion 3.3.2, “Labels or Instructions,” requires websites to provide labels or instructions when content requires user input.  

Accessible Authentication #

1. Do not block permission to copy/paste 
2. Do not force user who is using the Web to log in to get password support (reset) from a mobile device 
3. Do  not use a combo of letters/numbers for passcode 
4. Do not force users to memorize passcode 
5. PayPal has a AAA example that is recommended. 

One of the ways apps use to confirm the identity of users is two-step verification. Captchas are another. Both have presented issues for persons with disabilities, especially on mobile devices. 

Captchas with photos – these fail accessibility because they are visual tests that blind or sight impaired people can’t use. An alternative is required. 

Email passcode – This process is very difficult for people with various disabilities, including blindness or sight impaired and those with cognitive related issues. They are asked to remember a series of numbers that come in off-site and must remember that number to be able to type it in when they return to the mobile app. Many need to write it down first. Many people can’t manage several tabs open on a mobile device.  

Make the code a link.
 
3.3.7 Accessible Authentication (A) 

1. Do not block permission to copy/paste 
2. Do not force user who is using the Web to log in to get password support (reset) from a mobile device 
3. Do  not use a combo of letters/numbers for passcode 
4. Do not force users to memorize passcode 
5. PayPal has a AAA example that is recommended. 

One of the ways apps use to confirm the identity of users is two-step verification. Captchas are another. Both have presented issues for persons with disabilities, especially on mobile devices. 

Captchas with photos – these fail accessibility because they are visual tests that blind or sight impaired people can’t use. An alternative is required. 

Email passcode – This process is very difficult for people with various disabilities, including blindness or sight impaired and those with cognitive related issues. They are asked to remember a series of numbers that come in off-site and must remember that number to be able to type it in when they return to the mobile app. Many need to write it down first. Many people can’t manage several tabs open on a mobile device.  

https://www.w3.org/WAI/WCAG22/Understanding/accessible-authentication