---
title: "Accessibility statement · intentic"
description: "Accessibility status of the intentic website and app, and how to report a problem."
url: "https://intentic.dev/accessibility/"
---

Accessibility

# Accessibility statement

Artur Kurowski, trading as radarsu is committed to making its digital services accessible. This statement covers the [intentic.dev](https://intentic.dev/) website and the [app.intentic.dev](https://app.intentic.dev/) web application. It follows the structure of the Polish public-sector accessibility statement template. The intentic operator is not a public body; an office using intentic publishes its own statement.

[Przeczytaj deklarację po polsku](https://intentic.dev/pl/deklaracja-dostepnosci/)

## Dates and compliance status

Website first published: 6 July 2026. Statement last reviewed: 15 October 2026.

The website and web app are partially compliant with WCAG 2.1 AA. The assessment covers only the screens and automated rules listed below; it does not establish full compliance across all content and features.

## Non-accessible content and limits

After fixes, axe-core found no violations of its automated WCAG 2.2 A/AA rules in the sampled demo screens. Fixes cover contrast, control names, a skip link, keyboard operation of agent cards and the command palette, dialog focus and office refresh announcements. This is a source and demo assessment; it does not establish that fixes are deployed in every running installation. Outside this sample, the component kit retains previously identified contrast and keyboard scrolling issues. We do not invoke statutory exemptions or disproportionate burden.

We have not tested with NVDA, JAWS or VoiceOver, involved disabled users, or completed an audit of a specific deployment. We checked selected keyboard paths, a 320-pixel layout and doubled text size. This is not a full browser-zoom review or a review of every screen, error state, extension and document. Generated forms, Office files and PDFs also need a separate assessment.

## How we prepared this statement and keyboard shortcuts

Prepared on 13 October 2026 using axe-core WCAG 2.1 A/AA self-assessment in Chromium: a demo app sample and the public home, privacy, docs and pricing pages. The 15 October source review expanded the app sample to access, areas, personas, data protection, audit, connections, approvals, workflows, organisation governance and fictional EZD RP and e-Doręczenia data. Automated WCAG 2.2 A/AA rules were checked in three themes; selected screens also used narrow English and Polish layouts. Checks also covered focus and focus restoration, loading and error messages, reduced motion and forced colours. Self-assessment does not replace a full expert audit.

The first Tab in the main app reveals the ‘Skip to main content’ link. The app also lists its shortcuts in keyboard settings.

## Feedback and contact

Send accessibility problems, requests for content in another format, and feedback to [contact@intentic.dev](mailto:contact@intentic.dev?subject=intentic%20accessibility). Include your name, contact method, page address or feature name, the problem and your preferred solution. Do not send sensitive office work data.

We aim to respond without undue delay, normally within 7 days. If resolution takes longer, we will give a new date, no later than 2 months, or offer another way to access the content. These are our voluntary commitments for intentic services.

## Requests and complaints

If you use a deployment run by a public office, request digital accessibility or alternative access from that office. If its response is insufficient, use the complaint procedure in that office's statement. For further help, contact the [Polish Commissioner for Human Rights](https://bip.brpo.gov.pl/). You can also send feedback about intentic itself to the email above.

## Other information

### Mobile apps

This statement covers the website and web app. It does not cover a native mobile application.

### Architectural accessibility

Not applicable to this online service. An office offering intentic describes its premises in its own statement.

### Communication accessibility

Contact the service operator through the email above. Each office provides information about sign-language interpretation and its other contact methods.

## For public offices

An office deploying intentic for staff or citizens must publish its own statement for that deployment. It may use this page's shared-screen findings and test method as a starting point. It must assess its configuration, extensions, content, integrations, contact details, complaint procedure and premises.