Governance infrastructure should work for everyone.
Civerent is building accessibility into its public website and governance workflows as a permanent product requirement.
Effective August 23, 2026
1. Commitment
Civerent is committed to improving access to its website and governance platform for people with disabilities.
Accessibility is treated as an ongoing product requirement. This statement describes current goals and practices but is not a claim of complete conformance or formal third-party certification.
2. Accessibility target
Civerent uses the Web Content Accessibility Guidelines version 2.2 Level AA as its current design and evaluation target.
WCAG is applied as practical guidance for perceivable, operable, understandable, and robust experiences. Meeting a target requires continuing testing across content, interactions, browsers, devices, and assistive technologies.
3. Current practices
- Semantic page structure and descriptive headings.
- Visible keyboard focus styles for interactive controls.
- Keyboard-operable links, buttons, and forms using standard web controls.
- Programmatic labels for public form fields.
- Text alternatives or accessible labels for meaningful interface icons.
- Color choices designed for readable contrast in the primary dark interface.
- Responsive layouts intended to support zoom and different viewport sizes.
- Status text designed to communicate form outcomes without relying only on color.
4. Testing approach
- Automated linting and application tests during development.
- Keyboard review of important navigation and form workflows.
- Responsive visual review across representative viewport sizes.
- Inspection of labels, landmarks, headings, focus behavior, and error feedback.
- Future expansion into automated accessibility scanning and assistive-technology testing.
5. Known limitations
Civerent is under active development, and some experiences may not yet fully satisfy every WCAG 2.2 Level AA success criterion.
Complex governance tables, dense dashboards, exported documents, third-party authentication interfaces, and newly released features may require additional accessibility improvement.
6. Compatibility
Civerent is designed for current versions of major standards-based browsers. Accessibility behavior can vary by browser, operating system, device, settings, and assistive technology.
Users should keep browsers and assistive technologies reasonably current where possible.
7. Assistance and alternatives
If a feature, document, or workflow is not accessible, contact Civerent and describe the page, task, assistive technology, and barrier encountered.
Civerent will evaluate reasonable alternatives and remediation options based on the request, product capability, and applicable requirements.
8. Accessibility feedback
- Include the page address or feature name.
- Describe what you were trying to accomplish.
- Describe the barrier and any error message.
- Identify the browser and assistive technology when comfortable doing so.
- Do not include passwords or unnecessary sensitive information.
References
Contact Civerent
Questions and reports
Contact Civerent about this document, report a concern, or request additional information.
support@civerent.comDo not send passwords, authentication tokens, government identification numbers, vulnerability exploit code, or other highly sensitive information by ordinary email.