Accessibility Statement
This website aims to make its materials accessible to as many readers as possible, including people with visual, hearing, motor, cognitive, or reading disabilities and differences. Accessibility is part of how we plan, write, and review our pages, rather than being limited to their visual appearance.
This statement explains our approach, the standards that guide our work, the measures we seek to implement, and how users can report an accessibility barrier. The website is primarily editorial and publishes articles, tables, instructions, and informational materials for readers in Argentina. For this reason, we prioritize clear reading, predictable navigation, and compatibility with assistive technologies.
Accessibility is an ongoing process. Although we continually work to improve the website, a new page, image, or feature may require additional adjustments. If you encounter a difficulty, you can report it through the contact form so that we can review it.
Our Approach to Inclusive Reading
We understand accessibility as an ongoing responsibility rather than a one-time review performed before publication. When creating or updating a page, we aim to ensure that the content can be read, navigated, and understood across different devices, browser settings, and assistive technologies.
Our review process combines automated tools, manual checks, and feedback from readers. Automated tools can detect common issues such as insufficient contrast, images without text alternatives, structural errors, or controls without labels. However, they cannot replace human evaluation: a page may pass an automated test and still be confusing for someone navigating with a keyboard or screen reader.
Our review process may include:
- Automated checks using tools such as Lighthouse and axe DevTools.
- Manual keyboard navigation without using a mouse or touchscreen.
- Basic testing with screen readers such as NVDA, VoiceOver, JAWS, or TalkBack.
- Review of heading hierarchy, links, forms, and visible focus indicators.
- Analysis of comments submitted by readers.
The goal is to identify barriers before publication and prioritize issues that make it difficult to access the main content, tables, contact form, or navigation.
Technical Standards We Follow
The website uses the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, developed by the W3C, as its main reference. These guidelines are a widely used standard for creating web content that is perceivable, operable, understandable, and robust.
WCAG 2.1 AA is a design and review objective, not a guarantee of complete compliance with every success criterion at all times. Accessibility may be affected by browser changes, device differences, technical updates, or third-party content.
We consult the W3C Web Accessibility Initiative guidelines when evaluating contrast, keyboard navigation, alternative text, semantic structure, and other essential elements.
Visual Accessibility
The interface is designed to accommodate different visual needs, ranging from mildly reduced visual acuity to the use of screen magnifiers or screen readers. We prioritize a clean structure, readable text, sufficient contrast, and the ability to enlarge content without losing access to important functions.
Informative images, such as diagrams, screenshots, and infographics, should include alternative text that communicates their essential information. When an image is decorative and adds no meaningful content, it may use an empty alt="" attribute so that screen readers ignore it. This prevents file names or irrelevant descriptions from being announced. The W3C recommends making this distinction.
Complex images may be accompanied by a nearby written explanation. For example, if a table is presented as an image, the important information should also be available as text or as an HTML table. A screenshot should not replace an explanation; it should serve as visual support.
| Visual element | Accessibility measure | Objective |
|---|---|---|
| Informative images | Descriptive alternative text. | Communicate the content to screen-reader users. |
| Decorative images | alt="" or equivalent markup. | Avoid unnecessary auditory clutter. |
| Complex charts | Summary or description placed near the image. | Explain key data and conclusions. |
| Links | Visual distinction in addition to color. | Make links easier to identify. |
| Tables | Clear headings and HTML structure. | Allow information to be read by rows and columns. |
Font Sizes and Contrast
Typography uses relative units such as rem and em to better respect browser and operating-system preferences. You can enlarge the page using your browser controls, for example by pressing Ctrl and + or Cmd and +, without requiring a separate version of the website.
Color combinations are reviewed with reference to WCAG contrast levels. As a general guideline, standard-sized text should achieve a minimum contrast ratio of 4.5:1, while large text should achieve a minimum ratio of 3:1 against its background. This criterion is defined by WCAG 2.1 AA.
Links should not rely exclusively on color. They may also use underlining, different font weights, icons, or visible state changes. This helps people with color-vision deficiencies, low vision, or screens with limited color quality.
Screen-Reader Compatibility
We aim to use semantic HTML so that the page structure can be understood by screen readers. This includes hierarchical headings, genuine lists, tables with headers, clearly defined page regions, and buttons with identifiable names.
The heading structure follows a logical order: one h1 for the main subject, followed by h2 and h3 subheadings to organize the information. Lists are created as actual lists rather than paragraphs with visually inserted dashes. Tables are used to compare data and not to control the position of elements on the screen.
Buttons, links, and form inputs should have clear labels. When a visible label is insufficient, accessible descriptions, including ARIA labels, may be used, provided that they add meaningful information and do not unnecessarily duplicate content that is already announced.
Cognitive and Reading Comfort
Accessibility also means making content easier to understand. Some readers may have dyslexia, ADHD, concentration difficulties, fatigue, memory-related difficulties, or may be reading Spanish as a second language. Clear pages benefit all of these users, as well as people accessing the website from a mobile phone, with limited time, or through an unstable internet connection.
We aim to use short paragraphs, descriptive subheadings, lists where they help organize information, and direct language. We avoid unnecessary animations, flashing content, automatic playback, and excessively dense text. When a technical term appears, we try to explain it the first time it is used.
For example:
- Wagering: a betting requirement connected to a bonus.
- RTP: the theoretical percentage returned to players over the long term.
- Cash out: an option that allows a bet to be closed before the final result.
- KYC: verification of a customer’s identity and other personal information.
- EDD: enhanced due diligence applied to higher-risk profiles or situations.
Long articles, particularly those exceeding 2,000 words, may include a brief summary of the main points at the beginning. This allows readers to quickly determine whether the article answers their question before reading the complete content.
Keyboard and Motor Accessibility
Not everyone can use a mouse, touchscreen, or precise gestures. Some people navigate exclusively with a keyboard, switches, voice commands, head pointers, eye-tracking devices, or adapted assistive technologies.
For this reason, we aim to make the website’s essential functions usable without a mouse. Keyboard focus should remain visible: when moving through links, buttons, fields, or controls, users need to identify which element is currently active. We do not remove focus styles solely for visual-design purposes.
Accessible navigation should follow a logical order. When the Tab key is pressed, focus should move according to the visual and structural order of the page. It should not jump to hidden elements, become trapped inside a component, or move unpredictably.
Motor-accessibility measures include:
- Visible keyboard focus on links, buttons, and form fields.
- A navigation order consistent with the page structure.
- Sufficient spacing between buttons and controls to reduce accidental activation.
- Forms with clear labels and understandable error messages.
- No actions that require holding down a key or performing precise movements.
Using the Entire Website Without a Mouse
Functional elements, including menus, links, the contact form, and interactive controls, should be accessible by keyboard. Common keys include Tab to move forward, Shift + Tab to move backward, Enter or the Space bar to activate controls, and arrow keys when required by a particular component.
The focus order is intended to follow the visual sequence of the page. The website may also include links that allow users to skip repeated navigation blocks and move directly to the main content. These skip links reduce the number of elements that a person using a keyboard or screen reader must navigate through. The W3C explains their usefulness.
Keyboard compatibility is reviewed particularly carefully on pages containing menus, wide tables, forms, and expandable elements. If you encounter a control that cannot be opened, closed, or used without a mouse, please report it through the contact form.
Audio and Multimedia
The website prioritizes written content so that essential information does not depend on listening to audio or watching video. We aim to avoid automatically playing audio, pop-up videos with sound, and elements that unexpectedly interrupt reading or interfere with a screen reader.
This approach benefits people with hearing disabilities, those browsing in shared spaces, users with limited internet connections, and people who prefer to read at their own pace. It also helps reduce mobile-data consumption.
If videos are published in the future, we will seek to provide:
- Synchronized captions for spoken content.
- A written transcript containing the relevant information.
- Descriptions of important visual elements when necessary.
- Visible controls for playback, pause, and volume.
- No automatic playback with sound.
Third-party multimedia resources may have their own limitations. When we cannot control their accessibility, we will seek to offer a written alternative or a summary of the essential information.
Mobile Accessibility in Argentina
A significant part of the audience accesses the website through mobile phones and may use 4G or 5G networks with varying coverage depending on the region. For this reason, pages are designed to function reasonably well on small screens and connections that may not always be fast or stable.
Mobile optimization may include images in modern formats such as WebP or AVIF, lazy loading for multimedia content located below the first screen, and a reduction in non-essential external scripts. These measures help reduce data consumption and improve loading speed on mid-range devices or slower connections.
Touch controls are designed with sufficient space to reduce accidental taps. As a reference for inclusive design, we aim for comfortable dimensions and suitable spacing between buttons, particularly in navigation menus, forms, and calls to action. A target size of 44 × 44 CSS pixels is a useful reference for preventing accidental activation, although exact requirements depend on the applicable WCAG criterion and the type of control. The W3C provides additional guidance on this approach.
| Mobile situation | Planned measure | Benefit |
|---|---|---|
| Slow connection | Optimized images and lazy loading. | Lower data consumption and faster loading. |
| Small screen | Responsive design and scalable text. | Reading without unnecessary horizontal scrolling. |
| Motor difficulty | Separated buttons and comfortable touch areas. | Fewer accidental taps. |
| Screen-reader navigation | Semantic structure and clear labels. | Better orientation within the page. |
Limitations of Third-Party Content
Some materials may include elements from external sources, such as screenshots of operator interfaces, links to regulatory documents, embedded charts, multimedia players, or resources from third-party organizations. The editorial team does not have complete control over the accessibility of these elements.
A screenshot of a gambling platform may contain small text, low contrast, reduced-size buttons, or information that is difficult to interpret with a screen reader. It is used only for illustrative purposes and not as a replacement for a written explanation. When appropriate, we add alternative text or a description explaining the important information.
Third-party widgets, embedded charts, PDF documents, and videos may retain limitations imposed by their original provider. We cannot modify their code, structure, or internal labels. However, we aim to reduce their impact by providing context, descriptive links, and text alternatives whenever possible.
Before following a link or using an external tool, please remember that the third party’s own terms, cookie policies, and accessibility conditions will apply.
How to Report an Accessibility Barrier
If you encounter difficulty accessing content or using a feature, you can report it through the website’s contact form. Accessibility barriers are reviewed as a priority, especially when they prevent someone from reading an article, navigating by keyboard, understanding a table, or submitting a request.
To help us identify the problem, please include:
- The URL of the affected page.
- A brief description of what is not working or is difficult to use.
- The device and browser being used.
- The assistive technology being used, if applicable.
- The step at which the difficulty occurs.
For example, you may report that a menu does not receive keyboard focus, an image lacks a description, text overlaps when enlarged, or a form is not announced correctly by a screen reader. Do not submit gambling-account information, personal documents, passwords, or banking details.
Continuous Improvement Cycle
Accessibility requires ongoing monitoring. We update pages, change templates, add images, modify forms, and introduce new features. Each change may create an unexpected barrier or provide an opportunity for improvement.
Automated checks may be performed when major changes are made to templates or shared components. Manual reviews focus particularly on keyboard navigation, focus indicators, headings, tables, forms, and experiences involving assistive technologies. A broader assessment may be carried out periodically, for example once a year or whenever significant design or structural changes are introduced.
The improvement cycle includes:
- Detecting errors through tools and manual reviews.
- Prioritizing barriers that block access to the main content.
- Correcting reusable components to prevent the same problem from appearing repeatedly.
- Retesting the solution with a keyboard and assistive tools.
- Documenting lessons for future publications and updates.
Not every improvement can be implemented immediately, particularly when it depends on third parties or extensive technical changes. Nevertheless, reported barriers help us define priorities and improve future versions of the website.
How We Use Reader Feedback
Reader feedback is an important source of information for identifying problems that may not appear during a technical review. Someone who uses a screen reader, enlarged text, keyboard navigation, or an adapted device may encounter specific difficulties in real-world situations.
Messages describing a specific barrier are reviewed as a priority. If the problem affects a shared template or component, it may be added to the improvement plan so that it can be corrected across multiple pages.
The editorial team aims to respond to accessibility inquiries whenever possible and provide information about an available correction or alternative. Although an exact resolution time cannot always be guaranteed, every clear report helps make the website easier to use for everyone.