# 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="/files/22f55d3bc2b11682aa19cbfc83a2df878812f13e" alt=""><figcaption><p><em><strong>Figure 1.</strong> "Page contains a form" parameter in Eximee Designer</em></p></figcaption></figure>

If the parameter is selected, 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 as forms. However, if we wanted to design a page so that it did 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: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
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>
```

The question should be specific, self-contained, and written in natural language.
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.