You should be able to read Ptichi without using a mouse or playing audio. The site is built around ordinary headings, links, buttons and text, with visible keyboard focus and a reduced-motion setting supplied by your device or browser.
Product
Reading and practice should be reachable
The accessibility approach of the Ptichi website, its current limits and how to report a barrier.
How to get around
Use Tab and Shift+Tab to move through links and controls. Homepage method tabs support arrow-key navigation; standard buttons work with Enter or Space. Browser zoom remains available.
Articles contain their exercise instructions in text. Illustrations have alternative text when they carry meaning; decorative images should not interrupt reading. Tables use headings so their relationships remain understandable.
Audio has a real limit
Demo audio is optional and labelled. The website does not turn on your microphone. Reading the explanation does not require hearing the sample.
The speech-practice method itself includes listening and comparing recordings. Text instructions do not make that experience equivalent for every reader, including people who cannot hear the relevant difference. We have not established an equivalent non-audio learning path, and we do not claim one.
What has not been certified
This is a description of the current approach, not a claim of complete WCAG conformance or compatibility with every assistive-technology combination. Keyboard and responsive checks do not replace direct testing with disabled users or a comprehensive accessibility audit. The desktop app needs its own assessment.
Report a barrier
Use the public contact route. The page address, browser, assistive technology if relevant, and the action you could not complete are enough to start. You do not need to disclose a diagnosis or send a voice recording. The current GitHub route requires an account; we recognise that as a limitation of our support access.
Reviewed: