Test websites on multiple browsers and devices, including mobile phones and tablets.
Offer help or support for users who encounter accessibility barriers.
Long-term Actions
Involve people who use assistive technologies like screen readers, switch devices, or captioning tools in the testing and feedback processes.
Test for keyboard-only access across all steps including registration, login, confirmation and uploading documents. If someone can’t complete the process without a mouse, it’s not accessible.
Use plain and simple language
Ensure all images have descriptive alt text for people who use screen readers.
Use high-contrast colors for text and backgrounds
Avoid relying on color alone to convey information.
Make forms accessible, with clear labels, instructions, and error messages that screen readers can detect.
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
Most feedback systems use digital tools that not everyone can use. Some online forms do not work with screen readers or other assistive technology. Requiring people to email a committee chair instead of using the standard feedback channels can deter people from providing feedback.
Ways to address the barrier
Allow anonymous feedback opportunities
Check and improve accessibility
Ensure websites are accessible
Establish continuous feedback loops
Measure the developed standard's impact with affected communities
Some digital tools used for meetings and teamwork are not accessible to everyone. When tools are hard to use or not available to all, some people are left out and cannot fully take part.
Common problems include:
Tools that don’t work with screen readers or other assistive technologies
Buttons or features that are hard to use with a keyboard
Missing or limited captions, screen reader support, keyboard navigation, high-contrast modes, and sign language/interpretation support.
Security settings that block accessibility features