Accessibility Best Practices Guide for Open Source Projects #194508
Replies: 3 comments
-
|
Yo @mlama007 — this is exactly what OSS needs. |
Beta Was this translation helpful? Give feedback.
This comment was marked as low quality.
This comment was marked as low quality.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
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:
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:
Every fix opens the door for someone who couldn't use your project before. That's a win worth celebrating. 🎉
Beta Was this translation helpful? Give feedback.
All reactions