Testing for Subheadings using the Functional Accessibility Evaluator

Overview

The Functional Accessibility Evaluator (FAE) is an online tool that you can use to analyze web pages in accordance with HTML Best Practices under WCAG, Section 508, and the Illinois Information Technology Accessibility Act.

You can register for a free account to run sitewide reports and save those reports.

Strengths

  • Gives Immediate feedback on nesting.
  • Checks for text content within heading tags.
  • Gives Severity notification via Pass/Warning/Fail
  • Can sign-up/login to track progress and run site-wide reports.

Weakness

  • Relies upon human checking for 4/7 rules.
  • No feedback on where in the code the error(s) are.

Step 1: Running the report on a single web page.

Procedure

  1. Enter the URL of the web page to check on the FAE request form

Screenshot

Screen shot of Running the report on a single web page.

Step 2: FAE Summary Report

Procedure

FAE will return a summary with two sections:

  • Evaluation Results by Best Practices Main Category
  • Evaluation Results by Best Practices Subcategory

To see more information about Subheadings

  1. Look at the Navigation & Orientation Subcategory under the Evaluation Results by Best Practices Subcategory.
  2. Examine the row Subheadings (h2..h6) for % Pass, % Warn, and % Fail. This indicates the web page’s success ratio in this subcategory.
  3. For more information click on the “Subheadings (h2..h6)” link to get details about rule violations for a web page or the page information for a web website.

Screenshot

Screen shot of FAE Summary Report

Step 3: FAE Page Report Pass

Procedure

  • The Page Report will provide details on specific rules. In this instance all rules have been satisified.
  • In the next step we will investigate a web page that fails these checks

Screenshot

Screen shot of FAE Page Report Pass

Step 4: FAE Page Report Fail

Procedure

  • This is an example of a web page that receives fails or warns on the three of the FAE‘s section on Subheadings (h2..h6).
  • You can use the Best Practices link to find more information about the reasons you may have failed the Subheadings (h2..h6) sub category.

Screenshot

Screen shot of FAE Page Report Fail

Rules Evaluated with this Technique

Rules evaluated with Functional Accessibility Evaluator
Test
Type
Description
Undefined

Each section of a web page must have a heading and the heading must describe content of the section.

Automatic

Heading elements that follow the last h1 element must be properly nested.

Automatic

All subheadings (h2…h6) must contain text content.

Undefined

Sub haedings of the same level should have content between the headings

Undefined

The text content of headings of the same level within the same section should be unique.

Automatic

The text content of an subheading element (h2-h6) should not only come from the alt attribute value of img elements.

Undefined

The text content of headings should be concise (less than 65 characters).