Some of the things you can learn in 40 seconds (video above):

• Automatically assisted auditing features could be very helpful in documenting accessibility errors the automatic tests uncovered.
• EN 301 549 has 137 success criteria for websites, some of which can be unselected based on what is being tested.
• For mobile applications, the number of success criteria that requires testing is 162 in EN 301 549.

Work smarter, not harder

Let automation test what it can. For one, or one thousand pages. Cover the rest of what needs to be tested with guided testing or manual tests with detailed testing instructions.

Combine all information sources with a single click on Accessibility Cloud to watch your audit come to life.

Information sources allow including test results from other sources to your audit. This is a great and innovative way to work with accessibility audits as it enables many benefits, including live audits.

Information sources which can be selected to your audits:

• Automatic test results from Accessibility Cloud’s automatic tests
• Findings (library of individual accessibility defects you documented)
• Guided tests

Once activated, the results of these sources are automatically processed, violations are documented, linked and included in your audit reports.

Some of the things you can learn in 90 seconds (video above):

• Automatic test results can help with your audit with details you might miss since the automation will cover many pages
• Accessibility Cloud shows you which automatic tests are passed but when it comes to marking corresponding success criteria, they go as “Cannot tell”. All automatic accessibility tests done by any technology have partial coverage over relevant success criteria and tools can just be wrong. Auditors / testers have control and final say over what gets registered as “Passed” or “Failed”, as it should be.
• If you document the defects as individual findings, your audit will take significantly less time, plus, findings will give you a lot of side benefits.
• Audits can be created by utilizing one or more information sources and Accessibility Cloud manages relationships between engines, testing tools, data formats and associations of everything to each guideline.

Since information sources are different data points elsewhere in Accessibility Cloud, their statuses can also be reflected to your audits in real-time, if you prefer. This introduces the possibility of having a live audit, which updates itself as the problems of the site get remediated and when you mark individual findings as resolved. Corresponding violations will be removed from your reports as they get resolved, making your accessibility audit report a live one, always showing the correct conformance level.

Here are three examples, one for each information source:

• Automatic test results changing a live audit
  Remediation is successful and the monitoring revealed that the accessibility error documented on your audit is fixed. It disappears from your live audit after your review.
• Findings changing a live audit
  Remediation is successful and you tested the defect for accessibility. You mark the finding as resolved and it disappears from your live audit.
• Guided tests changing a live audit
  You made an update to your previous guided test. The defects from your previous version are no longer there. Violations associated disappear from your live audit.

Needless to say, for those who prefer traditional, static audits / test reports, that’s also available. Static audits / manual tests are locked in time and they don’t get updated automatically. This is called finalization in Accessibility Cloud. This option can be found on the audit report.

Accessibility Cloud crawls and tests your entire site, or a great number of pages, by default, unless you stop this behavior. This paves the way for automatic sample selection for audits / manual tests. Accessibility Cloud uses the following parameters in determining which pages are the most important ones and what type of accessibility problems which are discovered in each page and how do these errors correspond to those important pages to determine a meaningful and representative sample selection that is also testable manually.

• Crawling data
• Menu structure
• Accessibility errors discovered
• Error / occurrence densities of each error
• Errors’ relationship with pages
• More

Accessibility Cloud offers detailed manual testing instructions from a great, open-source resource: WCAG Primer