Accessibility statement
We build public-facing software for a living, so we have to get accessibility right. This page covers the standard we hold ourselves to and how to tell us when we have missed it.
The standard we build to
We aim to meet WCAG 2.1 Level AA on this site and on the products we build for clients. For public-sector work, we also build to Section 508 expectations.
What that means in practice
- Semantic markup that works with screen readers and keyboard navigation.
- Visible focus styles so you can always see where you are.
- Text and interface colors chosen to meet contrast minimums.
- Form fields with clear labels and plain-language error messages.
- Respect for reduced-motion preferences set in your browser or system.
Ongoing work
We test as we build and fix issues as we find them. If you use assistive technology and hit a barrier on this site, we treat that as a bug, and we want to hear about it.
Tell us about a barrier
Email accessibility@avenuecivic.com with the page and a short note on what went wrong, and we will work to fix it. If you need information from this site in another format, ask and we will provide it.
On the products we deliver
When we build for an agency, accessibility conformance ships as part of the work, and we can provide a conformance report (such as a VPAT) on request.