Accessibility (WCAG)
N8 Casino India is committed to inclusive, barrier-free access for every player. We design, build, and test against WCAG 2.2 Level AA and align our practices with India’s RPwD Act (2016) and GIGW guidance. This statement describes our standards, features, known limits, and how to request reasonable accommodations.
Official operator: We are an official, regulated casino brand serving India. Accessibility is part of our compliance and customer-care commitments. 18+ only.
Our commitment and scope
Our goal is for all core user journeys—account creation, KYC/AML verification, deposits, withdrawals, live chat, game browsing, and responsible-gaming tools—to meet WCAG 2.2 Level AA. We apply accessible patterns during design, run automated and manual checks before release, and re-test after significant UI or content changes.
This statement covers our primary website, mobile web, and supported in-app web views. It also describes how we handle third-party components (for example, payment gateways or embedded game providers) and what you can do if you encounter a barrier.
Standards & governance
We base our accessibility program on well-recognized standards and Indian legal frameworks. Our teams receive periodic training, follow an internal accessibility checklist, and track issues in an engineering backlog with SLAs based on severity and user impact.
Summary of what we follow:
- WCAG 2.2 Level AA target across our primary experiences, with awareness of prior versions for backward compatibility.
- RPwD Act (2016) expectations for equal access to ICT content and services in India.
- GIGW principles for accessible government-grade websites used as a reference model for Indian audiences.
- Accessible document formats preference (e.g., OCR-ready PDFs or ePUB) for key policies and forms where feasible.
Review cadence: this page and our controls are reviewed at least annually or upon material changes to standards. Last reviewed: 2 September 2025.
Conformance status
Target level: WCAG 2.2 Level AA.
Methodology: semantic HTML as the baseline; ARIA only when necessary; automated rulesets on each build; manual screen-reader and keyboard testing; periodic external audits; and usability checks with larger text and high-contrast settings.
Status statement (rolling): Core journeys meet or are actively being uplifted to Level AA. Any gaps are tracked with owners and target fix dates.
Snapshot checklist (public summary)
| Area | Example criteria | Our approach |
|---|---|---|
| Non-text alternatives | Text alternatives for meaningful images and icons | Alt text; decorative images hidden from assistive tech |
| Contrast | Readable text and UI elements | AA contrast for text and essential controls; promo media audited |
| Keyboard access | No keyboard traps; logical focus order | Full keyboard navigation with visible focus indicators |
| Focus appearance (2.2) | High-visibility focus ring and clear focus notches | Robust focus styling; consistent order between screens |
| Target size (2.2) | Adequate hit areas on touch | Minimum target sizing on interactive elements |
| Forms & errors | Labels, instructions, error prevention | Clear labels; descriptive errors; accessible validation states |
| Robustness | Assistive tech compatibility | Semantic structures; minimal ARIA; compatibility testing |
Key accessibility features implemented
We continuously enhance usability for people who use screen readers, keyboards, switch controls, magnification, or high-contrast themes. The following features are part of our design system and review checklist:
- Text alternatives for images and icons; meaningful SVGs are labeled, decorative assets are hidden.
- Captions for prerecorded media where provided, and transcripts for important audio content.
- Color-independent cues, AA contrast, and layouts that support 200% zoom without loss of content.
- Keyboard-first navigation, visible focus, and “Skip to main content” entry points.
- No keyboard traps; logical reading and tab order across dialogs, menus, and overlays.
- Touch targets sized to reduce precision requirements; alternatives to dragging gestures where applicable.
- Clear labels, instructions, and error messaging on forms; accessible validation feedback.
- Predictable navigation and headings; consistent landmarks and component behavior.
- Semantic HTML with ARIA used only when necessary to express states and relationships.
- Manageable motion and timers; pause/stop controls for moving or auto-updating content where feasible.
Testing coverage
We test with a representative set of assistive technologies, operating systems, and browsers. Individual experiences may vary by configuration, but this matrix reflects our baseline coverage and helps us detect regressions early.
| Assistive technology / Platform | Browsers | Notes |
|---|---|---|
| NVDA on Windows | Chrome, Edge, Firefox | Primary desktop screen-reader coverage |
| JAWS on Windows | Chrome, Edge | Enterprise and kiosk scenarios |
| VoiceOver on macOS | Safari | Mac accessibility baseline |
| TalkBack on Android | Chrome | Touch and gesture focus, target size checks |
| VoiceOver on iOS | Safari, in-app web views | Mobile web flows including KYC and payments |
| Keyboard-only and switch input | Current and recent major versions | Focus order, traps, and operability checks |
Third-party components
Some experiences—such as embedded game lobbies, anti-fraud modules, analytics dashboards, and payment widgets—are provided by third parties. We request WCAG conformance from vendors, select accessible options where possible, and apply accessible wrappers or fallbacks. Certain constraints (for example, iframes that restrict focus control) may still limit our ability to remediate directly.
Known limitations
Older promotional banners may not meet current contrast targets; these assets are being refreshed. A small number of legacy articles may include images without descriptive text; these are queued for remediation. Some embedded third-party interfaces can temporarily affect keyboard navigation until we ship workarounds or the vendor releases a fix.
Requesting help or accommodations
If you encounter a barrier, need an alternative format, or want help completing a task (including KYC), our support team will respond and provide a practical workaround wherever possible.
- Describe the issue and the page or screen where it occurs, including device, browser, and any assistive technology used.
- If relevant, include the exact steps that lead to the problem and any error messages shown.
- Tell us the outcome you need (for example, larger-print document, manual KYC assistance, or a phone-based walkthrough).
- Contact channels: Live Chat in the help center; Email: accessibility [at] n8casinoin.org; Phone/WhatsApp (messages only): +91-00000-00000.
- We aim to acknowledge within 48–72 hours and provide either a fix, a workaround, or a timeline for remediation.
Continuous improvement
Policy owner: Accessibility Lead, Compliance. Engineering teams are responsible for day-to-day implementation with QA support. Product managers track accessibility acceptance criteria for new work and ensure issues are resolved before launch.
Training and audits: Designers and developers receive periodic training. Automated checks run in CI; manual audits use screen readers, keyboard-only flows, zoomed layouts, and high-contrast simulations. External reviews are commissioned as needed.
Versioning: First published in 2025. Last review: 2 September 2025. Next planned review: within 12 months of the last review or after material standard changes.
Legal note
N8 Casino India operates as an official, regulated brand. Accessibility obligations form part of our broader duties to customers under applicable Indian law and internal policies. Where conflicts arise between aesthetic choices and accessibility, we prioritize accessibility. If something does not work for you, please let us know—we will make it right.