AudioEye Remediation Technology: How it Works

In an effort to assist our clients in solving issues of digital accessibility, AudioEye offers a JavaScript plug-in that allows users to remediate issues with online content. Much like including an analytics tracking tag, the process for installing the AudioEye JavaScript is an easy one; simply ensure the AudioEye JavaScript gets embedded globally into your website’s template source. Through this JavaScript, AudioEye is then able to deliver live, custom, real-time, DOM-level accessibility remediations to every visitor of your website.

The AudioEye JavaScript remediates issues of accessibility by leveraging JavaScript to target elements in the DOM and add additional or missing attributes to allow your content to more effectively communicate with the Accessibility API (which is what Assistive Technologies such as Screen Readers use). In other circumstances, we may add additional non-visual elements that can improve the experience for users of certain types of Assistive Technologies.  In all circumstances our JavaScript only makes non-visual changes to the DOM[1].

The AudioEye JavaScript employs a test-centric approach to fixing issues of accessibility, whereby JavaScript remediations are only applied when a specific WCAG failure condition is met. In other words, the AudioEye JavaScript only attempts to fix errors it uncovers in real-time. If an issue is not discovered, the AudioEye JavaScript simply lies dormant until such time as an issue is introduced. In this way, AudioEye remediations apply only when required and will never attempt to override accessibility issues that have already been corrected at the source.

The AudioEye JavaScript works by combining a rich library of automatic remediations and manual remediations. Automatic remediations are JavaScript functions that can be applied equally to all websites and are known to improve the accessibility of any website. Manual remediations are custom, site-specific JavaScript functions designed to remediate issues of accessibility which are unique to a given site. Both automatic and manual remediations are delivered via the same AudioEye JavaScript file, and, because AudioEye is delivering remediations via JavaScript, we are able to fix issues of accessibility without requiring access to our client’s original source code.

[1] Certain visual changes may be required to achieve full WCAG 2.0 conformance. AudioEye will never make visual changes to a site without receiving explicit direction from our clients.

Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk