Page Contents

Create Report (Run FAE)

Each report can evaluate up to 800 pages maximum. If your site contains over 800 pages, you may want to create multiple reports for different subdomains paths.

  1. Log in to the FAE service. You will be taken to a page to create a new report.
    Note: If you are not on this page. click the Run FAE link in the left menu.
  2. Enter an appropriate Starting URL into the text box to begin. The URL can either be a top level domain (e.g. or a subdomain with a path (e.g.
  3. Enter an appropriate report name into the Title field.
  4. For the Depth of Evaluation field, check the radio button to specify how many path levels down the report should evaluate.
  5. The Follow Links In parameter specifies whether the report should only include pages within the path or whether the report should evaluate content on a related domain.
    Note: For this selection, consider whether the related domain contains information under the control of your unit or not. When in doubt, you may be able to create a separate report for a different domain.
  6. Select an appropriate Ruleset based on whether you wish to evaluate your site for ARIA landmarks and components.
  7. Use the Evaluation Limited To option to control how many pages you wish to scan.
    Note: Reports with more possible pages will take longer to complete.
  8. Click the Evaluate button when you are ready to run the report. You will be taken to the Report Processing screen.
    Note: If the page does not change, you should confirm that all report options are correctly set and try again.

View Results (Summary)

These instructions allow you to view the Summary report listing all errors found on all pages within the scan.

  1. Log in to FAE as needed.
  2. If you do not see the report page, click the Report Processing or Archived Reports link in the left menu.
  3. Reports are listed in a table. If the Status of the report is set Completed, you can view the report.
  4. Click the title of the report to view results. Results are shown in a table classified by rule category and whether there is a violation, warning or manual check needed.

Interpret Results

To understand the meaning of a particular error, please refer to FAE Rulesets page. This page lists all the errors by category and links to a detailed description.

Additional information can be found at Blockers page.

Page Results

To view individual page results

  1. Make sure you have navigated to the Summary report following instructions in the section above.
  2. In the Reports menu, click All Pages to view a list of page reports. Click the title for any page to view a list of errors found with recommended fixes.
  3. Alternatively, you can click the Page 1 link, then use the Next and Prev links to go through reports page by page.

Note: Page reports only include a summary of errors found, but not necessarily details on where the error is located within the code. See the A-Inspector section to learn how to find location of errors.

Email Results

Both the Summary Report and individual page results may be emailed to one or more individuals.

  1. Navigate to the appropriate report.
  2. Click the E-mail Report link near the report title. An email message with a report link will be generated.
  3. Add appropriate people to receive the report.
    Note: This report link is publically available to anyone who has the URL.

Manage Reports

Number of Reports

Each user can store results from up to 80 reports, 40 of which can be archived permanently. If you create report 81, the oldest non-permanent report will be deleted. No permanent report will be deleted by the system.

Note: Each report can scan up to 800 pages.

Make a Report Permanent

  1. In the FAE interface, click the Manage Reports link in the left menu.
  2. Check the Perm option for any report you wish to be permanently archived.

Delete Reports

To delete a report

  1. In the FAE interface, click the Manage Reports link in the left menu.
  2. Make sure the Perm option is NOT checked for that report.
  3. Click the Delete button under the Action column for that report.


The AInspector toolbar provides a summary report of accessibility errors and recommended checks for a specific page, including a page which is password protected.

Note: AInspector does not currently work on the newest version of Firefox. We recommend installing Firefox ESR instead. For assistance, please read the Firefox ESR installation guide.

Install AInspector

Follow the instructions at the Installation Guide.

Find Flagged Code

See the Views and Rulesets documentation to parse the reports. To determine where in the HTML code an issue exists, follow the procedure below:

  1. Click the AI icon in the Firefox toolbar to run the report for the current page. A full list of findings categorized by category will be generated in the window on the left side.
  2. Click or double click a particular category to view results in that area.
  3. Double click any rule you need more information about. This opens the Details/Actions tab in the panel.
  4. Click the tab for Element Results to view a complete list of elements and their test status.
    Note: This tab is not available until steps #1-3 have been completed.
  5. Double click any element listed. The Firefox inspector tool will open the HTML view and navigate the cursor to the location in the page where the issue has been found.
    Note: If the page does not scroll down to that element, try double clicking then hitting the S key. This will cause the page to scroll to the selected element.

AInspector Example

A screen capture of AInspector, and how to find violations on a page.

The AInspector shows an image which is missing an ALT text. The file name is highlighted on the left in the toolbar, and the image itself is highlighted on the page.
Note: Nittany Bus Depot is a fictional company.

Other Testing Tools

FAE can be combined with other testing tools as needed depending on your issues. Below are some examples of tools that can be used with FAE.

Top of page