Meeta is a product for disabled people. If the product itself is hard to reach, the whole idea fails — so accessibility is written into the brief, the design review and the release checklist, not added at the end.
1. Our standard
We build to WCAG 2.2 Level AA, and use it as a floor rather than a finish line. Where the web standard doesn't map cleanly onto a phone app, we apply the same intent through Apple's and Google's platform guidance, and we say so here when we do.
We also hold ourselves to a plainer rule: no feature may require hearing, sight, speech, fine motor control or a fast reaction in order to take part.
2. This website
What you can rely on here, today:
- Structure. A skip link, one main landmark, one banner, one contentinfo, ordered headings, and a language declared on every page.
- Keyboard. Every menu, link and the display panel can be used without a mouse. Focus is always visible, and focus order follows reading order.
- Display controls. Three text sizes, a high-contrast mode and a reduced-motion switch, in the header of every page. Your choice is remembered in your browser.
- Motion. Nothing plays automatically. If your system asks for reduced motion, the site honours that on first visit, and the scrolling community strip stops where it is.
- Contrast and colour. Body text meets at least 4.5:1 and large text at least 3:1. No meaning is carried by colour alone; switches also change text and shape.
- Text and zoom. The layout reflows without horizontal scrolling down to a 320 px viewport, and survives 200% text zoom and 400% page zoom.
- Images. Product screenshots carry descriptive alternative text. Decorative art is hidden from screen readers.
- No traps. No time limits, no autoplay with sound, no keyboard traps, no flashing content.
3. The Meeta app
- Screen readers. Every control has a label. VoiceOver on iOS and TalkBack on Android are part of our release check, not a spot test.
- Text first. Posting, messaging, joining an event and check-in all work without sound and without speech. Voice notes and calls are optional extras.
- Type that scales. The app follows the system text size, including the larger accessibility sizes on iOS.
- Motion. Lumi's animations and the feed's transitions respect the system reduce-motion setting.
- Captions and descriptions. Where media plays, captions or a text equivalent are the default, not an add-on.
- Errors that explain. Error messages say what went wrong and what to do, and are announced to assistive technology.
4. How we test
- Automated checks (contrast, names and roles, landmarks) on every build.
- Manual passes with VoiceOver, TalkBack, NVDA and JAWS.
- Keyboard-only runs, 200% and 400% zoom runs, and a high-contrast run.
- Reviews with disabled testers across our five communities before a release is signed off.
5. Known limitations
We would rather list the gaps than claim a clean sheet:
- The product screenshots are stills. They are images of a design prototype, not a live app, and they cannot be interacted with or read on their own. Their alternative text describes what each screen contains.
- Some features described on this site are pre-release. Events, chat and membership are shown as designed in the v1.0.0 prototype. Where shipped behaviour differs, the app is the source of truth.
- Legal pages are drafts. Operator details are still placeholders, and the wording is awaiting counsel review.
- No full audit has been published. We have not yet commissioned a third-party WCAG audit; when we do, the report will be linked here.
6. Compatibility
This site is tested on the current and previous major versions of Safari, Chrome, Firefox and Edge, on desktop and mobile, and with iOS VoiceOver, Android TalkBack, NVDA with Firefox and JAWS with Chrome. It does not support Internet Explorer.
7. Feedback and escalation
If something here blocks you, tell us and it becomes a tracked defect — not an inbox item.
- Email lingxuan.overseas@gmail.com with the page, your device and what happened. Screenshots or a recording help but are not required.
- We acknowledge within 2 business days and aim to fix blocking issues within 10 business days.
- If you are not satisfied with our response, ask for it to be escalated to the product lead — mention "escalate" in your reply.
8. Review
This statement is reviewed at every release and at least twice a year. Next review: May 2027.