Accessibility

Our commitment

We are committed to making lingaga accessible to as many people as possible, including people who use screen readers, keyboard navigation, larger text, reduced motion, high contrast settings, or other assistive technologies.

Standards we aim for

Our goal is to meet or exceed the Web Content Accessibility Guidelines (WCAG) 2.1 AA where they apply to the lingaga website and app experience.

• Perceivable: Content should be readable, structured, and available to assistive technologies.
• Operable: Navigation and controls should work with keyboard and touch input.
• Understandable: Pages, forms, and settings should use clear language and predictable behavior.
• Robust: Markup and native controls should work across modern browsers, devices, and assistive tools.

What we are doing

• Using semantic HTML on public pages so headings, links, forms, and sections are understandable.
• Keeping strong color contrast and readable type for longer policy and help content.
• Providing visible keyboard focus states for links, summaries, and controls.
• Using labeled form fields and live status text for the early-access form.
• Building the iOS app with SwiftUI accessibility labels, hints, headings, and native controls.
• Testing responsive layouts so text does not overlap or require horizontal scrolling on small screens.

Ongoing improvement

Accessibility is not a one-time checklist. As lingaga grows, we will keep reviewing new screens, language flows, and account features for accessibility issues and will use feedback to improve them.

Contact

If you encounter an accessibility barrier in lingaga, or if something makes language maintenance harder than it should be, please let us know.