AccessiSiTE' technology covers a wide range of disabilities, diseases, and disorders. The system itself was developed in cooperation with disabled people from a wide range of fields so that we could evaluate throughout the devlopment process how different people with different abilities surf the internet. Based on this information we developed all of the system's features including the entire technological support. The following disabilities are supported: Full or partial blindness using screen reading software such as NVDA and JAWS. Motor disabilities such as joint injuries, limb amputations, and more. Parkinson's diseae (inability to control a mouse) Epilepsy (seizures when subject to flashing animations) Seniors who suffer from a wide variety of limitations. Cognitive disabilities such as memory disorders,dyslexia, stroke victims, and more. Visual impartments such as color blindness, catarcts, glaucoma, and more.

Comparing web accessibility providers, there are three different types of solutions. Our solution stands as a category in itself. Below you will find a detailed explanation of the various accessibility options, as well as a simple visual comparison table that will help you easily see the difference between those possible solutions. 1. Plugins and Add-Ons (free or not) Solutions of this kind are usually free available for a very low payment (a few dollars or tens of dollars). They provide approximately 20% compatibility with accessibility standards. These solutions do not meet the standard, nor do they help disabled people surf your website. They also expose the owners to immediate lawsuits. Those plugins do not even perform (and do not even claim to perform) 80% of the adjustments required by the standard, so using this kind of plugin does not provide protection from the law and does not even give you 60 days to repair malfunctions. Additionally, try to imagine a situation where you have a disability that prevents you from surfing the Internet, and you visit a website that has such a plugin installed. At first glance, you will be happy, as you will think that the site is indeed accessible and you can surf it and enjoy it. But once you get into the thick of it and try to surf, you will discover the disappointment. It's like reaching out your hand to a blind person, and when he tries to grab it, pull back. Not acceptable. 2. Manual Accessibility Services When you undertake a manual accessibility project, it's likely that your site will be accessible to the AA level and meet the standard once the project is completed. The main problem with this approach is that you will see a drastic deterioration in the level of accessibility within no more than three months from the time of implementation, with the vast majority being completely un-accessible in about 6-12 months. The reason for this is that after the code has been implemented, every site update, addition, or change is simply not going through the same process, so it is not accessible. It is important to understand that as more changes are made to the site, in time, the level of accessibility will decrease (because many new things have not been made accessible), to the point where the site accessibility is completely broken. The collapse of the site's accessibility in such projects usually takes place within six months to a year, and it can be easily recognized in almost every site that has been made accessible manually, and even on sites that have paid tens of thousands of dollars for this accessibility (the price of such a project starts at $1000 dollars and might reach tens of thousands of dollars). There is indeed one way to deal with this problem, but it requires a high monthly fee for an accessibility company to review the changes every month and make the site accessible. This can become very expensive even if you are a very large company with deep pockets. 3. Our System Our system is the first and only system in the world that knows how to make websites accessible to the AA level, in accordance with the accessibility legislation and with WCAG 2.0 standards, and does so using two machine learning AI’s (artificial intelligence). The first artificial intelligence is called "contextual understanding" and it can scan and decode the site it's installed on, understand the structure of links, titles, menus, elements, forms, and more, and make them accessible automatically, according to what it finds. The second artificial intelligence is a technological solution in collaboration with Google and Clarifai, and it knows how to scan and decode images and the elements in them, and provide accurate descriptions of all the images on the site that lack a description, so that blind people can also enjoy them while using screen reading software. Our solution does not depend on any person to decode and understand the structure of the site and make it accessible, rather it does so with AI (machine learning artificial intelligence). Therefore, it can scan the site, detect changes and updates, and make them accessible, in an entirely automatic way, every 48 hours. This means there is no dependency between updating the site and it's level of accessibility, and you can make as many changes and updates as you want. As you can see, our solution has a number of key advantages over other accessibility solutions on the market. Due to the affordable price, there are no more barriers or excuses. Until today, making a site accessible would cost thousands of dollars and leave a hole in your pocket.

Our solution does not interfere at all with the site’s source code. It "gets over" the site’s code on the side of the browser as soon as it loads, and modifies it according to user requirements. If the user has not chosen to perform an action, it won't do anything to the site code, and in any case, the system does not change, delete, save, or update anything from the source code, only from the code shown in the browser (also known as Client Side) - these changes occur only in the document’s objects structure (DOM) and using CSS and JS, and no system-level or server-level interface is required. Once the code has been removed from the site, the system will have no trace of it in the site itself. Additionally, it does not affect the site's performance at all. The system itself loads only after the entire site is loaded and fully rendered by the browser. In addition to this, the system loads asynchronously, so the browser does not wait for its loading in order to show the user your site or allow them to take action. In this way, we can take pride in the fact that the system does not affect site loading times and does not affect the site optimization score even minimally. And on top of that, it loads at full speed, with compressed files (GZIP) and full cashing, allowing the surfers full and proper use of the website from the very first moment.

Of course! There is no reason to get nervous, we are here to help. We're not going anywhere. If you have receive a complaint about the accessibility of your site, please gather as much information as possible about the problem. For example: in what pages it happens, which browsers or devices, and in what context. Does it happen after pressing a certain button? Is it showing right when the website is up? Does this happen when a screen reader is turned on? Once you've collected all the information, contact us and tell us about it. We will inspect, and if there is a problem, we will work to resolve it as quickly as possible. Beyond that, the number of repairs, modifications, additions, and improvements that we make is astronomical. We're constantly improving the system and adding capabilities to it.

First of all, it is important to understand that our system can fully operate on any site, in any system, and even without any system at all. Our system works on the client side and is not dependent on the server or the server-side language on which your site is built on. We have customers who maintain a website in many different systems, which are built in different server languages such as NET, Java, Python, NODE.JS, and PHP of course. Some of the systems it works on (beyond the obvious ones like WordPress, Joomla, Wix, Magento, and other popular site: .NET Nuke, Umbraco, Drupal, Webflow, Weebly, Instapage, PrestaShop, SquareSpace, Blogger, Volution , BigCommerce, Confluence, dotCMS, DJANGO, Plone, Ghost (node.js) and many others. There is no connection between the system on which the site is built on, to whether our solution will work on the site or not. In order to install our solution on a system for which we do not have an installation guide or plugin, you need to learn how to put a JavaScript block into your site. The chance that your system does not allow the entry of such code is low, so if you do not know or do not find the right place, it probably exists, you just have to ask the person who built the site for you to explain it to you. Note that for most systems, even the least popular ones, you can find guides on how to enter JavaScript blocks on the site, on Google.