What works, what doesn’t, and how to tell us.

01

Our commitment

We want our website, our mobile apps and our learning platform to work for people with disabilities.

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We treat accessibility as ongoing engineering work, not a one-time project.

A language-learning tool that someone can’t use isn’t a language-learning tool. If a barrier is stopping you, we want to know about it, and we want to fix it.

02

What we’ve done

Accessibility work already live:

• Live classroom.Microphone, camera, chat and reactions have labeled controls. Screen readers announce connection status and save states.
• Legal, FAQ and accessibility pages.Skip links, keyboard-operable accordions with correct ARIA state, visible focus, reduced-motion support and correct language tagging.
• Public challenge pages.Native buttons with accessible names, and descriptive alt text on character images.
• Mobile app.Screen headers announce as headings, and VoiceOver treats dialogs as modal. Small controls have larger touch targets. Placeholder text has more contrast, and light-mode status colors now meet 4.5:1 against the cream backgrounds. Native form controls and system alerts follow the phone’s own accessibility settings.
• Age check and AI consent.Both have labels and work with a screen reader.

03

Known limitations

We’d rather be honest about what isn’t fixed yet than claim a level of conformance we haven’t verified. Still incomplete:

• Keyboard and screen-reader gaps on the web.Parts of the student dashboard, teacher dashboard, booking pages and sign-in forms still have gaps. Some controls don’t fully work by keyboard. Screen readers miss some dialogs, and some form fields don’t have their labels attached in code. We’re fixing them in order of how central each flow is.
• Focus and color contrast.Focus styles and contrast are inconsistent across the product. Several accent and secondary text colors fall below the 4.5:1 target and are being re-tuned.
• Mobile app coverage.A minority of app screens carry complete screen-reader labels today. We’re labeling the rest screen by screen. Until that’s finished, we can’t claim WCAG 2.1 AA conformance on iOS or Android.
• Text size and motion in the app.Some app text stops growing before the largest system text sizes. Most animations don’t yet follow the system Reduce Motion setting.
• Testing on real devices.Full VoiceOver and TalkBack walkthroughs on real devices aren’t finished for every flow yet.
• Voice conversations.Live voice calls are audio-first by nature. During a live call, we don’t yet offer a text-only equivalent for people who are deaf or hard of hearing. Text-based practice (drills, flashcards, translation and written conversation) remains fully usable.
• Captions on character videos.Some character introduction videos don’t have captions yet. We’re adding captions across the whole library.

04

How to reach us

If something gets in your way, tell us. Tell us too if you need content in another format, or a reasonable accommodation to use Project Fluency.

Our contact form is the quickest way to reach us. If a form doesn’t work for you, email hello@projectfluency.com with “Accessibility” in the subject line.

We aim to reply within 3 business days. It helps to include:

• The page or screen where it happened (a link or the screen’s name)
• What you were trying to do
• The assistive technology you use (for example VoiceOver on iOS, JAWS or NVDA on Windows, switch control, or keyboard only)
• What you expected to happen, and what happened instead

You can also write to us by post:

05

Alternative formats

If any of our content doesn’t work for you as published, contact us. We’ll give you the same information in a format that suits you.

That includes plain-text versions of our legal documents, large-print PDFs or another reasonable format.

06

Outside services

We use a small number of outside services for core features: voice, payments and analytics. Our Privacy Policy lists them all.

We choose accessible providers with care, but each provider controls the accessibility of what it shows.

If you hit a problem inside one of these, tell us. We’ll either fix it or pass it on to the provider.

07

Review and updates

This page was last reviewed and updated on August 14, 2026.

We review our accessibility at least once a quarter, and after any major release. We date significant updates here.

Feedback is the fastest way for us to find and fix problems. Write any time.