Accessibility statement
We sell accessibility conformance, so we publish our own.
The pages residents use are the pages that have to conform. This statement covers the OptimoGov resident portal and the staff console, the standard we build to, how we test, what we know is outstanding, and how to tell us when we have got it wrong.
Last reviewed September 2026. Accessibility contact: accessibility@optimogov.com
Summary
- Standard
- WCAG 2.1 Level AA
- Scope
- Resident portal, staff console, generated documents and emails
- Evidence
- Accessibility conformance report, available on request
- Contact
- accessibility@optimogov.com
- Standard
- WCAG 2.1 Level AA
- Testing
- Keyboard and screen reader, on the resident paths
- Documents
- Permits and invoices as tagged PDFs
- Response
- Barrier reports acknowledged within two business days
What conformance covers
Not the marketing pages. The pages residents actually use.
This is the distinction most vendors get wrong. A conformance claim about a product website is worth very little to your ADA coordinator. The scope that matters is the resident's whole path, and everything the platform generates along it.
- Booking and registration. Finding a space, checking availability, applying, uploading a document, signing a waiver and paying, completable by keyboard alone and tested with screen reader software.
- Generated documents. Permits, invoices, receipts and confirmations produced as tagged, accessible PDFs rather than images of documents.
- Notification emails. Confirmations and reminders as accessible HTML with a plain text alternative.
- The staff console. Also in scope, because your staff include people who use assistive technology and Title II does not stop at the public-facing page.
- Contrast and resizing. AA contrast ratios throughout, resizable to 200% without loss of content or function, and no meaning carried by color alone.
- Error handling. Labels, instructions and validation messages exposed to assistive technology rather than shown only as a red outline.
The regulatory dates
Stated correctly, because several vendors still publish the old ones.
The Department of Justice published an interim final rule on April 20, 2026 extending both ADA Title II web accessibility compliance dates by one year. The WCAG 2.1 Level AA standard itself did not change.
| Entity | Date | Previously |
|---|---|---|
| Public entities with a total population of 50,000 or more | April 26, 2027 | April 24, 2026 |
| Public entities under 50,000, and any special district government | April 26, 2028 | April 26, 2027 |
In Canada, AODA in Ontario and the Accessible Canada Act are addressed by the same WCAG 2.1 AA conformance work.
Known limitations, and how to report one
A statement without limitations is not a statement.
We test continuously and we still find issues. Where something is outstanding we would rather you knew about it from us than discovered it yourself.
- Third-party components. Where a payment gateway or an identity provider renders its own screens within a booking path, its conformance is that provider's. We name which ones and will supply what we hold on each.
- Customer-authored content. Facility descriptions, images and documents uploaded by your staff are your content. The platform prompts for alternative text and will not stop a staff member skipping it, so your own content standards still matter.
- Legacy configurations. An older configuration migrated from a previous system can carry non-conformant content. We flag it during implementation rather than after.
- How to report a barrier. Email accessibility@optimogov.com with the page, what you were trying to do and the assistive technology in use. We acknowledge within two business days, give an assessment within ten, and tell you the remediation timeline or why we disagree.
Ask us for the conformance report before you shortlist.
Ask every vendor on your list for the same thing. It is the single most useful question in a municipal software evaluation.