Eye-Able® Audit
Identify and fix errors yourself with your WCAG checking software for all browsers.
General questions | Audit
- Can the Testing Tools Also Check the Mobile View?
- How Many Test Steps Are Included in Audit and Report?
- Can Audit Be Used Locally?
- What Result in the Dashboard Overview Is Considered Good?
- Which Barriers Cannot Be Tested by the Audit?
- Why are there differences between Report and Audit results?
- How can I hide errors in Audit or Report?
- Why does the warning ‘Touch target is too small’ sometimes result in unclear error messages?
- Does Eye-Able® Audit show exactly where an error is?
- Is the cookie banner checked by Eye-Able® Audit and Eye-Able® Report?
- Why can't Eye-Able® Audit be used on newly activated domains?
- Which errors in the report should be addressed first?
- 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 and Eye-Able® Report reports be downloaded or exported?
- Can Eye-Able® Audit or Eye-Able® Report switch between WCAG 2.1 and WCAG 2.2?
- If a website does not contain any errors found by Eye-Able® Audit and Eye-Able® Report, is it legally compliant and 100% accessible?
- Can visitors to the website also use Eye-Able® Audit?