While up to version 1.0.0 ally.js has been developed primarily by only one person, the intention is to get more people aboard. If there is anything about ally.js you'd like to improve, open an issue so we can discuss how you might approach that goal. We've created some docs and rules to give contributors some guidance. Don't worry if you don't understand every single piece of our fuzzy puzzle, we'll help you in any way we can.
ally.js strives to be a general purpose helper library for accessibility concerns. As such, contributions should be applicable to virtually any project and refrain from being overly specific. GOALS.md describes the possible future of the project. If you have any expertise or experience to share for those topics, please open an issue to discuss.
ally.js is not only about the library code. All the concepts covered by ally.js need to be explained in such a way that people new to accessibility understand what is going on. To make that happen, you can help improve our documentation or write a tutorial.
# Who can contribute?
Anyone can join. Everything is done on github in the open. Everything is up for discussion.
Issues tagged with good first contribution have been analyzed and explained. They should provide all details required for your first contribution to ally.js. Feel free to pick one, work on it and send a pull request. If you have questions, please post them to the issue and we'll get back to you.
./testor issues tagged with improve.
./docsor issues tagged with website or documentation.
- You specialize in the build pipeline? Issues tagged with build might be your thing.
- You specialize in a framework or library and would like to integrate ally.js? See the issues tagged with integration or open a new issue to discuss your approach.
# Documentation for contributors
While the project and most of its resources were created by Rodney Rehm, the following people had substantial impact on ally.js: