Govinity Accessibility Statement

    Public Portal and public meeting documents. Last updated October 23, 2026.

    Govinity, Inc. is committed to making its public-facing platform accessible to all residents, including people with disabilities. Residents use the Govinity Public Portal to find meetings, read agendas and minutes, watch live and recorded meetings, look up legislation and votes, learn about boards and commissions, apply to serve, sign up to speak and submit public comment. This statement describes the accessibility of that platform, how we keep it accessible, and how to reach us.

    Standard

    We conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, published by the World Wide Web Consortium (W3C). WCAG 2.1 Level AA is the technical standard adopted by the U.S. Department of Justice rule under Title II of the Americans with Disabilities Act for state and local government web content and mobile applications (28 CFR Part 35, Subpart H).

    Conformance status

    The Govinity Public Portal conforms to WCAG 2.1 Level AA. We keep it that way with a routine that runs every day, described below: every change is checked for accessibility before it reaches residents, anything that needs attention is written down and fixed, and the fix goes out to every city and county we serve. Our Accessibility Conformance Report (the standard VPAT report, WCAG edition) lists the result for every WCAG 2.1 requirement and is available to our customers on request from [email protected].

    How we keep the portal accessible

    Accessibility is not a one-time audit for us. It is a routine with four steps that repeats every day.

    • Check. Before any change reaches the portal, it is tested automatically for accessibility. Every page and every shared part of the site is checked in both light and dark mode, and a change cannot go live until it passes. Every night, an automated review also goes through the whole portal the way a resident would, opening menus and tabs along the way and including the pages residents use when they are signed in.
    • Document. Anything the checks find is written down as a task for our engineers: which page it affects, what the problem is, which accessibility rule it touches, and how urgent it is. After each round of improvements we update our published accessibility report.
    • Fix. Our engineers correct the problem. Anything that stops a resident from doing something, such as reading an agenda, watching a meeting or submitting a comment, goes to the front of the line. Problems reported by residents or city staff are handled the same way.
    • Release. The correction is tested the same way and then goes live for every city and county we serve, with nothing for anyone to install. The next nightly review confirms the problem is gone and closes it out.

    What is built in

    • Keyboard and screen reader. Every page works with a keyboard alone and with a screen reader. Buttons and links are real buttons and links, every control has a name a screen reader can say, and each page has a clear title and a way to skip straight to the content.
    • Meeting video. Live streams and recordings have captions, generated automatically in English, and residents can switch the captions to other languages. Where a transcript has been published, it appears on the meeting's page.
    • Agendas and minutes. The agendas and minutes the portal generates are made so a screen reader can read them like any other document, with headings, tables, bookmarks and a title.
    • Attachments. When city staff attach a document, the portal can check it for accessibility before it is published and tell them what it found.

    Compatibility

    The Public Portal works in current versions of Chrome, Edge, Firefox and Safari, on computers, tablets and phones. It works with screen readers such as NVDA, JAWS, VoiceOver and TalkBack, with a keyboard alone, and with the text enlarged up to four times. Pages adjust to narrow screens such as a phone without sideways scrolling. The portal follows the language set in the visitor's browser (English, Spanish, Tagalog, Simplified and Traditional Chinese) and the visitor's choice of light or dark display.

    Technology

    The portal is built with the standard web technologies that browsers and screen readers are designed for (HTML, CSS, JavaScript and WAI-ARIA). The documents it generates use the accessible PDF format (PDF/UA).

    How we test

    We test the portal ourselves: automated accessibility checks on every page, in light and dark mode, plus using it with only a keyboard, repeated through the daily routine above. Before a new city or county goes live, we also test the pages residents use most with screen readers on that government's own portal. Our current Accessibility Conformance Report is dated October 23, 2026.

    Feedback and contact

    We welcome feedback on the accessibility of the Govinity Public Portal. If something on the portal is hard for you to use, or you need a document in a different format, please contact:

    • Govinity support: [email protected]. Please tell us the page you were on, what you were trying to do, and the browser and any assistive technology you use.
    • Your city or county: the government that publishes this portal is responsible for the content on it and can provide documents in other formats. Its ADA coordinator or clerk is listed on its own website.

    What to expect: we aim to reply within two business days and tell you how and when the problem will be fixed. If you are not satisfied with our response, the government that publishes this portal has a formal complaint process under Title II of the ADA.

    What this statement covers

    This statement covers the Govinity Public Portal at public.govinity.com, the meeting video and documents on it, and the account pages residents use to apply to boards, sign up to speak and submit public comment. It does not cover the government's own website or documents kept elsewhere.