Category: Structure
Tests about the theme and the appropriate use of HTML markup.
| 14 | 1.3.1 Info and Relationships (A) | Landmarks present on the page are used to organize the correct type of content. |
|---|---|---|
| 15 | 1.3.1 Info and Relationships (A) | Wherever text appearance (i.e., bold, italics, underline, size) is used to convey information, that information must also be presented in text alone. |
| 16 | 1.3.1 Info and Relationships (A) | Headings must follow appropriate relative hierarchy to other headings on the same page. |
| 17 | 1.3.1 Info and Relationships (A) | Page structure is implemented with HTML. Visual appearance is implemented with CSS. Meaningful HTML is not used to solely achieve a visual effect or appearance. |
| 22 | 1.3.1 Info and Relationships (A) | All elements with semantic roles contain all required parent and child elements. (e.g., a "list" must contain "listitem"). |
| 23 | 1.3.1 Info and Relationships (A) | Element IDs do not repeat more than once per page. |
| 25 | 1.3.2 Meaningful Sequence (A) | The order in which content is presented in DOM must be logical. |
| 59 | 2.4.5 Multiple Ways (AA) | Two or more mechanisms of finding a webpage are available, unless the page is accessed as part of a step in a process. |
| 71 | 3.1.1 Language of Page (A) | The default language of each page must be defined in the html tag. |
| 72 | 3.1.2 Language of Parts (AA) | Text in a different language than the page default must be identified in HTML; aside from proper names, technical terms, words without a defined language, and words that are part of the vernacular of the immediately surrounding text. |
| 75 | 3.2.3 Consistent Navigation (AA) | Navigations which are utilized on multiple pages keep the same relative order on all pages, unless the user initiates the change. (Items can be removed or added, but they must maintain the same order relative to each other) |
| 76 | 3.2.4 Consistent Identification (AA) | Any components with similar functionality used on multiple pages must be labeled identically and function identically. (e.g. a header Search field must be labeled the same on all pages) |
| 77 | 3.2.6 Consistent Help (A) | Help mechanisms such as contact details, messaging, chat, or self-help options must be in the same relative order on all pages where the information is present. |
| 87 | 4.1.2 Name, Role, Value (A) | All elements have appropriate accessible names and roles assigned. |
| 89 | 4.1.2 Name, Role, Value (A) | All custom functionality utilizes the appropriate ARIA features for states, properties, and values. (e.g. aria-expanded, aria-haspopup) |