Accessibility Statement

1. Our Commitment

Clienty is committed to ensuring that our marketing site and application are accessible to people of all abilities. We believe legal technology should work for everyone — including the attorneys, staff, and clients who rely on it every day. We treat accessibility as an ongoing effort rather than a one-time project.

2. Standards We Follow

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. These guidelines explain how to make web content more accessible for people with a wide range of disabilities, including visual, auditory, cognitive, and motor impairments.

• Perceivable: Text alternatives for non-text content, sufficient color contrast, and content that adapts to different display sizes.
• Operable: Full keyboard support, no reliance on complex gestures, and predictable focus behavior.
• Understandable: Clear language, consistent navigation, and helpful error messages on forms.
• Robust: Semantic HTML, ARIA where needed, and compatibility with modern screen readers and assistive technologies.

3. Accessibility Features

We've built the following into our marketing site and continue rolling them out across the Clienty application:

• Semantic structure: Proper heading hierarchy, landmarks (nav, main, footer), and semantic HTML elements.
• Keyboard navigation: All interactive elements are reachable with Tab / Shift+Tab and activate with Enter or Space. Visible focus rings indicate the currently focused element.
• Skip to content: A skip link at the top of every page lets keyboard and screen reader users jump past the navigation to the main content.
• Screen reader labels: Buttons, icons, images, form fields, and expandable sections include accessible names, descriptive alt text, and state attributes (aria-expanded, aria-controls).
• Responsive design: Content reflows cleanly at 320px wide and supports browser zoom up to 200% without loss of functionality.
• Reduced motion: We respect the prefers-reduced-motion setting where animations are used.

4. Known Limitations

Despite our efforts, some areas may not yet be fully accessible. We're actively working to address:

• Third-party content: Embedded Stripe payment forms, calendar integrations, and analytics scripts are controlled by their providers. We select vendors that meet accessibility standards but cannot fix issues in their UIs directly.
• Legacy screens: A small number of older application screens are still being migrated to our updated accessible component library.
• Rich media: Some marketing imagery is decorative and not accompanied by transcripts; video captions are being added as content is produced.

5. Supported Assistive Technology

Clienty is designed to work with the latest versions of commonly used assistive technology, including:

• VoiceOver (macOS and iOS)
• NVDA (Windows)
• JAWS (Windows)
• TalkBack (Android)
• Keyboard-only navigation
• Browser zoom and OS-level text scaling

We test against the two most recent major versions of Chrome, Firefox, Safari, and Edge.

6. Reporting an Issue

If you encounter an accessibility barrier on our site or in the application, please let us know. Your feedback helps us improve. When reporting an issue, please include:

• The page URL or screen where you encountered the issue
• A description of the problem
• The assistive technology, browser, and operating system you were using

Email us at clientysupport@clienty.io. We aim to respond to accessibility reports within 5 business days.

7. Ongoing Work

Accessibility is a moving target. We review new features for accessibility before release, run automated checks in our build pipeline, and update this statement as our practices and the underlying standards evolve.