Skip to main content
Babbily runs on the web. You can use it in desktop and mobile browsers, including when you add Babbily to the Home Screen on an iPhone or iPad. Some features depend on your browser, device, permissions, selected model, plan, and account state.

Browser, device, and file support

Troubleshoot microphone, upload, pop-up, plugin authorization, and device-specific issues.

Supported environment basics

For the best experience:
  • Use a current version of a modern browser.
  • Enable JavaScript and required browser permissions.
  • Allow cookies for Babbily so it can keep you signed in.
  • Allow pop-ups when connecting apps.
  • Allow microphone access when using voice dictation.
  • Keep your browser zoom, default font size, and operating system display settings at comfortable levels.
  • Refresh Babbily after changing browser permissions, plan state, connected apps, or account settings.

How the layout adapts

Feature dependencies

Built-in accessibility features

  • Visible keyboard focus. A coral focus ring shows which control has keyboard focus.
  • Text that scales. Text grows with your browser’s default font size, not only with zoom.
  • Reduced motion. When your device asks for reduced motion, Babbily simplifies animations, and scrolling score and price tickers become still rows.
  • Pause scrolling tickers. Choose Pause scores on News or Pause prices on Finance to stop a scrolling ticker.
  • High contrast. Babbily supports Windows High Contrast.
  • Touch targets. Touch targets are at least 40px, so controls are easier to tap.
  • Right-to-left layout. In Arabic, menus, tabs, and the image viewer follow right-to-left layout.
  • Translated interface. More of Babbily is translated into English, Spanish, French, German, Chinese, Hindi, Arabic, Portuguese, Russian, and Japanese. To change your language, open your account menu and choose Language.

Accessibility tips

  • Increase your browser’s default font size or zoom if text is too small.
  • Use operating system contrast, motion, and display settings when helpful.
  • Use keyboard navigation where supported by your browser and the active control.
  • Add clear prompt structure when using screen readers, such as numbered tasks or requested headings.
  • Prefer shorter chats or separate threads when a long page becomes difficult to navigate.
If your organization requires a formal accessibility review or specific compliance documentation, contact support with the requirement and timeline.

Report an accessibility issue

When contacting support, include:
  • The page or feature.
  • Browser, device, and operating system.
  • Assistive technology involved, if any.
  • What you expected to happen.
  • What happened instead.
  • A redacted screenshot or short description of the issue.
Do not include passwords, verification codes, private keys, payment details, or sensitive files in the report.
Last modified on October 7, 2026