Accessibility Statement

Guillaume & Co Studios · Published July 3, 2026 · Reviewed at every app release

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.

Our standard

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

What we build for

• Full screen-reader support: every core task, from finding a show to marking an episode watched, joining its discussion, posting, reporting, and blocking, is designed and tested to be completable with a screen reader alone.
• Meaningful descriptions on all artwork (show title and year, never "image").
• Locked episodes announce both their state and how to unlock them.
• Live discussions announce new messages politely, without stealing focus.
• Moderation controls (report, block) exposed as accessibility actions, not hidden behind long-press gestures.
• Text scaling to 200% without loss of content, high-contrast color palette throughout, and no information conveyed by color alone.
• Reduced-motion preferences honored across all animations.

Current status

Teletog is in active development ahead of public launch. Accessibility acceptance criteria are part of our engineering requirements, screen-reader runs are part of every milestone, and our beta research program includes screen-reader users in every testing round. iOS/VoiceOver support ships with the iOS version of the app. A statement update with detailed conformance status accompanies each public release.

Known limitations

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.

Feedback

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.