Accessibility Statement

The standard

This site is built toward WCAG 2.1 Level AA. That is a target, not a certificate. Nobody issues a “WCAG certified” seal, in the same way that no vendor can call a law firm’s advertising “Bar certified.” So this page does not claim conformance. It lists what is checked and how, and then lists what is not.

Two scopes matter. This statement covers the pages on legalcrm.pro. The intake forms, booking calendar, and client-facing messages a firm sends from the product run on the platform provider’s infrastructure and its own accessibility work, which we configure but did not build.

Checked in the code

Color contrast, by script

Every color pair the design uses for text, body copy on the bone background, muted text, the champagne accent, button labels, and text on the dark forest footer, is tested against the WCAG AA thresholds by a script in this site’s repository (scripts/check-contrast.py). It runs before a deploy and fails if any pair drops below the line. One decorative champagne fill is below the text threshold on purpose and is used only for rules and focus rings, never for words; gold text uses a darker, contrast-safe tone.

Zoom is not blocked

The viewport tag sets no maximum-scale and no user-scalable=no. Pinch-to-zoom on a phone or tablet works the way the device expects.

Reduced motion is honored

If your operating system asks for less motion, the stylesheet reads prefers-reduced-motion: reduce and cuts every transition and animation to effectively nothing, on every page.

Spanish is labeled as Spanish

The Spanish pages declare lang="es" on the page, and Spanish text inside English pages, such as the bilingual conversation on the homepage, carries its own lang attribute. Screen readers use that attribute to choose pronunciation. Spanish read aloud with English rules is not usable, however it looks on screen.

Visible keyboard focus

Links, buttons, and form fields show a visible focus outline when reached by keyboard (:focus-visible in the stylesheet), rather than relying on a browser default that some frameworks strip out.

Works without JavaScript

Every page renders its full content on the server. The tab strips, accordions, and the calculator enhance the page when JavaScript runs and show everything when it does not. The booking page includes a direct link to the calendar and the phone number for anyone who cannot use the embedded frame.

Not yet tested

We would rather say this here than have you find it. Three things have not been done as of this update:

• A screen-reader pass. No page-by-page test with VoiceOver or NVDA has been completed across every page and every interactive element.
• A keyboard-only audit. We have not confirmed that every flow, the tab strips on the homepage and features page, the FAQ accordions, the calculator sliders, and the site navigation, can be completed start to finish with a keyboard alone.
• The booking frame. The calendar on the demo page is an embedded frame from the platform provider. Its accessibility is the provider’s, and we have not audited it. The direct link and the phone number next to it are the fallback.

Until those are done, read this as a site that targets WCAG 2.1 AA and has verified the items above, not as one that has been audited end to end.

Report a barrier

If something on this site is hard or impossible to use with assistive technology, tell us which page and what happened. Use our contact page or call (305) 209-8453. A person in Coral Gables reads it, and a fix that is ours to make goes into the next deploy.