Introduction to the Attest Extension

On this page:

The WorldSpace Attest browser extension is the third generation of Deque's popular web accessibility checking tool that works within the web browser. It provides developers, content authors, and QA testers with the ability to check pages for accessibility issues, and to get expert help to solve them, while providing additional functionality as compared with Deque's open-source extension and accessibility rules engine, aXe.

Example of the new user interface of the Analyze pane of the Attest extension in Chrome

It is integrated with Deque's Enterprise accessibility Conformance Platform (ECP), featuring the WorldSpace suite of products, which includes the Attest, Assure, and Comply products that collectively represent the most powerful accessibility software suite available. WorldSpace Comply users can upload issues and scripts from the Attest extension to WorldSpace Comply, or download issues and scripts from WorldSpace Comply to the Attest extension. Additionally, the Attest extension provides Deque University clients with the ability to take advantage of enhanced, premium accessibility rule information and violation remediation advice in Attest.

What's New in 1.2?

Your WorldSpace Server Only!

Server Communication Note: Regardless of which version of the aXe-core rules you select for use in WorldSpace Comply or Attest projects, the engine in the extension does not ever communicate with any server other than the one hosting the page(s) being tested and the one on which your WorldSpace product(s) are installed (whether in Deque's secure cloud or on your local premises).

Past Versions: Attest continues to be a rapidly-evolving product. To view the user guide for the previous release versions, see WorldSpace Attest Browser Extension (for Chrome) 1.0 User Guide, and WorldSpace Attest Browser Extension (for Chrome) 1.1 User Guide. For insight into its recent history and detailed comparison of the first two product generations that were available for its predecessor in the Mozilla Firefox browser only, see Original FireEyes vs FireEyes II Comparison.pdf.

Overview

Accessibility testing in Chrome Developer Tools with the WorldSpace Attest Devtools extension provides developers with a set of tools that help create accessible Web applications.

The extension:

  • Finds Defects: Allows for analysis using the WorldSpace Attest rule set to find a large number of the accessibility defects in a dynamic Web application.
  • Simulates Screen Readers: Provides screen reader simulation, to allow developers to read the linearized text of the application and quickly spot accessibility issues without needing to be a screen reader expert.
  • Uploads/Downloads To/From Comply: Integrates with the WorldSpace Comply server to allow for, upload and download of issues; recording, debug and playback of scripts; and recording of scope definitions.
  • Supports Custom Rulesets: Allows custom rules to be configured and interchanged with the WorldSpace Comply server. Providing consistency across the entire organization.

Uses, Users, and Rationale

This section describes what Attest is used for (project types), when it is used during those projects (phases), who uses it (roles), and why they use it (what they use it to accomplish).

Remediation

The primary use of Attest is in retro-fitting existing sites and apps to be accessible.

Accessibility Testing

QA Testers use Attest for:

  • Formal Manual QA Testing: Quickly check for some basic accessibility issues as a first step prior to manually following their test case scripts.

Managing Issues

QA Testers use Attest to:

  • Upload Issues & Scripts: Store and share information in WorldSpace Comply.
  • Download Issues & Scripts: Import information from WorldSpace Comply.
  • Export Analysis Results: Rule violation report data in .csv files for sharing and further manipulation.

Fixing Issues

Developers use Attest to:

  • Learn How to Fix Issues: Quickly determine where and what the issues are, and then get detailed issue and solution explanations from Deque University.
  • Fix Issues: See the issues in context within the browser, then test out fixes right away in the console.

Validating Issues

QA Testers use Attest to:

  • Validate Fixes: Assure the quality of the fixed code as a part of the re-testing process to validate issues are resolved.

Developers use Attest to:

  • Validate Fixes: After learning how to fix the issues, they use it again to check the effectiveness of the fixes and validate they got everything right.

New Construction

A secondary use of Attest is in building new sites and apps to be accessible from the ground up.

Front-End Development

Developers use Attest to:

  • Check Code for Machine-Detectible Issues: Analyzing their code against the automated accessibility rules engine in a browser context, and simulating how assistive technologies will read their page structure and content elements.
  • Learn How to Fix Issues: Learn about how to fix machine-detectible issues right away, taking advantage of remediation advice with code samples from Deque University.

Subtopics