Teletog is a place to talk about TV shows without spoilers, and conversation belongs to everyone. We are committed to making Teletog usable by blind and low-vision users and by people using assistive technology, as a core design requirement rather than an afterthought.
Teletog targets WCAG 2.1 Level AA wherever technically feasible, implemented through the native accessibility services of each platform (TalkBack on Android, VoiceOver on iOS).
Teletog is live on Google Play and on the App Store, where iOS 1.0.0 was released on September 8, 2026. Our Android accessibility work is described below. On iPhone we have started reading our screens back through Apple's own accessibility interface, which reports the exact words VoiceOver speaks and the role and state of every control. That work has covered some screens and not yet the whole app, and exactly what it does and does not cover is described under Known limitations. Accessibility acceptance criteria are part of our engineering requirements. Every release, with no exceptions, runs a set of automated accessibility checks that fail the build: icon contrast, body text that is too low-contrast to read, touch targets below the minimum size, and controls that announce themselves as buttons without being activatable by a screen reader. A manual review on a physical device is a separate thing, it is slower, and it does not run before every release. Each release statement below says which of the two it received, because those are not the same assurance and we would rather you knew which one you have. On Android, we verified the app's accessibility tree on a physical device on August 5, 2026, walking the core tasks and confirming that controls are labeled, that focus order is sensible, and that a locked episode announces its locked state and how to unlock it without revealing anything about the episode. A statement update accompanies each public release.
Version 1.5.9, released September 20, 2026 (Android; also shipped as iOS 1.0.2 on September 22). Reviewed before release by people who did not write the code. The automated checks listed above all passed. The new surfaces in this release are the options menu on a show's page and a confirmation step before a show is removed. Both were read back through the accessibility tree: every item is a labeled node with the right role, each one can be activated by a screen reader, and every target clears the minimum size. Text contrast was measured on all four themes and the lowest value found was 5.09 to 1, above the 4.5 to 1 this page commits to.
One real defect was found and fixed before release, and it is the kind this page exists to report. Removing a show clears your progress and re-locks every episode room you had opened, so the app asks you to confirm first. That confirmation was only on the visible button. The same action offered to screen readers went straight through, so someone using TalkBack or VoiceOver could lose all of their progress in a single step with nothing asked. Both paths now go through the same confirmation. The test that covers it was part of the problem, because it only checked that the screen reader's action existed rather than performing it, so it passed just as happily before the fix as after. It now performs the action.
What this pass did not include: we did not drive TalkBack or VoiceOver by hand on a phone for this release. We read the accessibility tree and dispatched the screen reader's own actions through it, which is the entry point the phone uses, but reading the tree is not the same as listening to it. That pass is owed and we will say so here when it has been done.
Version 1.5.8, released September 12, 2026 (Android; also shipped as iOS 1.0.1 on September 14). Reviewed before release by someone who did not write the code. This is the first release we have checked on a physical device of each kind in the same pass. It brings notifications to iPhone, so the notification settings screen is new there, and that screen is what this review covered. On Android, on a Moto running the build that went to Google Play, we read the accessibility tree that TalkBack speaks from: every control is a labeled node with the right role and state, the section headings are marked as headings, the reading order follows the page, no state is carried by color alone, every target clears the minimum size, and the layout holds at twice the default text size with nothing clipped or overlapping. On iPhone we read the same screen through Apple's accessibility interface, which returns the exact phrases VoiceOver announces along with each control's role, state and place in the reading order. The labels, the order and the states match the Android tree element for element, and Apple's automated accessibility audit on that screen raised nothing about descriptions, contrast, touch regions, clipped text, control traits or text sizing. One defect was found and fixed before release: after you granted notification permission in the system settings and came back to the app, the screen kept telling you notifications were off until you left it and returned. It now rechecks when you come back, and it announces the change only when it moves into the blocked direction, so nothing interrupts you for good news. What this pass did not cover is described under Known limitations.
Version 1.5.7, released September 7, 2026 (Android). Automated checks only. This was a hardening release whose changes are almost entirely invisible, and the automated accessibility checks listed above all passed. The manual review on a physical device was not run before this release, so nothing new in 1.5.7 was read back by hand with a screen reader before it shipped. That pass is still owed and we will say so here when it has been done. The App Store version is built from the 1.5.6 code below, so it is not affected by this gap.
Version 1.5.6, released September 4, 2026 (Android; also shipped as iOS 1.0.0 on September 8). Reviewed before release by someone who did not write the code. It carried the largest batch of accessibility fixes we have shipped. Thirty-three controls announced themselves as buttons but could not actually be activated by a screen reader; each one now carries its action on the node the reader lands on, and an automated check keeps that shape from regressing. On the Daytime theme, the poster card menu and bookmark overlays and the co-watch lobby were painting near-black ink on a near-black backdrop, outlined buttons had no visible edge at all, and the flare emblem could not render on the light palettes; all three are fixed and held by tests in every palette. The "You're first here" empty state now scrolls on a short screen at large text instead of clipping, and the Terms and Privacy links at sign-up are each their own screen-reader stop rather than being folded into the consent checkbox. Reviewed by reading the accessibility tree and the built artifact, not by driving TalkBack gestures by hand; see Known limitations.
Version 1.5.5, released September 1, 2026. The pre-release accessibility review was run by someone who did not write the code. It found one real defect and we fixed it before shipping: a line of body copy on the sign-up screen was rendered in a low-contrast grey that measured between 2.5 and 3.5 to 1 against its background, below the 4.5 to 1 this page commits to. It now uses a color that clears the bar on all four themes. We also added an automated check that fails the build if any text is rendered in that color again, because the check we already had looked at the color palette rather than at how the colors were used, so it could not have caught this. Separately, we read the message composer on a physical Android device at double the default text size and confirmed it does not clip or overlap.
On iPhone. On September 12, 2026 we read the notification settings screen back on a physical iPhone through Apple's own accessibility interface, which returns the exact phrases VoiceOver announces along with each control's role, state and position in the reading order. Every control announced its name, its role and its value, in the order you would reach them, and Apple's automated accessibility audit on that screen raised nothing about descriptions, contrast, touch regions, clipped text, control traits or text sizing. Three honest limits on that. It is one screen, not the whole app, and we will say here as more of the app is covered. It is not the same thing as a person driving VoiceOver by gesture. And Apple deliberately prevents automated tools from activating controls in a store-signed build, so on iPhone the act of activating a control is confirmed by the shared code path and by the Android device rather than on the iPhone itself.
Text size and motion on iPhone. The largest accessibility text sizes and the Reduce Motion setting have not been exercised on an iPhone. Our text scaling is one piece of code shared by both platforms and it holds on Android at twice the default text size, which is beyond what iOS reaches before its accessibility sizes begin, but the iOS text engine at those largest sizes is not something we have measured. We would rather tell you that than imply a check we did not run.
On Android. Our verification reads the accessibility tree that TalkBack speaks from, rather than driving TalkBack by hand, because injected gestures bypass its touch exploration on our test device. Gesture-level behavior, such as swipe navigation and double-tap activation, is therefore confirmed by structure rather than by a full manual run.
Show artwork is licensed from third-party sources and may occasionally lack useful descriptions beyond title and year. We are evaluating richer description support as the product matures.
If you encounter an accessibility barrier in Teletog, whether it's something a screen reader mishandles, text that won't scale, or a control you can't reach, we want to know. Accessibility reports go to the front of our queue.
Accessibility contact
G&Co. Studios
info@gandcostudios.com, subject line "Teletog accessibility"