90 docs tagged with "WCAG 2.2"

The action triggered on down-events should be reversible by the up-event.

The functionality that relies solely on device motion should have an alternative input method.

All the functionality requiring multipoint gestures should have alternative controls.

All the functionality requiring path-based gestures should have alternative controls.

The prerecorded video-only content should have an alternative that provides equivalent information.

The sound that plays automatically and lasts longer than 3 seconds should have a control to turn it off.

The video should include an audio description for visual information not conveyed in the audio track.

The action should provide a cancel mechanism during interaction or an undo option after completion to ensure users can reverse unintended actions.

The captions for live video content should fully and accurately reflect the spoken text and include meaningful sound effects.

The captions for prerecorded video content should fully and accurately reflect the spoken text, be in the same language, and include meaningful sound effects.

The live video content should include captions.

The prerecorded video content should include captions.

The customized focus indicator should not rely solely on color presentation.

The color of the element should not be the only cue to convey information.

The column index should accurately reflect its position within the sequence.

The column should have a column index that is communicated to assistive technologies.

The content on the screen should rotate from landscape to portrait orientation.

The content on the screen should rotate from portrait to landscape orientation.

The mechanism should be provided to pause, stop, or hide content that moves, blinks, or scrolls for more than five seconds.

The large text should have a contrast ratio of at least 3.0:1 against its background.

The normal text should have a contrast ratio of at least 4.5:1 against its background.

The large text should have a contrast ratio of at least 3.0:1 against its background.

The normal text should have a contrast ratio of at least 4.5:1 against its background.

All the elements receiving keyboard focus should have a distinct and visible focus indicator.

The decorative non-text content should be hidden from assistive technologies.

The error message associated with the input should be presented in text, clearly describing what went wrong.

The user should have an opportunity to review, confirm, or correct the entered information before it becomes final when submitting legal, financial, or data-related interactions.

The heading should clearly describe the topic or purpose of the related content.

The heading text should be marked up as a heading.

The image should be marked up as an image.

The screen reader focus should start on the first element on the screen.

The name of an interactive element should accurately describe its function or purpose.

The interactive element should have a name.

The role of an interactive element should match its function.

The interactive element should have a role.

The state of an interactive element should accurately reflect its current condition.

The interactive element should have a programmatically determinable state.

The value of an interactive element should accurately reflect its current content or setting.

The interactive element should have a programmatically determinable value.

All the interactive elements should be focusable with a keyboard interface.

The interface element should have a contrast ratio of at least 3.0:1 against its background.

The single character key shortcuts should either be able to be turned off, remapped to a non-singular key shortcut, or activated only when the appropriate user interface component has focus.

The keyboard focus indicator should have a contrast ratio of at least 3.0:1 against its background.

The keyboard focus should go directly to the next visible interactive element with each keystroke in a sequential navigation.

All the interactive elements on the screen should be included in the keyboard focus order.

The keyboard focus should remain within modals or dialogs until closed.

The label of an interactive element, presented as text or an image of text, should match or be included in its accessible name.

The text written in a language different from the app's primary language should be programmatically marked with the correct language.

The app's language should be correctly set to ensure assistive technologies apply accurate pronunciation rules.

The purpose of the link should be clear.

The list items should be separately focusable when using assistive technologies.

The map should have a text alternative.

All the meaningful elements should be focusable using an accessibility interface.

The action should be triggered only on the up-event unless activating on the down-event is essential.

The status messages should not receive focus automatically without user interaction.

The context changes should only occur as a result of intentional user interaction, not solely by receiving focus.

The context changes should only occur as a result of intentional user interaction, not solely by receiving focus.

No content that flashes more than three times per second should be displayed.

All the parts of the screen, such as modals or menus, can be closed or exited using a keyboard interface.

All parts of the screen, such as modals or menus, can be closed or exited using a screen reader.

The context changes resulting from component setting adjustments should only be triggered after explicit user actions, or users should be warned about the change.

The label of meaningful non-text content should clearly, accurately, and fully describe its meaning.

The meaningful non-text content should have a label.

The paragraphs in the text should be separately focusable when using assistive technologies.

The reading order of elements announced by assistive technologies should match the visual order.

The elements that belong together must be presented together by assistive technologies.

The related elements should be properly linked so that their relationship can be conveyed to assistive technologies.

The row index should accurately reflect its position within the sequence.

The row should have a row index that is communicated to assistive technologies.

The text should not become hidden, disappear, or extend outside its containers when scaled up to 200%.

The text should not be overlapped or obscured by other text or content when scaled up to 200%.

The text should not be replaced with ellipses (...) or truncated when scaled up to 200%.

The focus should go directly to the next visible element with each swipe in a sequential navigation.

All the meaningful elements on the screen should be included in the screen reader focus order.

The focus should remain within modals or dialogs until closed.

The sensor-based cues such as haptics, shape, size, visual location, orientation, or sound should not be the only cue to convey information.

The sequence of events in a timeline or steps in a process should be conveyed to assistive technologies.

The status message should be announced by assistive technologies.

The error message associated with the input should describe suggestions on how to correct the error.

All interactive elements should have a minimum target size of at least 44 by 44 points.

All interactive elements should have a minimum target size of at least 24 by 24 points.

The text alternative for audio-only or video-only content should include all meaningful audio or visual information, such as critical sound effects, music, or visual details.

The prerecorded audio-only content should have a text alternative that provides equivalent information.

The text alternative should be provided for important visual information in the video that is not explained in the audio and for which no audio description is available.

The text should be presented as plain text, not as an image of text.

The text should scale properly when scaled up to 200%.

All the time-limited content can be paused, stopped, or extended.

The time limits for completing tasks should be adjustable, allowing users to pause, stop, or extend them as needed.

The label should clearly describe the topic or purpose of the related element.

The input field should have a label visible at all times.