Skip to main content

Accessibility Statement

Civilly is committed to digital accessibility. We work toward WCAG 2.1 AA conformance and continuously improve our platform for users with disabilities, including screen reader support and keyboard navigation.

Effective:

Key Takeaways

  • We work toward WCAG 2.1 Level AA conformance for digital accessibility
  • Full keyboard navigation is supported throughout the platform
  • Screen readers (NVDA, JAWS, VoiceOver) are regularly tested
  • Color contrast meets or exceeds 4.5:1 ratio for text readability
  • We welcome accessibility feedback via email or our support form
  • Quick Exit feature works with keyboard (ESC key) for safety

Plain English Promise: We have written this accessibility statement in clear, accessible language. No lawyer-speak, no hidden meanings. If something is unclear, please ask us.

Our Commitment to Accessibility

At Civilly, we believe everyone deserves equal access to tools that help them through difficult life transitions. We are committed to providing a website and application that is accessible to the widest possible audience, regardless of ability or technology.

We actively work to increase the accessibility and usability of our platform. Our ongoing accessibility efforts are part of our mission to serve all users with dignity and respect.

Accessibility Standards

Civilly works toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines explain how to make web content more accessible for people with disabilities and more user-friendly for everyone.

WCAG 2.1 is organized around four principles, often referred to as POUR:

  • Perceivable: Information and user interface components must be presentable to users in ways they can perceive
  • Operable: User interface components and navigation must be operable by all users
  • Understandable: Information and operation of the interface must be understandable
  • Robust: Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies

Current Accessibility Status

We have taken the following steps to ensure accessibility:

  • Built our platform using semantic HTML and accessible component libraries
  • Implemented keyboard navigation and screen reader support throughout
  • Ensured color contrast meets WCAG AA requirements
  • Added descriptive alt text to meaningful images
  • Created skip links and proper heading structure for navigation
  • Designed forms with proper labels and error messages

We continue to evaluate and improve accessibility as we develop new features and update existing ones.

Accessibility Features

We have implemented the following accessibility features across our platform:

Keyboard Navigation

  • All interactive elements (buttons, links, form fields) are accessible via keyboard
  • Tab key moves focus forward through the page in a logical order
  • Shift+Tab moves focus backward
  • Enter and Space keys activate buttons and links
  • Arrow keys navigate within menus, dropdowns, and date pickers
  • ESC key triggers Quick Exit for safety and closes modal dialogs
  • Skip links allow users to bypass repetitive navigation

Screen Reader Support

  • Semantic HTML5 elements (nav, main, article, aside) provide document structure
  • ARIA landmarks identify page regions for navigation
  • ARIA labels provide context for interactive elements
  • Live regions announce dynamic content changes
  • Form fields have associated labels that screen readers announce
  • Error messages are linked to their respective form fields
  • Tables include proper headers and captions where applicable

Visual Design

  • Color contrast ratio of at least 4.5:1 for normal text and 3:1 for large text
  • Visible focus indicators on all interactive elements
  • Information is not conveyed by color alone (icons, text, or patterns supplement color)
  • Text can be resized up to 200% without loss of content or functionality
  • Consistent navigation and layout across pages
  • Clear visual hierarchy with distinct headings

Content Accessibility

  • Plain language and clear, concise writing throughout
  • Descriptive headings that convey content structure
  • Link text that describes the destination
  • Alternative text for meaningful images
  • Decorative images are hidden from screen readers
  • Legal pages include "In Brief" summaries for each section
  • Complex information is broken into manageable sections

Forms and Inputs

  • Form fields have visible, associated labels
  • Required fields are clearly marked
  • Error messages are specific and explain how to correct the issue
  • Form validation does not rely solely on color
  • Autocomplete attributes help users fill in common information
  • Input fields have appropriate type attributes for mobile keyboards

Assistive Technology Compatibility

We design and test Civilly to work with the following assistive technologies:

  • Screen readers: NVDA (Windows), JAWS (Windows), VoiceOver (macOS and iOS), TalkBack (Android)
  • Voice recognition: Dragon NaturallySpeaking, Windows Speech Recognition, macOS Voice Control
  • Screen magnification: ZoomText, Windows Magnifier, macOS Zoom
  • Browser extensions: High contrast modes, text-to-speech tools

For the best experience, we recommend using the latest versions of these technologies with current browsers. Chrome, Firefox, Safari, and Edge are supported.

Assessment and Testing

Our accessibility assessment approach includes:

  • Automated accessibility testing integrated into our development workflow
  • Manual testing with screen readers and keyboard navigation
  • Color contrast verification using established tools
  • Testing across different browsers and devices
  • Review of user feedback and accessibility reports
  • Regular evaluation of new features before release

We maintain records of accessibility testing and remediation efforts as part of our ongoing commitment to improvement.

Quick Exit Accessibility

We understand that some users may need to quickly leave Civilly for safety reasons. Our Quick Exit feature is designed to be accessible:

  • Press the ESC key at any time to immediately exit
  • The Quick Exit button is visible on every page and keyboard accessible
  • Screen readers announce the Quick Exit button and its purpose
  • The feature works regardless of where focus is on the page
  • Quick Exit redirects to a neutral website that does not reveal your activity

Known Limitations

We are aware of the following accessibility limitations and are working to address them:

  • User-uploaded documents: PDFs and images you upload may not have accessibility features like alt text or proper tagging. We cannot modify content you upload, but we are exploring ways to help users understand document accessibility.
  • Third-party integrations: Some features that rely on third-party services (such as Plaid for bank connections) may have their own accessibility characteristics that we cannot directly control.
  • Complex data visualizations: Charts and graphs include data tables as alternatives where feasible, though some visual patterns may be challenging to convey to screen reader users.
  • Older help content: Some help articles created before our current accessibility standards may not yet meet all guidelines. We are updating these as part of our ongoing work.

If you encounter an accessibility barrier, please let us know. We will work with you to provide the information you need in an accessible format and use your feedback to improve our platform.

Ongoing Accessibility Efforts

We are committed to continuous improvement in accessibility:

  • Including accessibility considerations in our design and development process
  • Running accessibility tests as part of our development workflow
  • Conducting periodic accessibility reviews
  • Providing accessibility awareness for our team
  • Monitoring and responding to user feedback
  • Staying informed about evolving accessibility standards and best practices
  • Addressing accessibility issues alongside other platform improvements

Accessibility Feedback

We value your feedback on the accessibility of Civilly. If you encounter any barriers or have suggestions for improvement, please let us know through one of these methods:

  • Email: accessibility@civilly.io
  • General support: support@civilly.io
  • Support form: Available in your account settings

When reporting an accessibility issue, it helps if you can include:

  • A description of the accessibility barrier you encountered
  • The page URL or feature where the issue occurred
  • The assistive technology you were using, if applicable
  • Your browser and operating system
  • Any suggestions for how we could improve

We work to respond to accessibility feedback within two business days. If you are experiencing an urgent barrier that prevents you from using Civilly, please indicate this in your message so we can prioritize your request.

Alternative Formats

If you have difficulty accessing any content on Civilly due to a disability, please contact us. We will work with you to:

  • Understand the specific barrier you are experiencing
  • Provide the information you need in an accessible format
  • Identify ways to improve the accessibility of the content

Our goal is to ensure you can access the information and services you need.

Contact Us

If you have questions about this accessibility statement or need assistance accessing any part of Civilly, please contact us:

Civilly Services

San Diego, California, United States

We are committed to providing equal access to our platform. If you need assistance or accommodations, please reach out and we will work with you to find a solution.

Last updated:

Questions?

If you have any questions about this accessibility statement, please don't hesitate to reach out. We're here to help.

Contact Us