You should be able to learn about LFW, contact us, and request work without a mouse or a desktop computer. This statement covers our public website and client portal, the standard we work toward, and how to report a barrier.
Our standard
Our target is WCAG 2.2 Level AA. We have not established full conformance across every page and workflow. Automated checks help us find problems, but passing them does not establish accessibility for everyone.
How this site is built for access
- Keyboard access. We use native links, buttons, and form controls, visible focus indicators, and a skip-to-content link. Our checks include opening menus, moving through dialogs, and returning focus when they close.
- Comfortable controls. Our design target for standalone buttons and navigation controls is at least 44 by 44 CSS pixels. Links within sentences can be smaller.
- Form labels and feedback. Contact and booking forms have visible labels, identify invalid fields, and connect error messages to the affected controls.
- Readable text. We check text against its light or dark background. Our contrast targets are at least 4.5:1 for regular text and 3:1 for large text.
- Reduced motion. Site navigation and decorative animations respect your device’s reduced-motion preference. Interactive demonstrations may have their own playback controls.
- No CAPTCHA puzzles in our forms. Our contact, booking, and free-audit forms use server-side spam checks.
- Built-in accessibility. Improvements are made in the underlying pages and controls. The site uses third-party infrastructure, including Cloudflare; see our privacy policy.
How we check
We use axe-core to check sampled pages for automatically detectable accessibility issues. We also check keyboard operation, visible focus, form feedback, reduced motion, and layouts at phone and desktop widths. Our September 8, 2026 review covered shared navigation and forms, selected English, Spanish, and French public pages, and sample client-portal workflows.
Known limitations
We have not completed a comprehensive review with screen readers and other assistive technologies across every workflow. Complex demonstrations, charts, and downloadable PDFs need further manual review. Screenshots are images of an interface and cannot be operated like the interface itself; archived third-party pages may retain their original barriers.
Tell us
Email hello@lfw.com with the page address, what you were trying to do, and what went wrong. Include your browser or assistive technology if useful. You can also ask for the information in another format or for help completing a task. Leland reviews accessibility reports and prioritizes barriers that prevent access; the time needed for a fix depends on the issue.