Skip to main content

PublicInput Accessibility Statement

Jay Dawkins avatar
Written by Jay Dawkins
Updated over 2 months ago

At PublicInput, we believe everyone deserves an equal opportunity to engage with their government. Our platform is built and maintained with accessibility at its core.


1. Standards & Compliance

  • We aim to meet WCAG 2.1 Level AA guidelines across our web and mobile applications.

  • We continually test with automated tools and manual audits, including screen readers and keyboard‑only navigation.

2. Accessibility Features

  • Keyboard navigation: All interactive elements (menus, forms, maps) are operable via keyboard alone.

  • Screen‑reader support: Proper ARIA roles, labels, and landmarks ensure meaningful reading order.

  • Contrast & typography: Text and interface components meet or exceed 4.5:1 color‑contrast ratios; fonts scale up to 200% without loss of function.

  • Captions & transcripts: All video and audio content includes captions and text transcripts.

  • Form labels & instructions: Survey questions, map tools, and comment forms include clear labels, error identification, and instructions.

3. Ongoing Testing & Improvement

  • We run quarterly accessibility audits (external specialists plus in‑house QA).

  • We incorporate accessibility into every sprint, from design mock‑ups through development and release.

  • We track and resolve issues via our public issue log; critical fixes are prioritized immediately.

4. Known Issues

  • Some third‑party map overlays may not fully expose all controls to screen readers. Our default formats are built provide alternative forms of engagement alongside every map question format.

  • In rare cases, dynamic data visualizations may require manual refresh for assistive technologies; a “Refresh View” button is available.

5. Feedback & Contact

Your feedback drives our improvements. If you encounter an accessibility barrier, please let us know:

We commit to respond within 2 business days and to keep you updated on our remediation plan.

Did this answer your question?