Our Accessibility Commitment

The commitment

Campaign websites exist to reach every voter — including the roughly one in four American adults living with a disability. A campaign site that can't be read by a screen reader, navigated by keyboard, or seen by someone with low vision isn't just failing a standard; it's leaving voters out of the conversation. Electbase was built on the position that no campaign should have to choose between looking good and being usable by everyone — and that the platform, not the campaign, should carry the burden of getting this right.

This commitment is personal to us: our founder chaired the board of Disability Rights Arizona, and building for disabled voters is part of why Electbase exists — not a requirement we discovered later.

The standard we comply with

Electbase conforms to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA — the current W3C standard — across both this website and the campaign websites our platform publishes. That covers the full range of the guidelines: content that's perceivable (text alternatives, contrast, reflow), operable (keyboard access, visible focus, no keyboard traps, adequate target sizes), understandable (consistent navigation, labeled forms, clear errors), and robust (valid semantics that assistive technologies can rely on).

How we comply

Three layers, each of which has to pass before anything reaches a voter:

1. Accessible by construction. Every design block in the Electbase library — heroes, issue grids, donate bands, event lists, signup forms — is built accessible before any campaign touches it: semantic HTML landmarks and labeled navigation, keyboard operability with visible focus indicators on every surface, correctly associated form labels with accessible error messaging, text alternatives on images and media, reduced-motion support, and color tokens engineered to meet AA contrast. Interactive widgets (tabs, accordions, menus) use native elements or complete ARIA patterns.

2. Machine-checked at every publish. Every campaign site must pass an automated WCAG 2.2 AA check before it can go live — heading structure, landmarks and skip links, image descriptions, form labels, link names, and color contrast, including the brand colors a campaign picks itself. A page that fails the check cannot publish. The editor explains each issue in plain language and suggests a fix — for example, the nearest readable shade of your campaign color.

3. Continuously tested. The same accessibility checks run in our engineering pipeline on every change to the block library and to this website — hundreds of rendered pages are validated on every code change, so a regression is caught before it ships, not after a voter hits it.

What automation can't do — and what we do instead

We're honest about the limits. Automated checks can't judge whether an image description is accurate, and third-party services campaigns embed — donation processors, video hosts — control their own accessibility. We review those boundaries by hand, choose integration partners with accessibility in mind, run screen-reader checks as part of our release process, and treat every report from a real user as a defect to fix.

Questions, concerns, or barriers

If you have questions about our accessibility practices, concerns about compliance, or you've hit a barrier on electbase.com or on a site published by an Electbase campaign, we want to hear from you — and we'll prioritize the fix.

Email us at hello@electbase.com or use our contact form. If you're reporting a barrier, it helps to include what happened, the page you were on, and the assistive technology you were using (if any). A real person reads every message.

Scope