Accessibility ensures that everyone—regardless of ability—can interact with your content. It's about creating digital experiences that are inclusive and usable for all, including people who rely on screen readers, keyboard navigation, or other assistive technologies.
With the European Accessibility Act (EAA) coming into effect on June 28, 2025, accessibility is not just a best practice — it’s a legal requirement for many businesses operating in the EU. But compliance aside, accessible design also improves usability for everyone, extends your reach, and reflects your commitment to inclusion.
This article highlights key accessibility principles and tips to help you create flows that are both user-friendly and compliant. While the focus is on the EAA, the guidance also supports alignment with major global standards like the Web Content Accessibility Guidelines (WCAG) and the Americans with Disabilities Act (ADA).
❗Note: This article is for informational purposes only and does not constitute legal advice. Heyflow is not a legal advisor, and you are responsible for ensuring your flows meet applicable accessibility requirements. The topics below are a selection and not a complete list of all requirements.
What Heyflow handles
We take care of many technical aspects of accessibility behind the scenes, including:
Keyboard Navigation
Most blocks support keyboard use (e.g., buttons and form fields).
💡Coming soon: Improved navigation for blocks like Phone, Multiple Choice, and Picture Choice.
Accessible HTML Output
Pages include required elements like
<title>and<html lang="">.
❗Note: If you use custom code in your flow, we can’t guarantee accessibility—please test thoroughly.
What you’re responsible for
While we handle the foundation, you control the content and design—and that has a big impact on accessibility.
Labels
All form fields must include clear, descriptive labels.
Labels help users understand what information is being requested—especially when using screen readers or other assistive technologies.
Add labels directly within the input block settings in Heyflow.
💡Coming soon: Support for rich text labels and label-hiding options.
Non-Text Elements
Any non-text content, such as images, needs to include meaningful alt text.
Alt text helps screen reader users understand the purpose or content of the image.
In Heyflow, you can set this by adding a description to the “alt text” field for each image.
Our icons automatically have an alt text included.
Colors and Contrast
Text must have enough contrast against the background.
Try using tools like Coolors Contrast Checker to double-check your design.
Fonts and Headings
Use readable font sizes—avoid anything too small.
Only one <h1> should be used per page.
💡 If you're embedding your flow into a webpage that already has a <h1>, remove it from your flow to avoid duplicates.
Tools to Help You Check Accessibility
There are several free tools that can help you evaluate how accessible your flow is: