> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/zakladka-audyt-naruszenia-wcag/wcag-strona-jako-formularz.md).

# WCAG - page as a form

For WCAG compliance in the page properties (**Properties** → **WCAG**) a new parameter was created (**roleForm**="true" / roleForm="false"):

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FYJj4sGOQjNHR2QNuRzCM%2Fimage.png?alt=media&amp;token=f92990dd-7223-4304-a493-6b376ce67efb" alt=""><figcaption><p><em><strong>Figure 1.</strong> The "Page contains a form" parameter in Eximee Designer</em></p></figcaption></figure>

If the parameter is checked, the application page is assigned the "form" role:

```
<div data-ex-e2e="form-presenter" class="form ex-grid ng-tns-c200-0 ng-star-inserted" id="demo" mid="demo" role="form">
            <div class="form-pages ng-tns-c200-0 ng-star-inserted">
```

By default, this parameter is enabled, because most pages in applications serve the role of a form. However, if we wanted to design a page so that it does not contain any form, according to WCAG standards it should not have such a role:

```
<div data-ex-e2e="form-presenter" class="form ex-grid ng-tns-c200-0 ng-star-inserted" id="demo" mid="demo">
            <div class="form-pages ng-tns-c200-0 ng-star-inserted">
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/zakladka-audyt-naruszenia-wcag/wcag-strona-jako-formularz.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
