Now that you’ve signed up for the AudioEye Ally Managed Service, you may have several questions about what to expect next. This article is an overview of the steps that our Finalsite and AudioEye teams will take during the implementation journey and covers frequently asked questions.
Setting up Communication
Shortly after the contract is signed and the addendum is approved on your account, you will be contacted by the Accessibility team and the following steps will be performed:
- The Accessibility team will start an AudioEye Work Order Mavenlink project with the main point of contact on the account.
- The Accessibility team will request that you:
- CC anyone who needs to be involved to the ticket, as we will be using this ticket as the main method of communication.
- Send over the desired start date for the service
- The Accessibility team will provide you with the following materials:
- Ally Toolbar Communication Template: Template used by schools to draft communications to constituents about the change to the site and the school’s commitment to accessibility
- Implementation Journey Phase I-III: A document that gives more details as to what to expect in each Phase
- AudioEye Ally Implementation Process Infographic: Infographic of Phases
- AudioEye's FAQ page
Once a date is determined by the school, Finalsite will add the script to the website and the AudioEye team will activate the AudioEye script and launch your site into Step 1. The AudioEye Ally toolbar will now be present on your site. From this point on, the remediation of your site will be addressed by the AudioEye Accessibility Engineer team.
The AudioEye Ally implementation is a phased process divided into 4 Steps. Step 1 occurs immediately when the script is activated. Once the script is activated, the Compliance Accelerator will auto-remediate and fix several of your site’s accessibility issues and display the Ally Toolbar. At this point in time, the Help Desk icon and the Accessibility Certification will be present in the toolbar stating the progress that your site has made.
After Step 1 is completed, the AudioEye Accessibility Engineers will begin the manual remediations of your site pages. They will use assistive technology (AT) testing to uncover and fix any accessibility issues on your site. Your Accessibility Certification will be updated to Step 2 about halfway through the manual implementation.
After AudioEye completes the manual remediations, Step 3 will be reached. At this point, the Ally Toolbar will now display all of the Ally Tools, including the Site Menu, Page Elements Menu, Reader, and Player. Step 4 consists of ongoing monitoring and maintenance by the AudioEye Accessibility Engineer team. If a content creator forgets to add alt text to a new page, the AudioEye team will be there to catch it and address the issue.
Frequently Asked Questions
Q: How long does it take to activate the script?
A: AudioEye will need up to 10 business days to configure the school's domains into their system. AudioEye will also need to test the Ally Toolbar for display issues before officially launching to the live site. It is important to let us know about your desired date as soon as possible, so that AudioEye can have enough time to properly set up the service and schedule time with their engineers.
Q: How long does the implementation take?
A: The Step 1-3 implementation timeframe is dependent on your site’s complexity, the original accessibility health of the site, and the size of the site. Generally, the implementation is completed within 120 - 150 days from the activation of the script.
Q: Is there reporting with the AudioEye Ally Managed Service?
A: Currently, there is no reporting provided in the Ally Service, since the accessibility of your site is managed for you.
Q: How often do the AudioEye Accessibility Engineers check the site for accessibility once the site is in Phase 3?
A: The AudioEye team audits your site as content is added. A manual review is made annually.
Q: Does the Ally Toolbar service address content that is in PDFs, videos or third-party content?
A: Currently, the AudioEye Ally Toolbar does not scan or address accessibility issues in these kinds of content. It is your responsibility to test this content before publishing or to contact the third-party service to update their content. For more information about making accessible PDFs and videos, please visit our Knowledge Base.
Q: Can you please record a video of the Toolbar working on my site?
A: AudioEye provides a demo video that explains the tools on the Toolbar. We encourage schools to view this video and perform a live demo for constituents or stakeholders.
Q: Why does the Ally icon not show in mobile?
A: By default, the icon is not visible on tablet/mobile. We do not service all AudioEye tools on mobile and tablet devices because mobile devices already come equipped with robust accessibility tools available for all users. This includes VoiceOver on iOS and TalkBack on Android.
These tools are customized for these devices, and end-users who require Assistive Technology are already accustomed to these accessibility features. Secondly, the size of the Ally icon on mobile is an issue, since it will need to take up valuable space on the bottom of the screen and may interfere with the site’s mobile display.
The above said, the fixes themselves are still loaded onto the mobile site, it is only the accessibility icon that is not present. If the client would like us to service the accessibility icon on mobile, we can make the Help Desk and Certification statement available. The Help Desk provides users a means to report any accessibility usability issues and the certification contains verbiage speaking to the site’s commitment to accessibility and usability.