Accessibility Statement

1. Standard

• Legal baseline: the website and console are designed to meet Israeli Standard IS 5568, which is based on the Web Content Accessibility Guidelines (WCAG) 2.0 at level AA.
• Our target: WCAG 2.1 level AA. Where practical, we also apply WCAG 2.2 AA success criteria.

2. Accessibility adjustments

• Keyboard navigation: all interactive elements can be reached and operated with the keyboard, with a clearly visible focus indicator. The website includes a "Skip to content" link.
• Semantic structure: meaningful headings, landmarks (main navigation, footer, breadcrumbs), labelled form fields and buttons, and ARIA attributes where native HTML is not enough.
• Charts: the console's statistics charts respond to both the keyboard and the mouse, show tooltips on focus, and always offer a data-table view as a text alternative.
• Colour and contrast: the colour palette is checked for sufficient contrast on dark surfaces. Chart colours are chosen to stay distinguishable for people with colour-vision deficiencies. Information is not conveyed by colour alone.
• Text alternatives: meaningful images have alternative text. Decorative images are hidden from assistive technology.
• Languages and direction: full interfaces in English, Russian and Hebrew. Hebrew pages use right-to-left layout, with correct language and direction attributes.
• Reduced motion: animations and visual effects are reduced or turned off when your operating system requests reduced motion (prefers-reduced-motion).
• Zoom and resizing: pages support browser zoom up to 200% and adapt to small screens without losing content or functions.
• Status messages: notifications ("toasts") and form errors are announced in text.
• Accessibility toolbar (website and console): every page of the website and the console has an accessibility toolbar with these options:
• text size;
• high contrast;
• grayscale;
• highlighted links;
• a readable font;
• stopped animations;
• a big cursor;
• increased text spacing.

The toolbar can be operated with the keyboard. Your settings are saved in your browser only (see the Cookie Policy) and apply on every page until you reset them. The toolbar supplements our accessibility work; it does not replace it. The pages themselves are built to conform to the standard in section 1 without the toolbar, and they also work with your browser's and operating system's accessibility features (zoom, contrast modes, screen readers). In the console the toolbar button sits in the bottom corner on the side where text starts (bottom left in English and Russian, bottom right in Hebrew), and the settings are shared with the website when you use the same browser and domain.

3. Known limitations

• Content inside Discord. The bot works inside Discord, whose apps and interface we do not control. The accessibility of Discord itself is Discord's responsibility.
• Content created by server admins. Messages, embeds, images and panels that server admins write and post through the bot are their responsibility. We encourage admins to write clear text and avoid information conveyed only by images or colour.
• Generated images. Some bot features send images, such as welcome cards, rank and level cards, game profile cards and captcha images. The essential information on a welcome or level card is also sent as text in the same message or embed, for example the greeting or the level reached. Visual captcha is an image by nature. Server admins can choose verification methods without images (a button, rules acceptance or questions), and we recommend doing so where accessibility is needed.
• Third-party components. The PayPal checkout buttons and window are provided by PayPal, and their accessibility is PayPal's responsibility. If you cannot complete a payment, contact us and we will help.
• Flows editor. The visual workflow editor is a canvas designed mainly for a pointer (mouse, touch or trackpad):
• some actions work best by dragging, such as drawing connections between nodes and positioning them freely;
• keyboard shortcuts help: the node palette opens with Tab, and automatic layout arranges the nodes (Shift+L);
• editing is not available on very narrow screens.

If you cannot build a Flow you need, contact us and we will help you set it up. Ready-made Flow templates are also available.

We are continuing to work on these limitations. If something prevents you from using the Service, please tell us (section 5) and we will offer an alternative way to get the same result.

4. Review

This statement was last reviewed and updated on 26 September 2026. That review included keyboard navigation testing and automated accessibility checks (heading structure, text alternatives for images, form labels and contrast) of the website and console.

5. Accessibility contact

If you have a problem using the website or console, need information in an accessible format, or want to suggest an improvement, contact us:

• Email: info@botgg.app

Please include:

• a description of the problem;
• the page address (URL);
• the browser and assistive technology you use, if any;
• how we can reach you.

We will acknowledge your request within 5 business days and try to resolve it or offer an accessible alternative within 30 days. If a fix takes longer, we will tell you when to expect it.