Accessibility

Last updated: May 29, 2026

1. Our commitment

We want WayFYI to be usable by everyone, including people who rely on assistive technology to browse the web. WayFYI works toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We treat accessibility as an ongoing responsibility rather than a one-time checklist, and we aim to improve the product as we learn what works and what doesn’t.

2. What we’ve done

The list below describes specific work completed against WayFYI’s public surfaces as of the date above:

• Audited the landing page, sign-in, sign-up, Terms of Service, and Privacy Policy using a combination of automated tooling (Google Lighthouse, jest-axe) and a manual code review against WCAG 2.1 success criteria.
• Most recent Lighthouse Accessibility scores on the production deployment (desktop): home page 96, sign-in 100, sign-up 100, Terms 100, Privacy 100.
• Automated jest-axe scans run as part of our continuous integration across more than 38 component test suites, including every dialog and modal that gates user input.
• Implemented consistent keyboard navigation, focus trapping, and focus restoration across every modal in the app. Each dialog is announced to screen readers with the appropriate ARIA role and label.
• Added a skip-to-main-content link as the first focusable element on every page, so keyboard users can bypass the header chrome in a single Tab.
• Reviewed every form across the auth and signup flows to ensure inputs have programmatically associated labels and that error messages are linked to the input they describe via aria-describedby.
• Verified WCAG 2.1 AA colour contrast on body text app-wide. Our brand blue (#175790) measures 7.49:1 against white, clearing the stricter AAA bar; success green (#13803B) measures 5.03:1, clearing AA.

3. Known limitations

We want to be honest about the scope of the work above and what hasn’t yet been audited. The following areas remain open:

• Authenticated pages — the dashboard, trip editor, and account settings — are covered by automated component-level jest-axe tests but have not yet undergone a full Lighthouse audit or a manual screen-reader walkthrough.
• Mobile-specific accessibility has not been formally audited. Touch-target sizing against WCAG 2.5.8 and viewport reflow behaviour on small screens are tracked as a future pass.
• The landing page has a known heading-hierarchy skip (h1 jumps directly to h3, bypassing h2) that we plan to address.
• We target WCAG 2.1 Level AA, not Level AAA. Some interactive elements may not meet the stricter AAA contrast or touch-target requirements.
• Third-party content embedded in WayFYI — including the Crisp Chat widget and Google Maps — is governed by those vendors’ own accessibility commitments, which we do not control. We will work around limitations where we can, but we cannot guarantee the same level of accessibility for embedded third-party surfaces as for our own.

4. How to report an issue

If you encounter an accessibility barrier in WayFYI, please tell us. Send an email to help@wayfyi.com and include:

• A description of the problem.
• The page URL where it occurred.
• The assistive technology you were using, if relevant (for example, the name and version of your screen reader, the browser, and the operating system).

We’ll do our best to respond promptly and to incorporate fixes into our ongoing accessibility work. Reports help us prioritise, so we’re grateful for the time it takes to write one.

5. Related policies

See also our Terms of Service and Privacy Policy.