Accessibility

How myEmotes approaches accessibility today, where we are still improving, and how you can report barriers.

myEmotes is developed with the goal of keeping core discovery, browsing, and account flows as accessible as reasonably possible across desktop and mobile devices. Accessibility work is ongoing, and this statement describes our current approach rather than claiming full compliance with every possible scenario.

Current Focus

  • Clear page structure with headings and consistent section layouts.
  • Keyboard-accessible navigation for core browsing and dialog interactions where technically feasible.
  • Responsive layouts for desktop, tablet, and mobile viewports.
  • Readable color contrast and scalable typography across the public frontend.

Need Help?

If you encounter an accessibility barrier, contact us at [email protected].

Please include the affected page, device or browser, assistive technology if relevant, and a short description of the issue.

What We Aim To Support

We aim to keep the most important public flows usable with keyboard navigation, modern browsers, responsive zoom levels, and common assistive technologies. This includes discovering emotes, opening detail dialogs, reading legal pages, and navigating creator or category pages.

We also try to avoid unnecessary visual complexity and maintain consistent interaction patterns so that repeated actions behave predictably across the site.

Known Limitations

  • Some interactive areas, especially newer UI components, may still need refinement for screen readers or advanced keyboard-only workflows.
  • Media-heavy interfaces can occasionally be more demanding on small screens or older devices.
  • Accessibility coverage in the private admin area may differ from the public frontend and is not yet optimized to the same standard.

Feedback And Continuous Improvement

Accessibility issues are reviewed as part of ongoing product and frontend work. Where a barrier materially affects access to a core function, we treat that as a product quality issue rather than a cosmetic detail.

Reports that include the exact page URL, expected behavior, actual behavior, and screenshots or recordings help us resolve issues much faster.

If you need support using a specific public page or workflow, send the link and a short description to [email protected].