A verification flow should be understandable and operable.

Measures included

• Semantic headings, landmarks, labels, lists, and tables.
• A skip link on every main page and visible keyboard focus styles.
• Plain-language status messages announced through an accessible live region.
• Text alternatives for meaningful images and empty alternatives for repeated decorative marks.
• Responsive layouts that support narrow screens and browser zoom.
• Warm colors selected for readable contrast, plus stronger contrast when the browser requests it.
• Animation that stops or becomes static when reduced motion is enabled.
• No important instruction communicated by color alone.

Input and device support

Links, buttons, and forms work with keyboard focus, touch, mouse, pen, and browser-provided spatial pointers. Console and TV browsers with the Gamepad API can move focus with a directional pad or stick and activate the focused control with the primary button. Core content and verification remain available when gamepad support or background animation is unavailable.

Third-party security check

The verification flow uses Cloudflare Turnstile. Its accessibility and availability are partly controlled by Cloudflare. If the security check cannot be completed with assistive technology, contact an administrator of the Discord server where verification began and explain which step is blocking access.

Known limitations

Accessibility can vary by browser, assistive technology, Discord client, and third-party service. The operator should review reported issues and prioritize anything that blocks verification or access to the official documents.

Feedback and accommodation

Report a problem through the official support method shown by Jambot or to an administrator of the participating Discord server. Include the page, the step that failed, your browser or assistive technology if you are comfortable sharing it, and the result you expected. Do not include passwords, tokens, or active verification links.