# WCAG

{% hint style="info" %}
Introduction to WCAG (Consdata blog article)

[What is WCAG and why should you implement the standard in your organization?](https://consdata.com/pl/blog/biznesowy/co-to-jest-wcag-i-dlaczego-nalezy-wdrozyc-ten-standard-w-swojej-organizacji)
{% endhint %}

{% hint style="info" %}
WCAG in banks (Consdata blog article)

[WCAG in banks – a legal obligation or an opportunity for competitive advantage?](https://consdata.com/pl/blog/biznesowy/wcag-w-bankach-obowiazek-prawny-czy-szansa-na-przewage-konkurencyjna)
{% endhint %}

{% hint style="info" %}
WCAG tests (Consdata blog article)

[WCAG accessibility testing](https://consdata.com/pl/blog/biznesowy/testowanie-dostepnosci-wcag)
{% endhint %}

{% hint style="info" %}
Automated accessibility testing (Consdata blog article)

[Did you know that in Jest you can automatically test accessibility (a11y)?](https://blog.consdata.tech/2025/05/19/automatyczne-testowanie-dostepnosci.html)
{% endhint %}


---

# 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/wcag.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.
