1.1.1 - All non-text content presented to the user has a text alternative that serves the same purpose.
1.4.1 - Color should not be used as the sole visual means of representing information, indicating actions, requiring responses, or as a visual differentiator.
1.4.3 - The visual representation of text and images of text must have a contrast ratio of at least 4.5:1.
1.4.5 - If technologies allow for the visual representation of content, text should be used to convey information rather than text images.
1.4.11 - In visual presentation, the contrast ratio is at least 3:1 against adjacent colors for:
1. User interface components
2. Graphical objects
1.3.3 - Instructions provided for understanding and operating content should not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.
2.4.4 - The purpose of each link can be determined from the link text alone or from the link text combined with contextual content that can be determined programmatically, unless the purpose of the link could be ambiguous to users in general.
3.3.3 - If an input error is identified and suggestions for correction are known, those suggestions are provided to the user, unless doing so would compromise the security or purpose of the content.
3.3.4 - For web pages containing legal constraints or financial transactions for users who manage the modification or deletion of data controlled by the user in a storage system, or who submit user responses to tests, at least one of the following conditions must be met:
Reversibility: Actions are reversible.
Control: User-entered data is verified, and the user is given the opportunity to correct errors.
Confirmation: A mechanism for reviewing, confirming, and correcting information before final submission is available.
1.3.2 - When the sequence in which content is presented affects its meaning, the correct reading order can be determined programmatically.
1.4.12 - In content implemented using markup languages that support the following text styling properties, no content or functionality is lost when setting the following without modifying other style properties:Line height (leading) at least 1.5 times the font size.Spacing after paragraphs at least 2 times the font size.Letter spacing at least 0.12 times the font size.Word spacing at least 0.16 times the font size.
2.4.6 - Use headings and labels to describe topics or purposes.
4.1.2 - For all user interface components (including but not limited to: form elements, links, and script-generated components), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notifications about changes in state of these elements are made available to user programs, including assistive technologies.
2.1.1 - All functionality of the content must be operable through a keyboard interface without requiring specific timing for individual key presses, unless the functionality fundamentally requires input based on the user’s path of movement and not just its end points.
2.4.1 - A mechanism is available to skip repetitive content across multiple web pages.
1.4.13 - In cases where mouse hover or keyboard focus makes content visible or hidden, the following conditions must be met:
Dismissable: A mechanism is available to dismiss the extra content without moving the mouse pointer or keyboard focus, unless the extra content communicates an input error or obscures or replaces other content.
Accessible: If mouse hover can trigger additional content, the mouse pointer can move over the extra content without it disappearing.
Persistent: Extra content remains visible until the hover or focus event is removed, the user dismisses it, or the information is no longer valid.
4.1.2 - For all user interface components (including but not limited to: form elements, links, and script-generated components), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notifications about changes in state of these elements are made available to user programs, including assistive technologies.
4.1.3 - In content implemented using markup languages, status messages can be programmatically determined via role or property, so they can be presented to the user through assistive technologies without receiving focus.
2.5.3 - For user interface components with labels that include text or images of text, the name contains the text presented visually.