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
Be transparent in the application process
Quick Actions
- Publish clear selection criteria for technical committee members that reflect inclusion and diversity goals.
- Provide role descriptions that outline:
- Time commitments
- Tasks and responsibilities
- Compensation or volunteer expectations
- Provide information on accessibility supports including:
- What accommodations are available by default (e.g., captioning, large print, flexible schedules)
- What can be provided by request (e.g., sign language interpretation)
- How to request support, and who to contact
- Communicate regularly with applicants about their status and timelines.
- Offer alternative ways to participate such as public comment periods to those not selected.
Barriers these actions address
- Inaccessible registration systems
- Lack of clear and accessible onboarding process
- Lack of organizational support
- Unclear participation information
Check and improve accessibility
Long-term Actions
- Create a permanent dedicated accessibility group within the organization to track inclusion over time.
- Celebrate improvements in accessibility and inclusion to show the group’s progress.
- Regularly assess the inclusiveness and accessibility of meetings and processes through feedback
- Consider accessibility across formats, devices, and languages.
- Design digital content so people with disabilities can access, understand, and use it.
- Conduct accessibility audits with usability and assistive technology experts to ensure all digital platforms including websites, member portals, application sites and feedback mechanisms are accessible.
- Offer alternative ways to participate: in-person, phone, relay services, video calls, or paper applications.
- Proactively consult with D/deaf and D/disabled committee members to determine specific access needs
- Provide accommodations to participants, including:
- Sign Language interpreters (ASL, LSQ, etc.)
- Real-time captioning (CART)
- Note-taking services
- Clear and consistent turn-taking protocols
- Accessible digital files and materials in advance
- Ensure physical spaces (if used) are accessible for mobility devices, sensory needs, and rest requirements. (Physical Space)
Barriers these actions address
- Inaccessible registration systems
- Inaccessible digital documents
- Inaccessible feedback mechanisms
- Inaccessible virtual meetings
- Recruiting for diversity
Ensure all documents are accessible
Quick Actions
- Use plain language and avoid technical jargon when possible.
- Include infographics, diagrams, and visual explanations to break down complex concepts. Ensure that all visual items include textual descriptions and alt text where appropriate.
- Use real-world examples to ground abstract ideas.
- Maintain a living glossary of technical terms and acronyms
- Include a summary page at the beginning of each document outlining its purpose, key content, and its relevance to other work
- Ensure all documents including drafts, meeting notes and final publications are accessible from the start, and throughout the collaboration process not just at the end of the process
- Publish standards in accessible formats like properly structured Word documents and tagged PDF documents
Long-term Actions
- Train chairs and committee members in accessible document creation practices
Barriers these actions address
- Inaccessible digital documents
- Inaccessible digital collaboration tools
- Inaccessible registration systems
- Too much background information for new members
- Underestimated workloads
- People don’t start at the same place
Ensure websites are accessible
Quick Actions
- 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.
Barriers these actions address
- Inaccessible registration systems
- Inaccessible feedback mechanisms
- Inaccessible digital collaboration tools