Our commitment
We are committed to providing an accessible and inclusive experience for all people, including people with disabilities. Our goal is conformance with WCAG 2.2 Level AA across ballotscope.com and public experiences we manage. We design, build, and test with accessibility in mind and invite feedback to keep improving.
Scope
- ballotscope.com and core features such as report cards, alignment quiz, Campaign Central, Explore Leaders, and Developers & Docs
- public content we host or embed (for example, videos or downloadable documents)
- community spaces we manage or moderate that are linked from our site
Third-party platforms we do not control, such as Reddit and GitHub Discussions, maintain their own accessibility policies. Where possible, we configure and use those platforms in accessible ways and provide alternatives when needed.
Standards and conformance target
- Target standard: WCAG 2.2 Level AA
- Technologies: HTML, CSS, JavaScript, ARIA (used only where necessary)
- Status: we are working toward full conformance and remediate issues on an ongoing schedule
Assistive technologies and environments we test with
- Screen readers: NVDA (Windows/Firefox), JAWS (Windows/Chrome), VoiceOver (macOS/Safari), TalkBack (Android/Chrome)
- Browsers: current stable Chrome, Firefox, Safari, Edge
- Inputs: keyboard-only, touch, and switch access where feasible
How we build for accessibility
- Semantic HTML with proper landmarks and headings
- Descriptive labels, instructions, and names for controls and links
- Meaningful alternative text for non-decorative images and icons
- ARIA used sparingly to enhance, not replace, semantic markup
- Clear focus management in dynamic interfaces and dialogs
- Respect for user preferences such as reduced motion
Keyboard support
- Logical, predictable focus order
- Visible focus indicators on interactive elements
- Skip to content link on all pages
- No keyboard traps; dialogs and menus are reachable and dismissible via keyboard
Color, contrast, and typography
- Text and interactive element contrast meets or exceeds WCAG 2.2 AA
- Content remains functional when text is resized up to 200 percent
- We avoid using color alone to convey meaning and provide textual or programmatic alternatives
- Dark mode support where applicable
Media and alternatives
- Captions for videos we publish
- Transcripts for audio and livestreams where feasible
- Autoplay is avoided for media with sound
Forms and validation
- Each input has a programmatically associated label and accessible name
- Required fields and errors are announced to assistive technologies
- Errors are described specifically with guidance to resolve them
- Status messages use appropriate ARIA roles when needed
Mobile and responsiveness
- Touch targets sized appropriately
- Orientation changes supported
- Gesture actions have keyboard or on-screen alternatives
Documents and downloads
- New PDFs and office documents follow accessibility best practices (tags, reading order, headings, alt text)
- When a document cannot be made fully accessible, we provide an alternate accessible format on request
Known issues and remediation
We continually audit and improve the site. If there are known issues, we list them here with target fix dates, and we prioritize fixes that block access to key tasks.
Feedback, requests, and accommodations
If you encounter a barrier or need content in an alternative format, contact us at accessibility@ballotscope.com or use the Help Center form. Include the page URL, a brief description of the issue, and any assistive technologies you use. We aim to respond within 5 business days. For time-sensitive accommodations (for example, event access), please note the deadline.
Compliance documents
If you require a VPAT or Accessibility Conformance Report, email accessibility@ballotscope.com and we will provide the most recent version or timeline for availability.
Accessibility on social platforms
For social content we produce or moderate: