Contribute to the toolkit

You don’t need to write code to help shape this work. The toolkit is for people whose access needs are different or change over time, and most of them have never opened GitHub. What we most need to hear is what you notice when you try it, and what trips you up in the technology you use every day.

Ways to take part without code

Tell us about a problem. Is something in an app, a website or a device getting in your way? Tell us about it. Builders at our workshops start from the problems people bring them, so yours could be the next thing someone works on. You don’t need to know anything about code. Tell us through our contact form.

Try it, and tell us how it went. If you’ve used one of the browser extensions built on the toolkit, we want to know what worked, what didn’t, and what you wished it could do. Your feedback goes straight to the people building it. Tell us through our contact form. There’s also an install guide that doesn’t assume any coding.

Test what other people build. At our workshops, some people’s whole role is to try projects out alongside the people they’re meant for, then tell the builders honestly whether they help. (Our events page lists the workshops.)

Share a combination that works for you. Maybe a page only becomes usable when the text is bigger, the motion is turned down and the pop-ups are gone. A combination like that can become a skill, a short recipe that anyone else can use, and writing one doesn’t take any code. Send us the idea through our contact form, and someone can write it up.

Help with the writing. Spotted something confusing, a typo, or a gap in our documentation? Letting us know helps more than you might think.

Show us what you’ve made. If you’ve built something with the toolkit, with or without code, we’d love to see it. Take a look at the gallery.

How we work with you

  • People with disabilities are involved in design and evaluation from the start, not brought in at the end.
  • We’re careful with your information. We only use your details for what you agreed to, and you can ask us to remove them whenever you like.
  • Feedback reaches us privately through a form rather than as public comments, so you can be as frank as you want.
  • Everyone follows our code of conduct.

If GitHub is a barrier

You never need GitHub to take part. Tell us through our contact form, or email ai4a11y-collective-contact@googlegroups.com, and say how you’d like us to reply.

Contribute code

If you write code, here are the main ways to contribute to the toolkit.

What you can contribute

  • A skill. A markdown file that turns on a few existing adapters for a specific need. For example, calm-browsing turns on motion-reducer, dark-mode and focus-mode. You don’t need to write any code.
  • An adapter or an auditor. An adapter is code that makes one change to a page, e.g., a reading ruler that follows your cursor. An auditor is code that finds accessibility problems that standard checkers like axe-core don’t catch.
  • An app built on the toolkit. Build an app with the toolkit in your own repository, on any platform, and tell us about it in an issue.
  • Work on the benchmarks. Help define how to check whether an adaptation improved accessibility for the person it was meant for.

Before you start

  1. Read the contributor guide on the toolkit’s GitHub page. It covers setting up, the ways to contribute and how to open a pull request. Step-by-step instructions for adding a skill, adapter, auditor or profile are in docs/adding-to-the-catalog.md in the repository.
  2. Look at what’s already there. Browse tools/adapters/ and toolkit/skills/builtin/ in the repository first.
  3. Involve the people it’s for. People with disabilities must be part of design and evaluation, and paid for their time.

Opening a pull request

Open a pull request on GitHub. Our template asks what the pull request does, which parts of the toolkit it changes, who it helps and how you tested it.