Accessibility in the OpenGov Cloud

In everything we do, our goal is simple: Building the best products possible for our customers. That’s why providing an inclusive user experience is a “need to have,” not a “nice to have.” By incorporating best practices for vision, hearing, and motor-impaired audiences, we can ensure the OpenGov Cloud is accessible to a wide range of users.

Our Accessibility Best Practices

Vision: Easy to Read

For people with color blindness or sensitivity to bright colors, OpenGov’s design ensures that the interface is bold, simple, and anchored on a color palette that meets contrast ratio guidelines in acordance with Web Content Accessibility Guidelines (WCAG) AA standards.

Hearing: Easy to Absorb

We ensure design and content in the OpenGov Cloud are concise and translatable by a screen reader. Additionally, responsive sizing and clear headings ensure screen readers can accurately assist users with low vision. And we’re not done yet. We are currently building a library of captions and transcriptions for video content.

Mobility: Easy to Access

Our engineers and product designers ensure users can navigate through the software with their keyboards, efficiently steering to the elements they’d like to select. The surface area of each interactive element is designed to be large enough to tap.

Cognitive: Easy to Understand

Look familiar? We hope so! Design patterns are repeated so users can easily recognize similar workflows across applications. We partner with our local government customers to confirm online forms and webpages are simplified to reduce cognitive load.

Statement of Conformance

OpenGov is committed to making accessible products and enabling our customers to comply with accessibility laws. We recognize it is not possible to satisfy all criteria for each type of content. To provide the highest level of access to people of varying abilities, we have implemented the following internal standards:

  • Develop and maintain OpenGov software in accordance with WCAG 2.1 Level AA Standards, in addition to the requirements of Section 508.
  • Conduct regularly scheduled conformance assessments.
  • Address identified conformance gaps by establishing an accessibility remediation roadmap and executing against it.
  • Provide ongoing training for design and development on current accessibility standards and conformance.
  • Accessibility assessments are built into our pre-release testing process.
  • An accessible front-end library is available as a tool for developers to promote conformance.
  • Regularly promote the importance and value of accessibility internally by way of our in-house accessibility experts.

Want to Learn More
About Accessibility at OpenGov?