Actions
The following buttons appear at the top of the right panel and give ways to handle the issue:
Fix: Allows you to fix an issue through the following methods:
Code Editor: Using the code editor will open a new window for writing code in TypeScript, based on the jQuery library and CSS styles. The code editor uses IntelliSense for ease of use and supplies several Allyable libraries for writing standard and global code.
A patch is created for a specific element by its selector and its page URL. The selector can be changed to group multiple issues of the same type or create a more generic selector. validating for a page can be overridden to make a patch apply to the entire domain.
Input Text: Text issues can be fixed by entering the missing text in a designated field. If more than one language is configured for the specific domain, a new field is created for each language to fill.
Filling the text creates the necessary code behind the scenes (the actual code is displayed in the TypeScript tab).
In the settings tab a label can be given to each patch for easier identification.
Wizards: The wizard enables back office users without knowledge in coding to fix generic issues.
Ignore . Clicking Ignore for an issue signals to the system that the issue is known and considered as the desired outcome. The system stops alerting about the issue until the next detection.
Disable . Visible only on AutoFix. Clicking Disable signals to the AI-WEB engine to stop auto-fixing the issue on the next run.
Enable . Re-enable a disabled fix.
Approve . Once a patch is created, an approval is necessary to use it as a patch and published to the virtual layer. (This requires special permissions.)
Once a fix is created and Saved, a new tag will appear next to it, indicating that the fix is waiting for approval. Only users with admin rights will be allowed to approve a fix. An approved fix is ready to be published to the customer website using a bundle
Related Articles
Embedding a single line of code
Allyable provide each customer with a secured single line of code to embed in their website. When the script is embedded in the website correctly, the accessibility virtual layer is applied on each visited page, scan for accessibility violations and ...deploying a “one line of code”. What are the exact steps to deploy this?
The "one line of code" is a simple script to implement for each domain/sub-domain you want to evaluate. The script should be embedded in the beginning of the <head> section of the master page of each application and contain an "async" attribute to ...Can the modifications selected by customers via the Accessibility Overlay be done without the need of our developers having to hard-code anything for it?
All the modifications are part of the accessibility overlay, nothing is changed in the source code.Is there a way to change/alter the modification options on the Accessibility Overlay provided to customers on the site without having to hard-code anything for it?
All the modifications are part of the accessibility overlay. We provide simple wizards and code editors in our backend for easy remediation.What kind of required hard-code development is needed to add the Accessibility Overlay to a site for customers to use it?
Each license requires a secured single line of code to embed in the website. Just like google analytics once this script is embedded every visited page is being scanned, monitored and violations are logged in the backend.