Accessibility | TRULNK

Our Commitment

TRULNK LLC is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards to ensure we provide equal access to all users.

Conformance Status

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, the current published version of WCAG. We also align our practices with the prior WCAG 2.1 Level AA criteria. These guidelines explain how to make web content more accessible for people with disabilities and more user-friendly for everyone.

We assess conformance through a combination of automated testing tools, manual testing, ongoing review of our user interface, and feedback from users. We treat accessibility as a continuous improvement process rather than a fixed milestone — while we strive for full conformance, some areas may still be in the process of improvement.

Measures We Take

TRULNK takes the following measures to ensure accessibility:

Include accessibility as part of our development process and design reviews
Provide skip navigation links on all pages
Use semantic HTML elements and ARIA attributes for interactive components
Ensure sufficient color contrast ratios for text and interactive elements
Support keyboard navigation throughout the application
Associate all form inputs with descriptive labels
Announce dynamic content changes and form errors to assistive technologies
Provide text alternatives for non-text content

Known Limitations

Despite our best efforts, some content may not yet be fully accessible. We are actively working to identify and resolve issues. Known areas where we are working to improve include:

Embedded payment forms provided by Stripe (Stripe Checkout iframes) are governed by Stripe's own accessibility implementation. We rely on Stripe's ongoing improvements to these embedded components.
Bot-detection challenges provided by Cloudflare Turnstile may occasionally surface interactive challenges; the visual challenges are Cloudflare-controlled but should remain accessible to screen readers and keyboard users in most cases.
Complex dashboard interfaces with real-time data (such as live call monitoring, analytics, and the admin operations console) are being progressively enhanced for screen reader compatibility and may not yet announce all dynamic state changes optimally.
The phone-number-selection step during onboarding lists multiple phone numbers from a third-party provider (Twilio); the rendering is accessible, but the selection experience may benefit from clearer instructions and additional keyboard navigation cues, which we are working to improve.
Calendar integration setup (Google Calendar, Microsoft Outlook) redirects to third-party OAuth consent screens; accessibility on those screens is controlled by the respective providers.

Feedback and Contact

We welcome your feedback on the accessibility of TRULNK. If you encounter any barriers or have suggestions for improvement, please contact us:

TRULNK LLC
P.O. Box 631
Roswell, GA 30077
Email: accessibility@trulnk.com

We aim to respond to accessibility feedback within 5 business days and to resolve reported issues as quickly as possible. If you are not satisfied with our response, you may escalate the matter by contacting us at legal@trulnk.com.

Compatibility

TRULNK is designed to be compatible with the following assistive technologies:

Screen readers (including NVDA, JAWS, and VoiceOver)
Screen magnification software
Speech recognition software
Keyboard-only navigation

TRULNK is designed to work with current versions of major browsers including Chrome, Firefox, Safari, and Edge.

Technical Specifications

The accessibility of TRULNK relies on the following technologies:

HTML
WAI-ARIA
CSS
JavaScript

These technologies are relied upon for conformance with the accessibility standards used.