Accessibility Statement

Last updated 2026-10-19. This statement covers the website at targa.dev and the dashboard at app.targa.dev. It follows the statement model of the European Accessibility Act and is reviewed each time the interface changes in a way that matters.

What we aim for

Targa is built to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA on every screen, by default. The design system every screen is built from checks colour contrast in every theme as part of the build, keeps focus visible, keeps targets at least 24 pixels, works in high-contrast and forced-colours modes, respects reduced motion, and reflows down to 320 pixels wide and 400% zoom. Every page states its language and reading direction, in all 44 languages Targa runs in.

Targa is a microenterprise, which the European Accessibility Act does not oblige to meet its requirements for services. We apply them anyway, and this statement is published so that you can hold us to them.

Where we stand

targa.dev and app.targa.dev are partially conformant with WCAG 2.2 AA: most of the content conforms, and the parts that do not are listed below with the reason and what we are doing about them.

Known gaps

The investor deck page (targa.dev/pitch) is a self-contained document outside the design system. It has not been reviewed against WCAG 2.2 and is not part of the Service. It will be reviewed or withdrawn.
Charts on the dashboard show numbers as bars, sparklines and score dials. Each carries its value as text, but a table view of the underlying numbers is not available everywhere yet. We are adding one.
Sign-in through Google, Apple and Telegram uses those providers' own buttons and windows, whose accessibility we do not control.
Screen-reader passes are done on macOS and iOS (VoiceOver). A pass with NVDA on Windows is pending; components move to "stable" in our library only after it.
The Telegram bot's messages are shown by Telegram's own apps and follow their accessibility.

How we test

Automated checks run on every change (contrast across every theme, the focus and structure rules above). Each component in the library gets a manual pass with a keyboard and a screen reader before it is marked stable. Automated tools find roughly a third of accessibility problems, so the manual pass is the part that matters.

Tell us

If something on targa.dev or in the dashboard is hard or impossible to use, write to [email protected] with the page and what happened. We answer within 10 working days, and tell you what we will do and when. If you are not satisfied with our answer, you can turn to the authority responsible for the accessibility of digital services in the country where you live; in the European Union, each member state names one under the European Accessibility Act.

About this statement

This statement was prepared on 2026-10-19 from the design system's own checks and manual review, and is updated whenever the known gaps change. It is reviewed at least once a year.