Description
AudioEye’s patented technology tests for over 400 accessibility and compliance issues, and fixes many of them automatically, reducing the time to make content accessible.
You will get your first AudioEye Accessibility Score the moment you install AudioEye on your site. From then on, AudioEye monitors your site for new issues with every site visitor, detecting and fixing hundreds of errors, while also providing you with a reporting dashboard that identifies what we cannot fix and needs your attention.
Technology can’t do it alone. With advanced plans, AudioEye has a team of certified accessibility experts who can help you throughout your accessibility journey. For those issues that we cannot fix automatically, we show you what the issue is, and how to address it on your site. If a lawsuit occurs, AudioEye is here to support you every step of the way.
Note: Use of the AudioEye plugin requires an active subscription to an AudioEye Plan. See pricing here. A link to sign up for a new account is presented during the plugin activation process. To log into an existing AudioEye account, you will need to provide your AudioEye Site ID.
Script delivery (CDN): AudioEye loads the storefront script (aem.js) from wsmcdn.audioeye.com by default today. We are migrating to wsv3cdn.audioeye-services.com. New setups without a saved Site ID use the new host by default; sites that already had a Site ID saved before the CDN preference existed keep the legacy host until an administrator enables the new host under AudioEye Script CDN (Advanced) after allowlisting the new URL in any Content Security Policy (script-src, etc.). On first run, the plugin includes an optional onboarding step that explains how to allowlist the new host in your CSP.
Features included in all AudioEye base plans:
- Path to compliance with ADA, Sec 508, AODA & more, using WCAG 2.1 AA
- AudioEye Trusted Certification
- Usability toolbar with 24/7 Helpdesk
- Suite of AI-Powered Tests & Fixes
- Access to Certified Accessibility Experts
- Basic Legal Support & Warranty
Features available in AudioEye custom plans:
- Advanced Legal Support
- Manual Remediations
- Premium Support
- Custom Training
Screenshots
AudioEye activation screen – sign up for a new AudioEye account or add an existing AudioEye Site ID 
Activation confirmation screen 
AudioEye Web Accessibility plugin admin panel – links to the AudioEye Dashboard and to re-enter your Side ID if necessary
Installation
You can easily install the AudioEye plugin from your WordPress admin area by searching ‘audioeye’ and following the prompts. You can also install the AudioEye plugin manually:
1. Download the plugin’s zip file, extract the contents, and upload them to your wp-content/plugins folder.
2. Login to your WordPress dashboard. Activate the AudioEye plugin through the ‘Plugins’ menu.
3. Within the AudioEye plugin dashboard, create an AudioEye account or login to an existing account.
FAQ
-
What is digital accessibility compliance?
-
In the United States and many other countries, there are laws that call for digital content to be accessible to people with disabilities. Making digital content accessible means that people with disabilities are able to access and navigate the content using Assistive Technologies.
Compliance to the law differs from country to country but, generally speaking, the guidelines set forth in W3C, called the Web Content Accessibility Guidelines (WCAG), are used to measure compliance. As defined in WCAG, website content needs to be perceivable, operable, understandable and robust.
-
Is the AudioEye solution secure?
-
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.
-
Why can’t AI do it all?
-
As smart as artificial intelligence has become, it simply cannot do everything that is needed to test and fix digital content so that it is accessible. And, in fact, the compliance standards explicitly recognize this and call for manual testing as a requirement.
-
A toolbar is all I need, right?
-
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 automatically find and fix the majority of common accessibility errors while providing reporting on which issues need to be addressed directly. Oh, and we also provide a toolbar!
Read Our Blog: Toolbars, Overlays & Testing: Demystifying The Tech Behind Online Accessibility
Reviews
Contributors & Developers
“Accessibility by AudioEye” is open source software. The following people have contributed to this plugin.
Contributors
“Accessibility by AudioEye” has been translated into 1 locale. Thank you to the translators for their contributions.
Translate “Accessibility by AudioEye” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.2.0
- CDN migration: Documented and shipped admin guidance for moving storefront script delivery from
wsmcdn.audioeye.com(legacy) towsv3cdn.audioeye-services.com. The legacy host remains the default for existing installs until you opt in; new installs without a saved Site ID default to the new host. Use AudioEye Script CDN (Advanced) to save your preference after updating your Content Security Policy (script-srcand any other directives your site requires for third-party scripts). - Onboarding: First-run flow adds step “2. Optional: add our script host to your CSP allowlist” before you enter your Site ID, so teams can update policies before go-live.
- Admin UI: Script CDN (Advanced) on the active settings screen is a plain section with migration copy, checkbox, and save (no accordion). CDN preference can be saved before or after entering a Site ID.
