Access should work for more people.

Our engineering target is WCAG 2.2 Level AA across company-controlled public routes. This statement reports the current scope, assessment approach, limitations, and assistance route.

Navigation and display controls

Keyboard-visible skip links provide direct access to the main content, site navigation, and accessibility options. The persistent Accessibility button provides landmark shortcuts, text-size and text-spacing controls, stronger contrast, reduced decorative motion, and a reset action. It is an optional preference aid, not a substitute for accessible page code, browser settings, or assistive technology. Display choices are stored only in your browser and do not load a third-party accessibility service.

WCAG 2.2 Level AA target

We use the W3C WCAG 2.2 Level A and Level AA success criteria as the current technical baseline. WCAG organizes accessibility under four principles: perceivable, operable, understandable, and robust. The site is designed for semantic landmarks and headings, keyboard operation, visible and unobscured focus, browser zoom, 320 CSS-pixel reflow, descriptive image alternatives, readable contrast, reduced motion, and controls that meet the WCAG 2.2 minimum target-size criterion.

Conformance status

WCAG defines full conformance only when every applicable requirement is satisfied across each complete page and supported variation. MtnSkyAlgo is not yet claiming full conformance. WCAG 2.2 Level AA remains the active target while manual assistive-technology validation, third-party review, and independent evaluation are completed. A passing automated scan is not certification.

Assessment approach

Three established tools are installed in the project: eslint-plugin-jsx-a11y checks JSX while code is written; Deque axe-core scans hydrated public routes in Playwright; and the IBM Equal Access Accessibility Checker provides an independent ruleset. The release audit reports every detected violation mapped to the target WCAG rules instead of filtering results by severity or accepting a broad saved exception baseline.

We also review keyboard focus order, skip links and landmarks, enlarged text and 320 CSS-pixel reflow, WCAG text-spacing overrides, reduced-motion behavior, heading structure, image alternatives, target sizing, critical purchase and support paths, and active states of navigation, FAQ disclosures, the review rail, accessibility preferences, and privacy controls. Preference combinations, browser-storage persistence, and reset behavior are included in the interaction suite. W3C evaluation guidance is explicit that no automated tool can determine conformance; knowledgeable human evaluation, assistive-technology testing, and ideally evaluation involving people with disabilities remain necessary.

Tested environments

The internal release matrix exercises current Chromium desktop and mobile-sized viewports with keyboard and pointer input, plus automated Firefox and WebKit-compatible browser runs where supported by the test environment. Windows Narrator testing is planned and tracked separately but has not yet been completed. Playwright WebKit on Windows is not native Safari, and native Safari with VoiceOver remains an external validation requirement.

Regional requirements

Accessibility law varies by organization, service, location, and customer. In the United States, the US Department of Justice web accessibility guidance explains how the ADA applies to web-based goods and services, while Section 508 separately governs US federal agencies. In the European Union, the European Accessibility Act includes e-commerce services and applies through national implementing laws, with defined exemptions and proportionality provisions.

Other examples include the United Kingdom, where official guidance identifies WCAG 2.2 AA for public-sector sites and reasonable-adjustment duties for service providers; Ontario, where covered public organizations and businesses or non-profits with at least 50 employees must meet specified WCAG 2.0 AA criteria; and Australia, where the Australian Human Rights Commission connects accessible digital goods and services with the Disability Discrimination Act and WCAG. These references explain regional context; they do not establish that every rule applies to this business or make this statement legal advice.

Third-party content and services

Whop checkout and account management, Discord, TradingView, video platforms, and other linked services are operated by third parties. Their accessibility may differ from this website. The homepage’s read-only community panel uses Discord’s public widget data, while joining the server and viewing role-based channels takes place on Discord. No checker, plug-in, widget, or overlay can guarantee global legal compliance or eliminate every barrier.

Known limitations

Native Safari and VoiceOver validation, evaluation involving users with disabilities, and current accessibility conformance reports from critical third-party vendors remain outside the completed company-controlled automated checks. Membership videos and livestreams must be evaluated in their hosting platforms for captions, transcripts, audio description when applicable, and player operability.

Feedback and assistance

Contact accessibility support or email [email protected] with the page URL, the task you were trying to complete, and a description of the barrier. Include your browser or assistive technology only if you are comfortable doing so. Do not include passwords, payment credentials, medical records, or other sensitive information.

This page describes the current public-site implementation and audit scope; it is not a certification or guarantee that every person, device, assistive technology, third-party service, or legal requirement is covered. Last reviewed: .