Fund open-source language and accessibility infrastructure
The initiative is independent and currently self-funded. Funding would sustain shipped tools and pay for expertise that open-source projects should not expect people to donate.
What funding supports
Maintained tools
Issue triage, releases, security response, dependency updates, and adoption support for i18n-security-lint and readme-ci.
Paid lived-experience review
Accessibility findings reviewed by people who use screen readers and other assistive technology in daily life.
Indic-language review
Native-language review for Hindi and other Indic locales instead of accepting contributions on trust.
Public evidence
Field studies, transparent corpora, reproducible methods, and publication of results and limitations.
Secure infrastructure
Continuous integration and sandboxed-execution compute for public developer tooling.
Current milestones
-
Now
Adoption over new surface area
Demonstrate the two shipped tools against live projects, improve them from user reports, and make installation and failure output easier to act on.
-
Next
Accessibility signals, validated
Build and validate machine-readable accessibility metadata, then score a second pull-request cohort to test whether the first study's pattern holds.
-
Next
AI contribution policy 0.2
Expand the verified catalogue and revise the schema through direct project and foundation feedback.
What a funding conversation includes
Detailed proposals are available with scoped milestones, budget assumptions, reporting cadence, evidence outputs, and the maintenance work that continues after a release. Figures are supplied with their programme scope rather than presented as one unsupported initiative-wide number.