Eye-Able Audit
Identify and fix errors yourself with your WCAG checking software for all browsers.
General questions | Audit
- Testing the mobile view with the Eye-Able testing software
- Overview of All Test Steps for Audit and Report
- Can Audit be used locally?
- Which Barriers Cannot Be Tested by the Audit?
- Cookie banner check in Eye-Able Audit and Eye-Able Report
- What does a ‘warning’ mean in Eye-Able® Audit and Report?
- Do decorative images trigger an error message in Eye-Able® Report or Audit?
- Can native apps (iOS/Android) also be tested with Audit or Report?
- Can Eye-Able® Audit or Eye-Able® Report switch between WCAG 2.1 and WCAG 2.2?
- Can visitors to the website also use Eye-Able Audit?
- Does the Eye-Able testing software work in a similar way to the Wave plug-in in the browser?
- Eye-Able Figma Audit
Installation | Audit
Features and Functions | Assist
- License activation for Eye-Able Audit on newly activated domains
- Does Eye-Able® Audit show exactly where an error is?
- How can I hide errors in Audit or Report?
- Why does the warning ‘Touch target is too small’ sometimes result in unclear error messages?
- I do not have the ‘Hide problem manually’ feature in the audit. How can I activate it?
- Can Eye-Able® Audit and Eye-Able® Report reports be downloaded or exported?
- How can I grant Audit access to all websites?
- Why are there differences between Report and Audit results?