Usability
This website/application is currently in development.
We are actively working toward full accessibility and aim to conform with Web Content Accessibility Guidelines (WCAG) 2.2 Level AA (the current international standard; alternatively WCAG 2.1 Level AA if your jurisdiction requires it). However, because fun.app is under active development:
Not all features, pages, or content may yet meet WCAG AA standards.
Some areas may contain temporary accessibility barriers (e.g., incomplete keyboard navigation, missing alternative text, insufficient color contrast, uncaptioned media, or compatibility issues with certain assistive technologies).
Features in progress or recently added might not have undergone full accessibility testing.
We are committed to inclusive design and are taking the following steps:
Incorporating accessibility best practices (semantic HTML, ARIA where needed, keyboard support, etc.) from the start where possible.
Conducting ongoing manual and automated testing as development progresses.
Prioritizing remediation of identified issues in upcoming releases.
Known Limitations (as of January 2026):
Certain interactive elements (e.g., dynamic forms or modals) may not be fully keyboard-accessible yet.
Some third-party embedded content (videos, maps) may lacks captions or descriptions — we are coordinating with providers.
Mobile/responsive views are still being optimized for screen readers.
We have not yet completed a comprehensive accessibility audit; barriers may exist that we are not yet aware of.
Feedback Is Essential Your input helps us improve faster. If you encounter any accessibility or usability barriers while using this site/app, please let us know by emailing us at info@fun.app - Please describe the issue, the page/feature affected, the browser/assistive technology used, and any suggested fixes. Do not expect a response.
Browser & Assistive Technology Compatibility This beta version is best experienced with recent versions of Chrome. We test with common screen readers (e.g., NVDA, JAWS, VoiceOver) where feasible, but full compatibility is not guaranteed during development.
Date of This Notice
Last updated: January 26, 2026.
We will update this statement regularly as features are completed and accessibility improves.
Thank you for your patience and understanding while we build a more inclusive experience.