Accessibility statement

A jobs platform that fails people with disabilities is a jobs platform that fails. We treat accessibility as a core product requirement, not an afterthought, and hold every change to these invariants:

• Every interactive element has an accessible name (visible text, aria-label, or aria-labelledby).
• Keyboard navigation works for every flow — no mouse-only interactions.
• Body-text contrast ratio ≥ 4.5:1; large-text ratio ≥ 3:1.
• Focus is visible on every interactive element; outline: none is never used without a focus-visible replacement.
• Images have alt attributes (empty for purely decorative).
• Forms have labels, errors are announced, dialogs trap focus and restore on close.

These rules live in our Development Checklist §2.5 and are checked before every change.

Target: WCAG 2.1 Level AA (the same standard that most national accessibility laws — ADA in the US, EAA in Europe, RPwD Act in India — converge on).

Current status: Partially conformant. Core flows (sign-in, job search, job detail, apply, saved alerts, privacy settings) have been walked against the checklist. Older admin and recruiter surfaces have not yet been audited end-to-end and likely contain issues.

We commit to a full audit by Q4 2026 and to shipping the remediations that audit surfaces. Meanwhile, we welcome reports of specific problems — see §4.

We're not hiding behind vague aspirations. The following are known problems we have not yet fixed:

• Some admin dashboards lack a full keyboard-only walk. Admins can reach every primary action by keyboard but tab order in nested dropdowns isn't optimal.
• Salary-range sliders are pointer-only. A numeric-input fallback is queued; for now, use the preset bands instead.
• Recruiter Kanban board drag-and-drop is mouse-only. Keyboard equivalents (move to next stage / previous stage) are on the roadmap.
• Some icon-only buttons on the employer-side tooling may be missing aria-label. Known debt; being audited as part of the Q4 sweep.
• Automated testing coverage is incomplete. We rely on manual checks and plan to integrate axe-core into CI.

If something else bothers you, please tell us (§4). We'd rather fix a real issue than argue about whether it's technically a WCAG failure.

Email accessibility@masterjobs.com with:

• What you were trying to do.
• What broke (screen reader stuck, keyboard trap, unreadable contrast, etc.).
• Assistive technology you were using (screen reader + browser + OS).
• A link or screenshot, if you can.

We aim to acknowledge reports within 3 business days and share a remediation plan within 10 business days for confirmed issues.

We test the platform with:

• Screen readers — NVDA (Firefox/Chrome on Windows), VoiceOver (Safari on macOS and iOS), TalkBack (Chrome on Android).
• Keyboard only — standard Tab / Shift-Tab / Enter / Space / Escape.
• Zoom — up to 200% without loss of function.
• Reduced motion — we respect prefers-reduced-motion.

Supported browsers: Chrome/Edge, Firefox, Safari — current and prior major version.

• Privacy Policy
• Terms of Service
• General contact