Built to be usable by everyone.
Accessibility is part of how we serve public bodies and their communities. Governly is designed and tested to conform with WCAG 2.2 Level AA.
This Accessibility Conformance Report describes the conformance of the Governly web application with WCAG 2.2 Level A and Level AA. Conformance levels are based on automated testing, manual keyboard-only operation, and screen-reader testing across representative pages of each functional area.
Product Information
| Name of Product / Version | Governly — product version 20260617 |
|---|---|
| Report Date | June 17, 2026 |
| Product Description | Web application for managing board meetings, agendas, strategic planning, and organizational communications. |
| Contact Information | support@governly.com |
| Notes | Scope is the Governly web application user interface. |
| Evaluation Methods Used | Automated testing (axe-core); manual keyboard-only operation; screen-reader testing with VoiceOver (Safari, macOS) and NVDA (Windows); text resize to 200% and reflow at 320 CSS pixels. Conducted across representative pages of each functional area: authentication, meetings, agenda and item preparation, AI assistant, settings, and administration. |
Applicable Standards / Guidelines
This report covers the degree of conformance for the following accessibility standard / guideline:
| Standard / Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.2, Level A | Yes |
| Web Content Accessibility Guidelines 2.2, Level AA | Yes |
| Web Content Accessibility Guidelines 2.2, Level AAA | No |
Terms
The terms used in the Conformance Level column are defined as follows:
- Supports — The functionality of the product has at least one method that meets the criterion without known defects, or meets with equivalent facilitation.
- Partially Supports — Some functionality of the product does not meet the criterion.
- Does Not Support — The majority of product functionality does not meet the criterion.
- Not Applicable — The criterion is not relevant to the product.
- Not Evaluated — The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.
WCAG 2.2 Report
The tables below record the conformance level for each Level A and Level AA success criterion in WCAG 2.2, with remarks describing how the product conforms or why a criterion does not apply.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | Informative images provide text alternatives; icon-only buttons and links expose accessible names (via aria-label or visually-hidden text); purely decorative icons are hidden from assistive technology (aria-hidden). |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | The product contains no prerecorded audio-only or video-only content. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | The product contains no prerecorded synchronized media. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | The product contains no prerecorded synchronized media. |
| 1.3.1 Info and Relationships | Supports | Structure uses semantic landmarks and a logical heading hierarchy; form fields are programmatically associated with their labels and related controls are grouped with accessible group names; data tables use header cells. These relationships are exposed to assistive technology. |
| 1.3.2 Meaningful Sequence | Supports | The DOM reading order matches the visual presentation order; styling is not used in a way that alters the meaningful sequence. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely solely on shape, size, color, or visual location; controls are identified by text and accessible names. |
| 1.4.1 Use of Color | Supports | Color is not the only means of conveying information or state; selected/active and toggle states are also conveyed through text, icon shape, and exposed states (e.g., aria-pressed, aria-current). |
| 1.4.2 Audio Control | Not Applicable | No audio plays automatically. |
| 2.1.1 Keyboard | Supports | All functionality is operable with a keyboard alone, including custom menus, dialogs, disclosures, and toggle groups. |
| 2.1.2 No Keyboard Trap | Supports | Keyboard focus is never trapped; dialogs that constrain focus while open are dismissible with Escape, which returns focus to the triggering control. |
| 2.1.4 Character Key Shortcuts | Not Applicable | The product defines no single-character key shortcuts. |
| 2.2.1 Timing Adjustable | Supports | There are no time limits on reading or interacting with content. |
| 2.2.2 Pause, Stop, Hide | Supports | Transient status notifications are brief, and their content is also conveyed to assistive technology, so no essential auto-updating content persists in a way that would require a pause, stop, or hide mechanism. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No content flashes more than three times per second. |
| 2.4.1 Bypass Blocks | Supports | A “Skip to main content” link is provided as the first focusable element, allowing keyboard users to bypass the header and navigation. |
| 2.4.2 Page Titled | Supports | Each page has a unique, descriptive title that identifies its purpose. |
| 2.4.3 Focus Order | Supports | Focus order follows a logical, meaningful sequence; dialogs move focus into the dialog on open and restore focus to the triggering control on close. |
| 2.4.4 Link Purpose (In Context) | Supports | The purpose of each link is clear from its link text or its programmatically-determined context. |
| 2.5.1 Pointer Gestures | Not Applicable | No multipoint or path-based gestures are used; all actions use a single pointer. |
| 2.5.2 Pointer Cancellation | Supports | Single-pointer actions complete on the up-event, allowing a pointer-down to be aborted. |
| 2.5.3 Label in Name | Supports | For controls with visible text labels, the accessible name contains the visible label text. |
| 2.5.4 Motion Actuation | Not Applicable | No functionality is operated by device or user motion. |
| 3.1.1 Language of Page | Supports | The default human language of each page is set programmatically via the lang attribute on the html element. |
| 3.2.1 On Focus | Supports | Moving focus to a component does not trigger an unexpected change of context. |
| 3.2.2 On Input | Supports | Changing a form control does not automatically cause an unexpected change of context; such changes require an explicit action. |
| 3.2.6 Consistent Help (WCAG 2.2) | Supports | Help mechanisms appear in a consistent relative order on the pages where they are available. |
| 3.3.1 Error Identification | Supports | Input errors are detected, described in text, and programmatically associated with the field in error so assistive technology can convey them. |
| 3.3.2 Labels or Instructions | Supports | Form fields have persistent, visible labels; required fields and expected input are indicated in text. |
| 3.3.7 Redundant Entry (WCAG 2.2) | Not Applicable | No process requires re-entering information already provided in the same session. |
| 4.1.1 Parsing | Not Applicable | This criterion was removed in WCAG 2.2 and is retained here for reference only. |
| 4.1.2 Name, Role, Value | Supports | Custom interactive components expose a correct name, role, and state to assistive technology — e.g., menus expose expanded/collapsed state, toggle controls expose pressed state, dialogs expose a dialog role and accessible name, and disclosures expose expanded state and the region they control. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | No live synchronized media is present. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | No prerecorded synchronized media is present. |
| 1.3.4 Orientation | Supports | Content does not lock to a single display orientation; it adapts to both portrait and landscape. |
| 1.3.5 Identify Input Purpose | Supports | Inputs that collect information about the user identify their expected purpose via the autocomplete attribute. |
| 1.4.3 Contrast (Minimum) | Supports | Text and images of text meet at least a 4.5:1 contrast ratio (3:1 for large text). |
| 1.4.4 Resize Text | Supports | Text can be resized up to 200% without loss of content or functionality and without requiring horizontal scrolling. |
| 1.4.5 Images of Text | Supports | Text is presented as real text rather than images of text. |
| 1.4.10 Reflow | Supports | Content reflows to a single column at 320 CSS pixels wide without loss of information or functionality and without two-dimensional scrolling. |
| 1.4.11 Non-text Contrast | Supports | User-interface components and meaningful graphics — including icon controls, control borders, and focus indicators — meet at least a 3:1 contrast ratio against adjacent colors. |
| 1.4.12 Text Spacing | Supports | No loss of content or functionality occurs when text spacing (line height, and paragraph, letter, and word spacing) is overridden. |
| 1.4.13 Content on Hover or Focus | Supports | Content revealed on hover or focus is dismissible without moving the pointer, can be hovered, and remains visible until dismissed. |
| 2.4.5 Multiple Ways | Supports | More than one way is available to locate content (persistent navigation plus in-context links). |
| 2.4.6 Headings and Labels | Supports | Headings and labels are descriptive of the content and purpose they introduce. |
| 2.4.7 Focus Visible | Supports | A visible keyboard focus indicator is provided for all interactive elements through a global focus-visible style. |
| 2.4.11 Focus Not Obscured (Minimum) (WCAG 2.2) | Supports | When a component receives keyboard focus it is not entirely hidden by author content such as sticky headers or overlays. |
| 2.5.7 Dragging Movements (WCAG 2.2) | Not Applicable | No functionality requires a dragging movement. |
| 2.5.8 Target Size (Minimum) (WCAG 2.2) | Supports | Interactive targets are at least 24 by 24 CSS pixels, or have sufficient spacing. |
| 3.1.2 Language of Parts | Not Applicable | No passages or phrases in a language different from the page default were identified. |
| 3.2.3 Consistent Navigation | Supports | Navigation mechanisms that repeat across pages occur in the same relative order. |
| 3.2.4 Consistent Identification | Supports | Components with the same functionality are identified consistently across the application. |
| 3.3.3 Error Suggestion | Supports | When an input error is detected and a correction is known, a suggestion is provided in text and associated with the field. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Actions that modify or delete user data require explicit confirmation before they take effect. |
| 3.3.8 Accessible Authentication (Minimum) (WCAG 2.2) | Supports | Authentication uses a passwordless email link and requires no cognitive function test such as memorizing or transcribing a password or solving a puzzle. |
| 4.1.3 Status Messages | Supports | Status messages such as confirmations, errors, and loading states are exposed to assistive technology through live regions and are announced without moving focus. |
Legal Disclaimer
This Accessibility Conformance Report (ACR) describes the conformance of Governly product version 20260617, as evaluated on June 17, 2026, with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. It is provided for informational purposes to support customers’ procurement and accessibility-evaluation activities.
Basis and method of evaluation. This report is a self-assessment prepared by Governly’s own staff. It is not an independent third-party audit, and no independent verification or certification of conformance is offered or implied. Findings are based on internal testing using the methods described in this report — Automated testing (axe-core); manual keyboard-only operation; screen-reader testing with VoiceOver (Safari, macOS) and NVDA (Windows); text resize to 200% and reflow at 320 CSS pixels. Conducted across representative pages of each functional area: authentication, meetings, agenda and item preparation, AI assistant, settings, and administration — and are provided in good faith to the best of Governly’s knowledge as of the date above.
Point in time. This report reflects the product as of the version and date stated above. Governly is under active development, and conformance may change in subsequent releases. Governly updates this report periodically and upon material changes; the most recent version supersedes all prior versions.
Scope. This evaluation covers the Governly web application interface only. It does not cover, and Governly makes no representation regarding, content created, uploaded, configured, or authored by customers or their users — including but not limited to uploaded documents and PDFs, agenda and item text, attachments, and other user-supplied materials — or third-party services, integrations, or content outside Governly’s direct control. The accessibility of such content is the responsibility of its author or provider. Features that generate content through automated or AI-assisted analysis produce dynamic output whose accessibility may vary and which is subject to this same scope limitation.
Test environment. Conformance was assessed using Safari, Chrome and screen-reader testing with VoiceOver (Safari, macOS) and NVDA (Windows). Behavior in untested browsers, devices, assistive technologies, or configurations may differ.
No legal determination. Conformance with WCAG 2.2 Level AA does not constitute, and should not be relied upon as, a determination of compliance with any law or regulation, including the Americans with Disabilities Act, Section 508 of the Rehabilitation Act, EN 301 549, or any state or local requirement. Customers remain responsible for their own legal compliance.
Limitation of liability. This report is provided “as is.” To the maximum extent permitted by law, Governly disclaims all warranties regarding this report and assumes no liability arising from reliance on it.
Contact. Accessibility questions and issue reports may be directed to support@governly.com. Governly is committed to ongoing accessibility improvement and addresses reported issues on a monthly cadence.