Open source powers the software we all rely on - but if it isn't accessible, we're leaving people out.

I'm excited to share a new Accessibility Best Practices Guide for Open Source Projects that gives maintainers practical, actionable steps to make their projects usable by everyone.

Inside the guide:

• How to write an accessibility statement and ACCESSIBILITY.md - ACCESSIBILITY.md example
• Making docs accessible by default (headings, alt text, captions)
• Designing accessible interfaces (keyboard support, semantics, color & contrast)
• Building accessibility into PR checklists, issue templates, and CI - - accessibility issue template example and PR template example
• Leveraging GitHub Copilot for accessibility tasks
• Continuous testing — automated and manual

The core message: "Nothing about us without us." The most impactful thing you can do is partner with people with disabilities - early and often.

You don't have to do everything at once. Start small this week:

1. Add an ACCESSIBILITY.md - ACCESSIBILITY.md example
2. Make sure every interactive element is keyboard reachable
3. Fix missing form labels
4. Add alt text to your README5.

Every fix opens the door for someone who couldn't use your project before. That's a win worth celebrating. 🎉