Skip to content

Accessibility Statement

Last updated: September 1, 2026

We want this website to be usable by everyone, including people who navigate with a keyboard, a screen reader, magnification or reduced motion. This page records what we have done, what we know is imperfect, and how to tell us when we get it wrong.

Conformance target

We aim to meet WCAG 2.2 Level AA. Parts of this site are assessed automatically on every change and parts are reviewed by hand; because an automated check cannot prove conformance on its own, we hold that standard as a target rather than a statement of full conformance. Where we know we fall short, it is listed below rather than left for you to discover.

What is in place

  • A skip-to-content link as the first focusable element on every page.
  • A visible focus outline on every interactive element, never removed.
  • Motion respects prefers-reduced-motion: scroll behaviour and entrance animations stop.
  • High-contrast and forced-colours modes are handled, including for text rendered as a gradient.
  • Every form control has a real label; icon-only buttons carry an accessible name.
  • Decorative icons are hidden from assistive technology and contain nothing focusable.
  • Fonts are self-hosted and subset, so text renders without waiting on a third party.
  • Page content is revealed without JavaScript — the entrance animation degrades to plain visible content.

Known limitations

  • Demo booking links go to a third-party scheduler (Cal.com). If it blocks you, email us and we will arrange the same outcome another way.
  • The cookie table on our cookie policy scrolls horizontally on a narrow screen. It is a real table with real headers, so it works with a screen reader, but it needs sideways scrolling on a phone.
  • This statement covers futurestacks.com only. The Devfood ordering apps and dashboards are assessed separately — see devfood.com/accessibility for the product marketing site, and ask us during a demo for the live apps.

How this is assessed

Self-evaluation, plus an automated accessibility scan that runs against the built site and blocks a release on any serious or critical issue. Automated testing catches a minority of possible barriers, so it supplements manual review rather than replacing it.

Reporting a barrier

If something on this site prevents you from doing what you came to do, please tell us — it is the fastest way for us to fix it. Email contact@devfood.com with the page address and what happened. We reply to every message, and we will tell you what we are doing about it and when.