Accessibility statement

Accessibility of this site

If anything on this site does not work for you, please tell us through our contact form, or email ai4a11y-collective-contact@googlegroups.com, and let us know how you’d like us to reply.

What guides the toolkit

A few commitments shape how we build the toolkit, and we try to hold ourselves to them.

Nothing about us without us. People with disabilities help shape, build and evaluate this work from the beginning.

We start from what you ask for, not from a diagnosis. If you want larger text or plainer language, the toolkit adapts to that. You never have to name a condition or tell us you’re disabled.

Your profile is yours. You can look at it, correct it, and decide app by app who gets to read it. Nothing is shared unless you say so, and you can change your mind at any time.

It suggests rather than imposes. When the toolkit thinks a change might help, it asks first. Nothing changes behind your back.

It’s private by default. Your profile stays on your device unless you choose otherwise. Out of the box, the toolkit doesn’t remember anything from banking, health or government pages.

Apps take only what they need. An app can use a single part of the toolkit, or all of it.

We build on what already works. Where good open tools exist, we use them instead of reinventing them.

Underneath all of this is a simple idea. Most interfaces are designed for one imagined “average” user, and everyone else is expected to cope. We think the problem lies in that design, not in the people using it.

What the toolkit isn’t

  • An overlay. Overlays are widgets a site owner installs for every visitor, often to tick a compliance box. With the toolkit, you’re the one who decides what changes.
  • A replacement for assistive technology. It won’t stand in for your screen reader, magnifier or anything else you rely on. It’s built to work alongside them.
  • Finished. This is early research. We haven’t yet formally tested its adaptations with the communities they’re meant to serve.
  • A free pass for developers. Building with the toolkit doesn’t let anyone off the hook for making things accessible in the first place.

Risks we’re aware of

We’d rather be upfront about what could go wrong. Here’s what we know about so far, and what we’re doing about it.

  • It could seem to work better than it does. We’re open about where the toolkit does well and where it falls short, and we’re working on ways to measure whether an adaptation actually helped.
  • A few changes can’t be undone one by one. The browser extension lists what it changed and lets you undo each change, and turning an adapter off undoes its changes. Three kinds of fix to a page’s structure can’t be undone that way: reordering its headings, replacing outdated page elements, and fixing buttons placed inside other buttons.
  • It could guess wrong about what you need. AI models tend to work best for typical users and worst for people whose needs are less common, who are exactly the people this work is for. That’s why the toolkit suggests changes instead of applying them, and learns when you correct it.
  • The cost could end up falling on disabled people. Making things accessible is the job of the people who build them, not the people who use them. It’s one of the things we would like to look into if this work continues.
  • Developers could lean on it instead of thinking about accessibility. Anywhere developers are likely to read about the toolkit, we say clearly that it’s no substitute for building accessibly from the start.
  • Research with your data carries a privacy risk. We won’t use your data for research without first telling you exactly how and getting your consent.