AccessiWay is GDPR compliant because no personal or sensitive end-user data is processed or stored. The only personal data that is transmitted to our servers is the IP address.The software works client-side in a local session, so the other data we process (purely technical: css attributes and html elements) are saved in 'Local Storage' and not on AccessiWay's servers.
Testing tools such as WAVE and Lighthouse are free tools to check the accessibility level of your website. These tools are useful for checking basic elements of a site such as duplicate links, title hierarchies, duplicate titles, lack of image descriptions (Alt Text), or ARIA labels.
However, accessWidget is a tool that works in a client-side local session: this means that compliance tools of this kind will not be able to detect accessWidget adjustments. This is because accessWidget is designed to only activate when a user triggers it as required. This implies no permanent changes on the site. This ensures that all adjustments are easily activated and that the browsing experience of site visitors who do not need these changes is not affected in any way.
Therefore, since compliance tools do not access a website in the form of assistive technology, they will not be able to analyse the presence of accessWidget on a website and the resulting accessibility adjustments.
AccessiWay is designed to load asynchronously with your site, which means that it will only be loaded and displayed once the website is fully loaded. This is to:
Make the entire site accessible, not just specific parts of it.
Not affect the speed of the site or its performance in any way.
The AccessiWay system takes 0.2 seconds to load, which means that the loading time of your site will affect the time it takes to display AccessiWay. For example: if your site loads in 4 seconds, AccessiWay will appear in 4.2 seconds. If your site loads in 8 seconds, then AccessiWay will appear in 8.2 seconds.
If you are interested in checking the loading time of your site, we recommend a site called Pingdom. You can access it at the following link: https://tools.pingdom.com.
If you still feel there may be an error with the loading of AccessiWay, please contact one of our representatives to try and resolve your problem as soon as possible.
Have you already installed accessWidget on your site, but still do not see the accessibility icon?
This can happen for various reasons, but it is easy to solve. Here are some possible reasons and their solutions:
1) The trial period on your site has expired: this simply means that the 7-day trial for which your site was registered has expired. To continue using AccessiWay you will need to purchase a licence directly from your account, or speak to one of our sales representatives.
2) The code is not installed correctly: installing the script in the wrong area can cause AccessWidget to malfunction. To check if this is the case, go to your site and press F12. Once this is done, a pop-up bar will appear at the bottom of the screen displaying your website's code. When it appears, press Control + F, a search bar will appear at the bottom. In this search field type "acsb", if you see the script the software has been installed correctly. Contact us via the support form by pressing the 'contact us' button or write to us directly in the live chat.
3) Browser cache error: this can happen if you have many files stored in the browser cache from your website (automatically stored to improve loading speed), which shows you the version displayed before installing accessWidget. To correct this error, you simply have to empty your browser cache (this may vary depending on the browser). In most cases, simply go to your browser settings and delete the cached images and files. Once this is done, simply reload the page to obtain the correct display.
Web accessibility is a process and it would be impossible to break down all digital barriers with just one tool.
accessWidget does not repair what is not line of code (e.g. PDF, video, iFrame, app, webapp, intranet)
Anything displayed on a screen has been realised within a code. For visually-impaired people, this is not a problem as long as what we are seeing on the screen makes sense. Blind people navigate the web using a screen reader, or screen reader, which is an assistive technology that is used by blind people to use computers and surf the web. A screen-reader 'bypasses' the screen and goes straight to the code to examine and then report back to the blind user what is represented on the screen. It is essential that a website's code correctly reflects what is displayed on the website. However, there are different ways to code certain elements (such as a menu or drop-down menu) that will all look the same in the eyes of a visually-impaired person. For a visually-impaired person, who cannot recognise the overall structure of an element, reading content on a website could be misleading. For example, think of images on a website. Many times, images are used to symbolise a category on a website or to launch a newly released offer or product. In this case, a visually-impaired person can read the text "Clothes for kids" or "30% off kitchen supplies" on the image, but a visually-impaired person will only be able to hear the screen-reader read "graphics", which is the word in the code.
Generally, in the context of a website, physical and motor disabilities are defined by the inability to use a mouse to navigate. In general, a keyboard can do everything a mouse can do. The problem is that most websites are not optimised for keyboard navigation, which means that page elements do not respond to commanded actions. As a result, these sites exclude people with motor disabilities. This means that if a website element, such as a popup, form or menu, is not designed to respond to keyboard commands, then there is no way to interact with them without a mouse. For example, we all know that when we enter a website, an image or banner may appear in the form of a popup. If this happens, we click on the X to close it and continue to browse the site quietly. The problem arises if the popup is not optimised for keyboard navigation and does not respond to the command to close the popup: the user will be stuck on the popup, unable to return to the original page.
accessiWidget makes websites fully navigable via the keyboard. Using the ARIA attributes and contextual understanding of the AI engine, the necessary changes are made throughout the website code. People with motor disabilities can use the buttons to perform any action, from closing popups and forms to opening dropdowns and menus. Furthermore, to facilitate and speed up access to the various parts of the site, users can consult a list of 'useful links' directly from the interface. In this way, navigation is truly accessible and saves the user time and energy.
People with cognitive disabilities have certain limitations that can affect the way the content of a website is perceived and understood. These people, when visiting a website, may have confusing and frustrating experiences without proper context or changes in orientation. For example, slang and abbreviations can be complicated to understand for people with cognitive disabilities who do not know how to interpret the meaning of a word. When it comes to orientation, many websites are beautifully and innovatively designed, but can be quite disorienting for those who cannot focus on the various elements of the site.
accessWidget helps people with cognitive disabilities by enabling features on your site that add clarity and focus to the elements on the page. For example, the accessWidget interface comes with an integrated dictionary for on-demand definitions. In addition, site elements are outlined and focused so that visitors can clearly see the flow of the page without being distracted. The accessWidget interface also offers a default profile of Cognitive Disabilities. Visitors who require extra attention to fully understand elements of the site may not easily identify which accessibility modifications they need. By accessing this Profile, which can be easily identified by users, all the above-mentioned modifications are enabled for quick, simple and complete web accessibility.
The beauty of websites is that they can be designed to display content in the most diverse ways. Unfortunately, some inaccessible elements can be frustrating and even dangerous for some users. People suffering from epilepsy are forced to navigate websites with great caution, due to the risk of triggering a seizure caused by flashing elements such as GIFs, videos or animations. In many cases, these images are looped or autoplay or do not respond to a user's interaction or attempts to interrupt. Put simply, any site can be something akin to a minefield for a person suffering from epilepsy.
AccessiWay's interface allows site visitors to stop all flashing elements on a page. Instead of scrolling carefully and quickly pausing dangerous elements, epileptic users can pause everything at once before viewing it. This is made even easier by activating the 'Seizure Safe' profile, which simultaneously stops all flashing/blinking elements and reduces dangerous colour combinations.
A website can have many different shades, colours and formats. For people with visual impairments, the wrong colour scheme or font size can make it complicated or even impossible to view the content of your site. Common visual impairments include blurred vision, colour blindness and glaucoma. For example, you use one main colour for the theme of your website: a visitor suffering from colour blindness may not even be able to see it. In other cases, fonts are too compact or too small for a website user, who will not even be able to read what is written on a page. One of the main obstacles to accessible design is that many times a website owner does not want to compromise their website design and branding just for the sake of accessibility: a website is an extension of their business, and many times represents the presentation and first contact with a customer. This makes a company's website, no matter what the market or service, a very important factor! With accessWidget and consulting services, you can stay true to your design and allow people with visual impairments to navigate effectively.
After installing AccessiWay on your site, the new accessibility interface will immediately appear on your website. This interface is an accessibility-based tool, i.e. it allows visitors with visual impairments to make changes on demand for as long as they are on the site. For site users who do not need adjustments, the design of the site will remain intact. UI and design adjustments include changes to content, colour and orientation. All accessibility changes mentioned for visual impairments will be activated simultaneously, allowing the user an easy view of the content.
No, accessWidget works in Overlay, so it is impossible for the source code to be modified or for the performance of the site to be affected.
The loading of the software takes place asynchronously to that of the site, precisely 0.2 seconds later.
The user interface will immediately appear on the site. The AI can take up to a maximum of 48 hours to implement all the necessary changes (insert all the information to make the site navigable for people with disabilities). In addition, the longer AccessWidget remains on the site, the easier it will find it to work with any updates of new elements. AccessWidget performs a daily scan of the site, noticing any additions, and then remediates them in an automatic and automated manner.
Yes! AccessiWay uses two AI engines. The first, 'Computer Vision', is used to analyse and describe images. The other has the function of Contextual Understanding, and is used to learn the purpose and functionality of elements on the website.
Web accessibility is a process and it is not enough to have software to be able to define oneself as fully accessible and/or compliant.
Having a usable site from a practical point of view does not guarantee compliance with the regulations (imposed by L. 9 January 4/2004) because there are requirements that go beyond the navigability of the site, for recipients defined as "providers" in Art 3 L 4/2004, such as the Declaration of Accessibility (art 3-Quarter) and / or the training period (art 8.3).
It is therefore necessary, in order to be able to speak of full compliance and accessibility, to also make use of the consulting services offered by AccessiWay