Mulyra aims to conform to Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. We measure conformance against the success criteria published by the W3C Web Accessibility Initiative. Current status: partially conformant. Most of the product passes our automated and manual audits, but newer screens added during Phase 3 (cookie consent, data-subject request forms, the legal takedown form) have not yet completed a full re-audit. We track outstanding items in our internal backlog and prioritise them alongside other engineering work.

• Semantic HTML and React Native accessibility roles on every interactive element so screen readers announce purpose, not just label. • Keyboard-only navigation paths through every primary flow (signup, search, save, apply, contribute salary). • Visible focus indicators, with contrast tested against WCAG 1.4.11 (non-text contrast ≥ 3:1). • Text contrast tested against WCAG 1.4.3 (≥ 4.5:1 normal; ≥ 3:1 large). • Dynamic type support — the app respects OS-level text-size preferences on iOS, Android, and the web. • Forms label every input and surface error text inline (not via colour alone). • Animations honour the OS-level "reduce motion" setting. • Automated axe-core audit run on every merged change (Phase-1 K bucket).

We are openly tracking the following gaps: • Phase-3 cookie consent banner and DSR submission form have not yet completed a manual screen-reader walkthrough (re-audit scheduled — tracked internally as T-3.8.3). • A small number of charts on the salary-trends screen lack a text-table fallback. The numeric values are readable on tap; the chart-as-image alternative is in progress. • PDF resume uploads do not have an accessible preview — we expose the parsed text instead, and the file picker is fully keyboard navigable. If you hit a barrier that is not on this list, please tell us using the contact methods below.

Email [email protected] with as much detail as you can share — the page or screen, the assistive technology you were using (e.g., VoiceOver on iOS 17, NVDA on Windows 11, TalkBack on Android 14), and what you expected to happen. Screenshots or screen recordings help, but are never required. Response SLA: we aim to acknowledge every accessibility report within 5 business days and to share an initial fix plan within 15 business days. Some issues will take longer to resolve — we will keep you updated.

Conformance is evaluated through a combination of: • Automated testing — axe-core on every PR + a quarterly Lighthouse sweep. • Manual testing — keyboard-only walkthroughs and screen-reader spot-checks (VoiceOver on macOS / iOS, NVDA on Windows, TalkBack on Android) before each release. • User-reported feedback via the email above. The Web Accessibility Initiative's WCAG 2.1 reference is our authoritative source for success-criterion definitions.

Mulyra is designed to be compatible with the latest versions of: • Mobile: iOS VoiceOver, Android TalkBack, Voice Control (iOS), Voice Access (Android), Switch Control (iOS), Select to Speak (Android). • Desktop web: NVDA + Firefox, JAWS + Chrome, VoiceOver + Safari, Narrator + Edge. • Browsers: two most recent major versions of Chrome, Firefox, Safari, Edge. Older or non-mainstream assistive technologies may work but are not actively tested. If you rely on one and hit problems, please report it.

This statement is provided in good faith. It does not constitute a warranty of accessibility, nor a waiver of any right or remedy available under applicable disability-accommodation laws (including but not limited to the Americans with Disabilities Act, Section 508 of the Rehabilitation Act, and the European Accessibility Act). For ADA / Section 508 / EAA specific concerns, contact [email protected].