| WCAG Requirement |
References |
| 1.1.1 (Level A req.) |
Working with Alt Tags, Providing alternative text when ALT tags cannot be used, Using audio and video, Labeling text blocks and tables for proper association of information, Ensuring users can complete and submit tests, surveys, and forms |
| 1.2.1 - 1.2.5 (Level A and AA reqs) |
Using audio and video
|
| 1.3.1 (Level A req.) |
Labeling text blocks and tables for proper association of information, Ensuring users can complete and submit tests, surveys, and forms |
| 1.3.2 (Level A req.) |
Using the Title Explorer to configure object layering and reading order
|
| 1.3.3 (Level A req.) |
Author must design with this requirement in mind. |
| 1.4.1 (Level A req.) |
Author must design with this requirement in mind. |
| 1.4.2 (Level A req.) |
Using audio and video
|
| 1.4.3 (Level AA req.) |
Tools that can be used to access and measure color contrast
|
| 1.4.4 (Level AA req.) |
Lectora relies on browser capabilities to resize text. For details, see Browsers that support zooming on published content |
| 1.4.5 (Level AA req.) |
Author must design with this requirement in mind. For details, see Rendering a text block as an image |
| 2.1.1 – 2.1.2 (Level A reqs.) |
Using hyperlinks, buttons and other clickable objects, Using actions and integrating accessible interactivity, Checking for accessibility, Objects and actions that do not work with the keyboard |
| 2.2.1 (Level A req.) |
Take this requirement into consideration when using time-based objects and features within your titles such as timer progress bars, delayed actions, and timed tests. For details, see Specifying the type of progress bar, Delaying an action, Timing the Test, Allowing users to review and correct test questions before submission |
| 2.2.2 (Level A req.) |
Providing users a way to hide moving, flashing, or updating content
|
| 2.3.1 (Level A req.) |
Author must design with this requirement in mind. |
| 2.4.1 (Level A req.) |
Integrating methods for users to skip repetitive navigation, Using hyperlinks, buttons and other clickable objects |
|
2.4.2 (Level A req.) |
Changing the name of a chapter, section or page |
|
2.4.3 (Level A req.) |
Using the Title Explorer to configure object layering and reading order, Keyboard tabbing order and visual focus |
| 2.4.4 (Level A req.) |
Using hyperlinks, buttons and other clickable objects
|
|
2.4.5 (Level AA req.) |
Author must design with this requirement in mind. |
| 2.4.6 (Level AA req.) |
Specifying the HTML text type of a text block, Labeling text blocks and tables for proper association of information
|
| 2.4.7 (Level AA req.) |
Keyboard tabbing order and visual focus |
| 3.1.1 (Level A req.) |
Declaring the language for the title
|
| 3.1.2 (Level AA req.) |
Declaring the language for the text block
|
| 3.2.1 (Level A req.) |
The program produces HTML code that complies with this requirement. |
| 3.2.2 (Level A req.) |
Author must design with this requirement in mind. |
| 3.2.3 (Level AA req.) |
Using the Title Explorer to configure object layering and reading order, Integrating methods for users to skip repetitive navigation. |
| 3.2.4 (Level AA req.) |
Author must design with this requirement in mind.
|
| 3.3.1 – 3.1.3 (Level A & AA reqs.) |
Author must design with this requirement in mind. For details, see Ensuring users can complete and submit tests, surveys, and forms, Using hyperlinks, buttons and other clickable objects, Using actions and integrating accessible interactivity |
| 3.3.4 (Level AA req.) |
Allowing users to review and correct test questions before submission
|
| 4.1.1 – 4.1.2 (Level A reqs.) |
The program produces HTML code that complies with this requirement.
|