It may vary based on your CMS, but basically:

1. Log into the AudioEye Portal
2. Copy your AudioEye JavaScript to your clipboard
3. Log into your Platform Provider
4. Open your Page Editor
5. Paste the code globally within the Footer

Some competitors offer no more than a cheap toolbar. While toolbars can enable users to personalize the look of your website by changing contrast, fonts, and the display of animations, they don’t help a visitor who relies on assistive technology such as a screen reader.

Other companies offer solutions that are completely automated, but fail to point out that automation can only fix up to 35% of WCAG errors.

Then there are the consultants who will charge a high fee to explain your WCAG violations, but offer no solutions to resolve them.

At AudioEye, we combine powerful technology with expert testing and engineering. You outsource your compliance entirely to our advanced AI and team of certified experts. We're always-on, so you're never out of compliance. And, yes, we also give you a toolbar—one that has been tested by people who actually rely on assistive technology.

Yes. AudioEye takes each of our clients' security very seriously and has a duty to protect every site visitor accessing the Usability Toolbar embedded within our clients' websites. AudioEye conducts quarterly PEN tests, pre-release static code testing, and ongoing security awareness training to provide the highest level of security.

Wrong. A toolbar generally enhances usability for your visitors. They can change things like color contrast, the size of the cursor, font, font size, and more. Making your digital content accessible to an individual with an assistive technology, like a screen reader, requires back-end work.

With AudioEye, we find and fix your accessibility errors on your behalf and certify your compliance. Oh, and we also provide a toolbar!

A standard implementation of AudioEye on a typical web property delivers approximately 100kB of compressed JavaScript to a client’s browser, via our global CDN. The actual size of the code depends on the number of custom JavaScript functions that are required to remediate a given webpage. Users accessing an AudioEye-enabled website via standard broadband connection or fourth-generation mobile connection should expect to see the delivery times of approximately 200 - 400ms for the software to load. As this load time only takes place after the original page has fired its document-ready event, and is done so asynchronously, via JavaScript, there should be no perceived difference to an end user viewing a site with or without AudioEye.