Inaccessible registration systems

Why is this a problem?

Many standard development organizations’ application processes are not accessible, which makes it harder for people to participate. Some common examples include:

• Not having alternative registration options, such as phone, email, or paper sign-up
• Websites or application portals that don’t work with screen readers or other assistive technology
• Having no way to request accommodations during registration, or having a request option that is difficult to find
• CAPTCHAs that are hard or impossible to use with screen readers
• Time limits that log people out before they finish the form
• Forms that are long, complicated, and not written in plain language
• Forms that aren’t keyboard accessible and can’t be completed without a mouse
• Required fields that don’t make sense or force people to share personal information
• Mobile-unfriendly forms that are a barrier for people who rely on phones or tablets
• Requiring a specific file format for documents that need to be uploaded
• Not having a save-and-return option, which people who need more time or breaks require
• Error messages that are unclear, aren’t read by screen readers, or don’t explain how to fix the problem
• Language barriers, including not having a translation option or using overly technical wording
• Confirmation emails that don’t arrive or are inaccessible, for example, they have images instead of text or unclear next steps

Ways to address the barrier