Accessibility Statement

Last updated:

1. Our Commitment

Fiveoak is committed to making this Site accessible to everyone, including people with disabilities. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA and to comply with applicable accessibility laws.

Accessibility is not a checkbox for us — it is a continuous practice. We review every page before release and address issues as they are found or reported.

2. What We've Done

Accessibility measures implemented on this Site include:

  • Semantic HTML structure. Every page uses a single <h1> with no skipped heading levels. Landmark regions (<header>, <main>, <footer>, <nav>) are present on every page.
  • Skip-to-content link. A "Skip to main content" link appears at the top of every page and becomes visible on keyboard focus, allowing keyboard users to bypass the header navigation.
  • Color contrast verified. All text/background color combinations have been chosen to meet or exceed the WCAG AA ratio of 4.5:1 for normal text and 3:1 for large text and UI components. We use the design token system locked in our internal design spec to enforce these ratios.
  • Keyboard navigable. All interactive elements (links, buttons, form fields, navigation menus) are reachable and operable by keyboard alone.
  • Visible focus indicators. Every keyboard-focused element shows a visible focus ring. We do not suppress the browser focus outline without providing a clear custom replacement.
  • Images have alt text. Informative images carry descriptive alt attributes. Decorative images use alt="" or are rendered as CSS backgrounds or aria-hidden SVGs.
  • Forms are labeled. Every form field has a visible <label> that is programmatically associated with its input. Error messages use role="alert" and aria-describedby to communicate to screen readers.
  • Automated testing on every build. We run axe-core against every public route as part of our build and QA process. Zero violations are required before any change ships.
  • No cookies, no consent banners. This Site sets zero cookies and uses no advertising or tracking scripts, which removes a common source of accessibility friction (cookie banners that can be difficult to dismiss with keyboard or screen readers).
  • No autoplay media. The Site contains no auto-playing video, audio, or animation. Motion is minimal and respects prefers-reduced-motion.
  • Self-hosted fonts. The Lato font is served from our own servers. No third-party font CDN requests are made on page load, eliminating a class of FOUT-related layout shift that can disrupt screen-magnification users.

3. Known Limitations

We are committed to transparency about areas we are actively monitoring or improving:

  • Cloudflare Turnstile (bot-protection widget). Our demo-request form uses Cloudflare Turnstile, a third-party bot-protection widget. Turnstile injects its own <iframe> and manages its own keyboard and screen-reader experience. We have wrapped the widget with role="group" and a descriptive aria-label to give it a meaningful context in the accessibility tree. We evaluate Turnstile's a11y behavior periodically and will contribute issues upstream (or switch to an alternative) if we identify material barriers for users of assistive technology.
  • Product mock images. Certain decorative in-page product illustrations (dashboard previews, phone mocks) are marked aria-hidden="true" or role="presentation" because they are illustrative only and do not convey unique information not available in surrounding text. If you need a description of any illustration, please contact us.

4. How to Report an Issue

Encountered an accessibility barrier on this Site? Please tell us. We take every report seriously and aim to address confirmed issues within a reasonable timeframe.

Email: [email protected]

When you report an issue, it helps to include:

  • The URL of the page where you encountered the barrier.
  • A description of the barrier and what you were trying to do.
  • The assistive technology you were using (if applicable) — e.g., screen reader name and version, browser, operating system.

We aim to acknowledge accessibility reports within 5 business days and to provide a resolution or workaround within 30 days where technically feasible.