We firmly believe that the internet should be available and accessible to anyone, and are committed to providing a website that is accessible to the widest possible audience regardless of circumstance and ability.
To fulfill this, we aim to adhere to the strictly as possible to the World Wide Web Consortium''s (W3C's) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level. These guidelines explain how to make web content accessible to people with a wide array of disabilities. Complying with those guidelines helps us ensure that the site is accessible to all the people: for blind people, people with motor impairments, visual impairment, cognitive disabilities, and more.
This website is the use of various technologies that are meant to make it all accessible as possible at all times. We use an accessibility interface that allows persons with specific disabilities to adjust the website's UI (user interface) and design it to their personal needs.
Additionally, the website, the use of an AI-based application that runs in the background and optimizes its accessibility level constantly. This application remediates the website's HTML adapts Its functionality and behavior for screen-readers used by the blind users, and is the keyboard, the functions used by individuals with motor impairments.
If you've found a malfunction or have ideas for improvement, we'll be happy to hear from you. You can reach out to the website's operators by using the following e-mail
Our site implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure blind users visiting fellow with the -screen readers are able to read, comprehend, and enjoy of the website's functions. As soon as the user with a screen reader enters your site, they immediately receive at the prompt to enter the Screen-Reader-Profile, so they can browse and operate your web site effectively. Here's how our website covers some of the most important screen-reader requirements alongside the console, with screenshots of the code examples:
Screen-reader optimization: we run a background process that learns the website's components from top to bottom, to ensure ongoing compliance, even when updating the web site. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we may provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.). validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others. Additionally, the background process that scans all of the website's images and provides an accurate and meaningful image-object-recognition-based description as an ALT (alternate text) tag for images that are not described. It will also extract texts that are embedded within the image, using an OCR (optical character recognition) technology. To turn on screen-reader adjustments at any time, users need only to press the Alt+1 keyboard combination. Screen-reader users also get automatic announcements to turn the Screen reader mode on as soon as they enter the website.
These adjustments are compatible with all popular screen readers, including JAWS, and NVDA.
Users can also use shortcuts such as “M” (menu), “H” (headings and subheadings), “(F)” (the forms), and B buttons), and G (graphics) to jump to specific elements.
We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with the few limitations as possible. Therefore, we have worked very hard to be able to support all the major systems that comprise over 95% of the user market share, including Google's Chrome, Mozilla's Firefox, Apple's Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers), both for Windows and for MAC users.
Despite our very best efforts to allow anybody to adjust the website to their needs, there may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our back-end, adding, updating and improving its options and features, and developing and adopting new technologies. All of this is meant to reach the optimal level of accessibility, following the technological advancements. For any assistance, please reach out to