Accessibility
CrowdCreate should be usable by everyone — the people who run a fund and the people who give to it. This page is an honest account of what we do toward that, and where we know we still have work.
What we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We say "aim to meet" rather than "fully conform" deliberately: we have not commissioned a formal third-party audit, so we won't claim a certification we don't hold.
What we do on every release
- Automated accessibility checks (axe-core, against WCAG 2.0/2.1 A and AA rules) run across our key pages before each deploy, and we hold the line at zero serious or critical violations.
- Semantic HTML and landmarks, so screen readers and keyboard users can navigate by structure rather than guesswork.
- Keyboard operability for interactive elements, including the donation widget's controls.
- Visible focus, labelled form fields, and color contrast that aims to meet the AA thresholds.
- Reduced-motion preferences are respected — we don't force animation on anyone who's asked their device to limit it.
Where we know there are limits
Automated testing catches a lot, but not everything — some barriers only surface with real assistive technology and real people, and we haven't finished that deeper testing across every page. Some steps also involve third parties we don't control: card entry happens on Stripe's hosted checkout, so its accessibility is Stripe's to maintain, not ours. If you hit a wall anywhere in that flow, please still tell us — we want to know.
Hit a barrier? Tell us.
If anything on CrowdCreate is hard or impossible to use with the tools you rely on, email us and describe what happened. We read these, we'll reply, and we'll do our best to fix it or find you a way through in the meantime.
Email hello@crowdcreate.appLast reviewed May 29, 2026. Related: Trust & Safety.