Skip to content
TalkerApp

Accessibility statement

Last updated:

OneFinger - Łukasz Czerwiński is committed to making its website accessible, in accordance with the Polish Act of 4 April 2019 on the digital accessibility of websites and mobile applications of public sector bodies.

This accessibility statement applies to the website gettalker.app.

  • Date the website was published:
  • Date of the last significant update:

That act binds public sector bodies, not us. We follow it, and the statement format of the Polish Ministry of Digital Affairs (version 2.0), voluntarily, because everyone should be able to use gettalker.app, including people who use only a keyboard or a switch, a screen reader, magnification, voice control or a slow way of typing. TalkerApp is for adults who type to speak, and many of them use a computer in their own way, so this site has to work for them first.

Compliance status

This website is partially compliant with the annex to the Polish Act of 4 April 2019 on the digital accessibility of websites and mobile applications of public sector bodies, due to the non-compliances and exemptions listed below.

Non-accessible content

Non-compliance with the annex

An audit in October 2026 found two non-compliances. We fixed both on October 19, 2026. We list them here until the auditor has checked the fixes.

  • Focus order on every page (WCAG 2.4.3). After “Accept” or “Reject” on the cookie bar, keyboard focus jumped to the first button in the page content, past the “Skip to content” link and the menu. Now it goes back to the start of the page, to the “Skip to content” link, and the next Tab leads to the menu.
  • The “Theme” and “Cookies” switches in the footer of every page (WCAG 4.1.2). They were groups of radio buttons. A screen reader announced the position of each option in the group, and the choice changed as soon as you moved through it with the arrow keys. Now each option is a toggle button of its own: a screen reader says which one is pressed, and the choice changes only when you press a button.

Content not within the scope of the act

The content below comes from third parties. We did not produce, fund or commission it, and it is not under our control (Article 3(2)(5) of the act).

  • The bot check on the sign-up form on the waitlist page comes from Cloudflare (Turnstile). Cloudflare says that it meets WCAG 2.2 Level AA. We have not verified that ourselves. The check can ask for one click, and the form says so while it waits. If the check cannot run, for example because a content blocker stops it, the form tells you at once and gives our e-mail address. Write to us and we will help you join the waitlist by e-mail. We then ask for your agreement in writing, as the form does.
  • Links to other websites. Pages of the people introduced on our People page, and other sites, are not ours, and some are only in Polish. We cannot vouch for their accessibility.

Preparation of this accessibility statement

  • Date this statement was prepared:
  • Date of the last review of this statement:

This statement is based on an accessibility audit carried out in October 2026 by Stowarzyszenie Centrum Usług Dostępnych (the Accessible Services Center Association). The audit was done by Tomasz Grabowski. It covered eight pages, the home page and the sign-up form among them, against WCAG 2.1 Level AA. The auditor used Chrome and Firefox, the NVDA screen reader and the keyboard alone, and simulated using the site with an eye tracker. The automated tests described below add to it.

Facilities, limitations and other information

Standard we build to

Web Content Accessibility Guidelines (WCAG) 2.2, Level AA (WCAG 2.2). It is newer than WCAG 2.1, which the audit used.

What we check

Automated checks are part of the site’s tests. They cover every page, including the three that open from a link in an e-mail and the “page not found” page. The scan looks at each page as it first loads. It does not go through every state a page can be in, such as the open menu or an error message. The checks catch problems early. They are not a full evaluation, and we do not publish their results here.

  • Contrast. The colors of the design are tested in the light and the dark theme. Body text, secondary text and links must reach at least 7:1. The faintest text, such as the gray suggestion in the scenes on the home page, must reach at least 4.5:1. The edges of controls and the focus ring must reach at least 3:1.
  • Automated scan. Each page, in both languages and in both color themes, is scanned with axe-core, a free automatic accessibility checker, against the rules of WCAG 2.0 to 2.2, Levels A and AA.
  • Keyboard focus. A test presses Tab through every page. It checks that each stop shows a whole focus ring and is not hidden behind the sticky header. Another test checks that focus goes back to the start of the page after an answer on the cookie bar.
  • Zoom, reflow and target size. Reflow means that a page fits a narrow window or a high zoom without sideways scrolling. Tests check that no page scrolls sideways at widths from 320 px up, also with the text size set to 200 % and with a reader’s own line, letter and word spacing. They check that buttons, form controls and menu links are at least 44 px tall, and that every link of the open menu can be reached in a window 320 px wide and 256 px high, which is what 400 % zoom gives on a 1280 by 1024 screen. They do not check every state inside a component.

What we have not checked yet

  • Pages the audit did not cover, such as the privacy policy, the waitlist terms, the press page and the pages that open from a link in an e-mail.
  • The criteria added in WCAG 2.2, which an audit against WCAG 2.1 does not cover. Our automated tests check some of them.
  • Use with the VoiceOver screen reader.
  • Use with a switch and with voice control.
  • Checking by hand in Windows high contrast mode (forced colors).
  • Use at 400 % zoom and in a very short window, checked by hand.
  • Use in Safari.

What we aim for

These are design targets, not results, until we have measured them and written them down:

  • Text contrast of at least 7:1 where possible (the Level AAA rule for text, WCAG 1.4.6) and never below 4.5:1.
  • Buttons, form controls and links on their own line at least 48 px tall. WCAG 2.5.5 (Level AAA) asks for 44 by 44 px, and the minimum for Level AA is 24 by 24 px (WCAG 2.5.8). Links inside a sentence follow the line height of the text.
  • No fixed time limit on reading or on filling out a form. Two things expire. The link in the confirmation e-mail works for 7 days, so that people who need more time or help have enough of it. The answer of the bot check, which Cloudflare lets expire after a few minutes, is renewed by running the check again before the form is sent. While Cloudflare waits for a click, no time limit of ours runs. Only if the check goes silent does the form stop waiting after a short time, tell you so and keep what you typed.
  • No content that flashes, and animation that follows your system’s “reduce motion” setting.
  • Semantic HTML for headings, lists, forms and buttons, in a logical order, so assistive technology can use them.
  • At high zoom and in a short window, the header wraps instead of being cut off and the open menu scrolls. The menu closes when keyboard focus leaves it.
  • Both languages are marked up, so a screen reader uses the right voice.

About this statement

  • Voluntary. TalkerApp is made by a microenterprise, which the European Accessibility Act (Directive (EU) 2019/882) and the Polish act that implements it exempt from accessibility requirements for services. The act on digital accessibility binds public sector bodies. We publish this statement anyway.
  • Review. We review this statement at least once a year, and whenever the site changes in a way that could affect accessibility.
  • Scope. The website gettalker.app, in Polish and English. Not covered: the TalkerApp program, which will have its own statement at release, and pages on other sites.

The TalkerApp program

The program is not covered by this statement and will have its own at release. For now, as of September 2026, from the program’s own user guide (chapter “Appearance”):

  • Checked automatically: accessibility tests with axe-core (WCAG 2.0 to 2.2 rules, Levels A and AA) cover the main screen, the keyboard overlay, Settings, the Phrases and History panels, Studio and the quick export window, and find no serious or critical errors. Color contrast is checked by tests in the Light, Dark and High contrast themes.
  • Not checked yet: a manual review with screen readers (VoiceOver on macOS, NVDA on Windows); manual tests with Windows contrast themes and with hardware such as switches and eye tracking.
  • Known limitation: in the Mini size of the overlay, keys are smaller than 44 px by design. From the Small size up, they are at least 44 px.

Keyboard shortcuts

The site adds no keyboard shortcuts of its own. The standard shortcuts of your browser and system work. In the “TalkerApp at work” scenes on the home page, the Esc key stops playback.

Feedback and contact information

You can report any problem with the digital accessibility of this website to Łukasz Czerwiński, by e-mail at hello@gettalker.app or by text message to +48 693 701 607. This number takes text messages only.

Say which page, what you wanted to do, and what device and assistive technology you use. A plain message is enough. There is no form to fill out and no format to follow, and a message written in whatever way suits you is welcome. We handle an accessibility problem as a bug, not as a feature request.

Everyone has the right to request that this website, or any part of it, be made accessible. When you make such a request, give:

  • your name,
  • how to contact you (for example a phone number or an e-mail address),
  • the exact address of the page with the content or element that is not accessible,
  • what the problem is, and which way of solving it would suit you best.

We answer as soon as we can, within 7 working days of receiving your request, and tell you what we will do and when. If that is too short for us, we tell you so and give you a new date by which we will fix the problem or give you the information in another way. That new date is no more than 2 months away. If we cannot make the page or content accessible, we offer you another way to get it.

Handling of requests and complaints about accessibility

If we refuse the accessibility you asked for, and you do not agree with the refusal, you have the right to complain. You can also complain if you do not agree to the other way of access we offered you in answer to your request.

Send your complaint by e-mail, text message or post to the owner of OneFinger:

  • Łukasz Czerwiński, owner of OneFinger,
  • address: ul. Puchacza 13/1, 20-323 Lublin, Poland,
  • e-mail: hello@gettalker.app,
  • text message: +48 693 701 607.

The act on digital accessibility does not cover private companies, so we follow this procedure voluntarily, and it is not an administrative proceeding. You can also tell the Polish Commissioner for Human Rights (Rzecznik Praw Obywatelskich) about it and ask them to step in.

Other information

Architectural accessibility

OneFinger does not serve customers at its registered office (ul. Puchacza 13/1, 20-323 Lublin, Poland) and does not receive visitors there, so we do not describe the accessibility of the building. We handle everything remotely, by e-mail and text message.

Communication and information accessibility

We do not provide a Polish Sign Language (PJM) interpreter, online or in person. You can reach us in writing, by e-mail or text message. A message written in whatever way suits you is welcome.

Questions about this page, or something here that is hard to use? Write to us.

hello@gettalker.app