Accessibility

The Funnelback Accessibility Auditor tool examines web content for accessibility issues. Using Funnelback's underlying crawling and filtering technology, millions of URLs are able to be examined for conformance on a regular basis, with conformance able to be examined over time. Once configured, a successful run against a collection will provide a series of reports via a web-based user interface for logged-in users.

Accessibility Auditor was previously known as WCAG Compliance Auditor (WCA).

Prior to Funnelback 15.10, the 'classic' accessibility auditor interface was used. This interface remains available in 15.10, however is not documented here. The documentation for it remains available online.

Accessibility Auditor Reports

Accessibility auditor reports are available for frontends within the Funnelback administration interface as long as accessibility auditor has been enabled on the underlying collection. The reporting interface consists of six main pages.

  • Overview - Provides high level statistics for the frontend as a whole, including over-time reporting for the frontend.
  • Domain Overview - Provides high level statistics for a single domain, including over-time reporting.
  • Documents - Provides reports for each individual document within the frontend, which can be scoped via a range of facets.
  • Document Audit - Provides a detailed audit for a document, highlighting problems within a source view (for HTML documents). The document audit page also allows specific issues Funnelback reports to be 'acknowledged', indicating that a human has reviewed them and that they should be excluded from future reports.
  • Issues - Provides an overview of the specific issues identified across all documents, with details of their WCAG 2.0 specification success criteria.
  • Acknowledgements - Provides a listing and management functions for acknowledged issues.

In-context documentation is also provided by way of '?' help links within the reporting interface itself.

Accessibility Auditor Administration

Accessibility auditor may be enabled for web collections from the 'Edit collection settings' screen, under the 'Accessibility Auditor' tab. Enabling this setting causes accessibility analysis to be performed on all HTML and PDF documents during document filtering, whenever the collection is updated. This setting adjusts the accessibility-auditor.check collection.cfg setting.

Most user management for accessibility auditor can be performed by managing user permissions on frontends, which will allow administrator users to access accessibility reports for either entire collections, or specific sub-sets (since the accessibility-auditor reporting interface will respect any scoping query processor options specified on the frontend). Generally, users must have the sec.accessibility-auditor role to allow access to the accessibility auditor reports, and must have permission on the underlying collection to work with acknowledgements.

top