Accessibility

Built to be used by everyone who serves the public.

Government software has to work for every member of staff and every resident — including people who navigate by keyboard, use a screen reader, need larger text, or rely on high contrast. Accessibility is a design requirement for Civic Mesa, not an afterthought, and we're committed to keeping it that way as the platform grows.

Our commitment

Working toward WCAG 2.1 Level AA.

We are committed to meeting the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA — the standard most US governments hold their vendors to, and the benchmark behind Section 508. We treat accessibility as ongoing work: we build to these guidelines, test against them, and fix issues as we find them.

Keyboard first

Every workflow is designed to be operable without a mouse — logical tab order, visible focus, and no keyboard traps.

Screen-reader friendly

Semantic markup, labelled controls, and meaningful alt text so assistive technology can announce what's on screen.

Readable by default

Color contrast aimed at AA thresholds, text that scales and reflows on zoom, and layouts that adapt from desktop to phone.

For residents

The public front door, open to all.

The resident portal is where the widest range of people meet your government online. It's built to be simple and accessible: report a concern with no account, in plain language, and check status by tracking code — on any device, with or without assistive technology.

  • No account, no barrier. Residents file a report without creating a login — fewer steps, fewer obstacles.
  • Plain language. Clear labels and instructions, not bureaucratic jargon.
  • Works on any phone. Installs to the home screen and reflows to small screens and large text.
Designed against WCAG 2.1 AA
Perceivablecontrast, text scaling, alt text
Operablefull keyboard, visible focus
Understandableplain language, clear errors
Robustsemantic, assistive-tech ready
Procurement & Section 508

Documentation for your accessibility review.

If your procurement process requires accessibility documentation — a VPAT (Voluntary Product Accessibility Template), an ACR, or answers to a 508 checklist — contact us and we'll work with your team. We'd rather have an honest conversation about where we conform today and where we're still improving than hand you a rubber stamp.

Request accessibility docs

Email hello@civicmesa.com and tell us what your procurement team needs. We'll respond with our current accessibility statement and supporting detail.

Report a barrier

If you hit something that doesn't work with your assistive technology, tell us — it goes on the fix list. Email hello@civicmesa.com with the page and what happened.

This page describes our accessibility commitment and current practices. Formal conformance level and VPAT status are confirmed per release — contact us for the latest.

Talk to us

Have an accessibility requirement? Let's talk.

Tell us what your procurement and accessibility teams need, and we'll show you how Civic Mesa is built for every member of staff and every resident.