Disability accomodations request (filter GitHub search results of repos by number of lines of code in the repo)

[JohnReedLOL]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Repositories

Body

Today, May 15th, is Global Accessibility Awareness Day (GAAD). A year ago today, GitHub signed the Global Accessibility Awareness Day (GAAD) Pledge, promising to empower people with disabilities to contribute to open source. It was described on the GitHub blog on May 15, 2025. I read it and responded by opening this issue:

https://github.com/orgs/community/discussions/159406

I have a disability that blocks my ability to contribute to open source and I opened that issue in hopes that the accessibility issue would be resolved. A year has passed and it has not been resolved. I am opening this issue as a sort of reminder or nudge to GitHub.

• John

p.s. This feature request doesn't necessarily just help me. For example, a Project Manager (PM) could filter some repos by the number of lines of code to judge scope.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[samus-aran]

Hi @JohnReedLOL Thanks for continuing to share your feedback with us! While we can’t provide a timeline or guarantee if or when new features may be scheduled, all feedback shared in existing discussions is recorded and reviewed by the our internal teams.

To help keep everything centralised and easier to track, there’s no need to create additional discussions (original discussion) for the same request. Continuing the conversation in the existing discussion is the best way to add context and signal ongoing interest. ✨

Hello @JohnReedLOL — we’re closing this issue as a duplicate of your original post to help prevent confusion for anyone following or commenting in this thread. Thanks for your understanding!