Accessibility statement

Our commitment

We want everyone to 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 know what they want to say but cannot rely on speech or fast typing, so this site has to work for them first.

Standard and status

• Standard we build to: Web Content Accessibility Guidelines (WCAG) 2.2, Level AA (WCAG 2.2).
• Status: we designed the site to meet WCAG 2.2 Level AA. We have not yet finished a full evaluation, so we do not claim that the site conforms. This page says what we check, what we have not checked yet, and what we know is not right yet.

What we check

Automated checks are part of the site’s tests. They cover every page, including the two 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 typing sample, 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.
• 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

• Use with screen readers, such as VoiceOver and NVDA. We have not tested the site with them.
• Use with a switch, with voice control or with eye tracking.
• 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 browsers other than Chromium (the engine behind Chrome and Edge). Our automated tests run in Chromium only.
• A full evaluation by a person against every WCAG 2.2 criterion.

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 in 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.

Known limitations

• The bot check on the sign-up form 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.
• The typing sample on the home page speaks with a voice installed on your device. If your device has no voice for the page language, the sample cannot speak and says so.
• 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.

Feedback and contact

If something on this site is hard or impossible for you to use, please tell us: hello@gettalker.app. Say which page, what you wanted to do, and what device and assistive technology you use. A plain e-mail is enough. There is no form to fill out and no format to follow, and text written with AAC is welcome. We handle an accessibility problem as a bug, not as a feature request. We answer within 7 working days and tell you what we will do and when.

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. We publish this statement anyway.
• Method. We wrote it from the design rules the site is built to and from the automated tests in its code. We have not carried out a full evaluation.
• Date. The date at the top of this page is the day we last changed or reviewed this statement. We review it 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.