Built in
Keyboard navigation, labeled inputs, focus states, and RTL layout support out of the box.
Your responsibility
Writing clear labels/help text, choosing sufficient color contrast in Design, and testing your specific field choices.
1
Write real labels, not just placeholders
Placeholder text disappears on focus and isn’t a reliable label for screen readers — always fill in the field’s Label.
2
Keep required-field messaging clear
Use the field’s help text to explain why something is required, especially for fields that become required conditionally via Logic.
3
Set language and direction correctly
For non-English forms, set Language in Form settings so screen readers pick the right pronunciation rules; RTL languages flip layout direction automatically.
4
Mind color contrast in Design
If you set a custom stepper color or design, check contrast against your background — especially for progress indicators and buttons.
5
Test with a keyboard and a screen reader
Tab through a real published form before sending it to real respondents, particularly if it uses heavy Logic branching or a multi-page wizard.
Accessibility is an ongoing effort, not a checkbox — if you find a concrete a11y issue in the fill experience, please report it with the field type and assistive technology involved.