Visual Headings - visual heading not defined programmatically

Test Case Summary

TC13.2-1.c-fail-1

Visually apparent heading is not a programmatic heading.

A successful test should identify a FAIL against Baseline 13.2 Visual Headings.

Baseline Test ID: 13.2-VisHeadingProg

Test Instruction: 1.c

FAIL

The “Classical Period” heading in the code sample is not defined as a heading programmatically.

Test Instruction	Instruction Detail	Expected Test Case Result
IC-1	Visually apparent headings, which denote sections of content. Headings are often in a larger, bolded font separated from paragraphs by extra spacing (though not always). Note the hierarchy and structure of each heading with respect to other headings on the page.	Visual apparent headings found.
13.2-1	Check that all visual headings are programmatically determinable and that programmatic heading levels logically match the visual heading presentation within the heading structure [SC 1.3.1].
13.2-1.a	The most important heading(s) should have the highest priority level. For example, `<h1>` is a higher level than `<h2>`, which is higher than `<h3>`.	Pass: The `<h1>` heading is higher than the other `<h2>` headings.
13.2-1.b	Headings with an equal or higher level start a new section; headings with a lower level start new subsections that are part of the higher leveled section.	Pass: the visual hierarchy of the headings are correct
13.2-1.c	HTML or ARIA programmatically identify each heading. When both are used, heading levels must match. H42: each heading is marked with `<h1>` to `<h6>`. ARIA12: each heading is marked with `role="heading"` and `aria-level="#"`. The default heading level is “2” when none is specified.	Fail: a visual heading is not programmatically identified with HTML or ARIA
Result	If the above check fails, then Baseline Test 13.2-VisHeadingProg fails.	FAIL; 13.2-1.c fails