> For the complete documentation index, see [llms.txt](https://docs.rooks.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rooks.ai/trust-and-accessibility/create-accessible-forms.md).

# Create Accessible Forms

Rooks provides an accessible foundation for your forms, while giving you the flexibility to shape the experience for your audience.

Accessibility is not something the form assistant can decide entirely on your behalf. Rooks can help generate clear content, maintain readable styling, and provide accessible form controls, but you'll want to be sure to review the finished form and confirm that it meets your organization’s needs.

### Begin with a clear description

When creating a form, tell the form assistant about the people who will complete it and any accessibility considerations you already know about. This context can help Rooks choose simpler language, shorter pages, and more understandable response choices.

For example, you might ask Rooks to:

* Use plain language for a general audience.
* Divide a long intake process into manageable pages.
* Avoid technical terms unless they are explained.

You can refine the language later without rebuilding the form.

### Make questions easy to understand

A person should be able to understand what a question is asking without having to infer its meaning from surrounding content. Short labels, useful instructions, and examples can make a form easier for everyone to complete.

Rooks provides labels and validation messages for supported question types. Review the generated wording to make sure those labels still make sense when read on their own. Clearly identify optional questions and explain any required formats, such as how to enter a date or account number.

### Keep the structure predictable

Grouping related questions onto the same page can make a form easier to follow. Page headings should help people understand where they are and what information is being requested.

Conditional logic deserves extra attention because different answers may produce different experiences. Rooks uses conditional visibility to show or hide a question or page; it does not jump someone to an unrelated location. Preview each important path to make sure necessary instructions remain visible and the sequence still feels natural.

### Choose readable styling

Rooks applies styling guardrails intended to support readable text, sufficient text contrast, and visible keyboard focus. These protections provide a helpful starting point, but colors and branding should still be reviewed in the completed form.

Pay particular attention to text placed over colored backgrounds, buttons, error messages, and any colors used to communicate meaning. Avoid relying on color alone to indicate whether something is selected, required, successful, or incorrect.

Logos and images should support the form rather than carry essential instructions. If someone needs information to complete the form, include it as readable text as well.