WCAG 3 Audit Calculator

[Title, role, or organization] asserts that: * We provide an audio player that supports appropriate media alternatives. The audio player includes the following features [list all that apply]: * turning audio descriptions on and off * changing the language of the audio descriptions

[Title, role, or organization] asserts that: * We provide a video player that supports appropriate media alternatives. The video player includes the following features [list all that apply]: * supports closed captions in a standard caption format * turning captions on and off * turning audio descriptions on and off * adjusting caption styles, including but not limited to: font size, font weight, font style, font color, background color, background transparency, and placement * changing the location of captions * changing the language of the audio descriptions

A mechanism is available that allows users to change the audio description language if multiple languages are available.

A mechanism is available that allows users to control the audio description volume independently from the audio volume of the video.

Audio descriptions are available in live video for visual content needed to understand the media.

Audio descriptions are available in prerecorded video for visual content needed to understand the media.

A mechanism is available to turn audio descriptions on and off.

The information conveyed by audio descriptions is equivalent to the visual content needed to understand the media.

[Title, role, or organization] asserts that: * We have reviewed the audio descriptions. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of the review * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * role of the creator * number of creators (for each Role) * date (Period) of review * examples of fixed issues based on the review

[Title, role, or organization] asserts that: * Our organization has a style guide that includes guidance on audio descriptions and a policy and/or processes that the style guide must be followed. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of when the style guide was published * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * summary of the needs of users involved * identified issues and details of solutions applied * copy or snapshot of the style guide

Audio descriptions are synchronized with video content without overlapping dialogue and meaningful audio content.

[Title, role, or organization] asserts that: * We have conducted usability testing with users who need audio descriptions, and changes were made to fix or mitigate the issues found. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of when the usability testing was conducted * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * scope * types of disabilities each user had * number of users (for each type of disability) * date of testing * identified issues and details of solutions applied

The video pauses to extend the audio track and provides an extended audio description to describe visual information needed to understand the media.

The information conveyed by extended audio descriptions is equivalent to the visual content needed to understand the media.

Nonverbal cues needed to understand the media are explained in audio descriptions.

Sounds needed to understand the media are identified or described in captions and transcripts.

When more than one language is spoken in audio content, the language spoken by each speaker is identified in all audio descriptions.

Speakers are identified understandably within all audio descriptions.

Visual information needed to understand the media is described in audio descriptions.

Enhanced features that allow users to interact with captions are available.

A mechanism is available that allows users to change the caption language if multiple languages are available.

The appearance of captions, including associated visual indicators, is adaptable including font size, font weight, font style, font color, background color, background transparency, and placement.

Captions are available for all live audio content.

Captions are available for all prerecorded audio content.

In 360-degree digital environments, captions remain directly in front of the user.

Captions are presented consistently throughout the media, and across related productions, unless exceptions are essential. This includes consistent styling and placement of the captions text and consistent methods for identifying speakers, languages, and sounds.

A mechanism is available to turn captions on and off.

Equivalent captions are available for audio and video content.

[Title, role, or organization] asserts that: * We have reviewed the captions. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of the review * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * role of the creator * number of creators (for each Role) * date (Period) of review * examples of fixed issues based on the review

[Title, role, or organization] asserts that: * Our organization has a style guide that includes guidance on captions and a policy and/or processes that the style guide must be followed. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of when the style guide was published * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * summary of the needs of users involved * identified issues and details of solutions applied * copy or snapshot of the style guide

Captions are synchronized with the audio content of synchronized media.

Captions are placed on the screen so that they do not hide visual information needed to understand the video content.

[Title, role, or organization] asserts that: * We have conducted usability testing with users who need captions, and changes were made to fix or mitigate the issues found. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of when the usability testing was conducted * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * scope * types of disabilities each user had * number of users (for each type of disability) * date of testing * identified issues and details of solutions applied

In 360-degree digital environments, the direction of a sound or speech is indicated when audio is heard from outside the current view.

Nonverbal cues needed to understand the media are explained in captions.

Sounds needed to understand the media are identified or described in captions.

When more than one language is spoken in audio content, the language spoken by each speaker is identified in all captions.

Speakers are identified understandably within all captions.

Figure captions persist or a mechanism is available to make figure captions persist, even if the focus moves away.

Automatically generated text descriptions are editable by the content creator.

Decorative images are programmatically hidden.

Text alternatives are available for non-decorative images.

Text alternatives for non-decorative images convey the equivalent purpose to the image.

[Title, role, or organization] asserts that: * Our organization has a style guide that includes guidance on image text alternatives and a policy and/or processes that the style guide must be followed. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * section labels relevant to image alternatives * copy or snapshot of the style guide

The image types are indicated.

Non-decorative images are detectable.

All non-text content that is not decorative includes a programmatically determinable equivalent text alternative.

Sign language interpretation is provided for all prerecorded audio content in the primary sign language that is most appropriate for each intended audience or region.

A mechanism is available to show and hide sign language interpretation.

[Title, role, or organization] asserts that: * Our organization has a policy to provide sign language interpretation for live in-person, hybrid, and fully online events/meetings. ::assertion-required * title, role, or organization making the assertion (with contact information) * date of assertion (if different from the date of the conformance claim) * date the policy was last reviewed/updated * how sign language interpretation can be requested * format: email, phone, contact form * timeline/deadline for requesting (maybe just the average timeline) ::assertion-recommended * approved vendors and contact information * steps for hosting on each platform used * versioned communications guide for announcing sign language availability for each meeting/event

Parts of graphical objects required to understand the content meet a minimum contrast ratio test

Information is not conveyed by hue alone.

Information is not conveyed by sound alone.

Information is not conveyed by spatial audio alone.

Information is not conveyed through visual depth perception alone.

Descriptive transcripts are provided for prerecorded audio and video content.

Dialogue transcripts are available for all live audio and video content.

Dialogue transcripts are available for all prerecorded audio and video content.

Nonverbal cues needed to understand the media are explained in transcripts.

Sounds needed to understand the media are identified or described in transcripts.

When more than one language is spoken in audio content, the language spoken by each speaker is identified in all transcripts.

Speakers are identified understandably within all transcripts.

Equivalent transcripts are available for audio and video content.

A text transcript is adjacent to audio and video content.

[Title, role, or organization] asserts that: * We have reviewed the transcripts. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of the review * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * role of the creator * number of creators (for each Role) * date (Period) of review * examples of fixed issues based on the review

[Title, role, or organization] asserts that: * Our organization has a style guide that includes guidance on transcripts and a policy and/or processes that the style guide must be followed. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of when the style guide was published * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * summary of the needs of users involved * identified issues and details of solutions applied * copy or snapshot of the style guide

[Title, role, or organization] asserts that: * We have conducted usability testing with users who need transcripts, and changes were made to fix or mitigate the issues found. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of when the usability testing was conducted * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * scope * types of disabilities each user had * number of users (for each type of disability) * date of testing * identified issues and details of solutions applied

Visual information needed to understand the media is described in transcripts.

Explanations of abbreviations are available when first used.

[Title, role, or organization] asserts that: * Our organization has a process and policy to review text content for clear language before publication. The process includes confirming: * All of the core requirements in the ‘Clear Language’ guideline are met. * Verb tense is chosen for ease of understanding. * Content uses short paragraphs. * Paragraphs that convey information begin with a sentence stating the main point or purpose (often called a topic sentence). * If a style guide is used by content authors, it must provide guidance on these aspects of clear language. * If author training is provided, it must provide guidance on these aspects of clear language. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of when the policy was implemented * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * copy of the policy implementing the clear language review * date author training was provided (if any) * number or proportion of authors who completed the training * copy of the style guide (if any) where clear language review has been defined

Common words are used, and definitions are available for uncommon words.

Diacritics required to identify the correct meaning of each word are available.

Sentences do not include nested clauses.

Sentences do not include unnecessary words.

Explanations or unambiguous alternatives are available in text content for non-literal language, such as idioms and metaphors.

Explanations or alternatives are provided for complex numerical information such as statistics.

A summary is available for long-form text content and: * is identifiable visually and programmatically, * uses concise sentences, and * provides access to explanations of any uncommon words that are used in the summary.

[Title, role, or organization] asserts that: * Our organization has a process and policy for reviewing text content to identify complex ideas such as processes, workflows, relationships, or chronological information, and adding visual aids to help readers understand them. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of when the policy was implemented * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * copy of the policy implementing the use of visual aids * date author training was provided (if any) * number or proportion of authors who completed the training * copy of the style guide (if any) where visual aids have been defined

The presentation of blocks of text can be adjusted, without loss of content or functionality, to meet the [values to be determined] for: * inline margin * block margin * line length * line height * justification

The default/authored presentation of blocks of text meets the enhanced [values to be determined] for: * inline margin * block margin * line length * line height

The default/authored presentation of blocks of text meets the minimum [values to be determined] for: * inline margin * block margin * line length * line height

The foreground and background color of text can be adjusted without losing content or functionality.

The default visual presentation of text meets [contrast measure to be determined, at a higher level than the core requirement for Text contrast sufficient (minimum)].

The default visual presentation of text meets [contrast measure to be determined].

Content that is exported, saved, or printed retains user-applied text-appearance customizations.

Text can be increased in size to at least 200% of the platform’s default body-text size.

The presentation of text style properties can be adjusted, without loss of content or functionality, to meet the [values to be determined] for: * typeface * font width * text decoration * capitalization * automatic end-of-line hyphenation

The default/authored presentation of text style properties meets the enhanced [values to be determined] for: * typeface * font size * font width * text decoration * letter spacing * capitalization * end-of-line hyphenation

The default/authored presentation of text style property meets the minimum [values to be determined] for: * typeface * font size * font width * text decoration * letter spacing * capitalization * end-of-line hyphenation

The human language of all content within the view is programmatically determinable.

Numerical information includes sufficient context in written text and a programmatic equivalent to avoid confusion when presenting dates, temperatures, time, and Roman numerals.

Meaning conveyed by text style properties is also programmatically determinable.

All visible text has a programmatically determinable equivalent.

Changes to interactive element names, roles, values, or states are visually and programmatically indicated.

Field constraints and conditions are available.

Visual information required to identify interactive elements and states meet a minimum contrast ratio test.

The importance of interactive components is indicated.

Persistent names (including labels) that identify the purpose of the interactive element are visually and programmatically available.

Interactive elements are visually distinguishable without interaction from static content and include visual cues on how to use them.

The programmatic name includes the visual label.

Accurate names, roles, values, and states are available for interactive elements.

Where an interactive element with the same purpose is used across pages/views, its visual position in the layout is maintained.

[Title, role, or organization] asserts that: - A review has been conducted and changes made (when necessary) to ensure that Components with the same functionality behave consistently: - Components that perform the same function behave in the same way and use the same visual indicators. - Within the component, interactive elements with the same function have consistent labels. - Standard user interface designs for the platform are used when applicable. ::assertion-required - title, role, or organization making the assertion (if different from the conformance claim) - date of when the review was completed - date of assertion (if different from the date of the conformance claim) ::assertion-recommended - results from the review - process or policy for maintaining the review

[Title, role, or organization] asserts that: - A review has been conducted and changes made (when necessary) to ensure that Components follow established conventions: - Each component follows applicable platform conventions for how users interact with that type of component. - If a component library is used, then each component in the library: - is tested for accessibility before being used - follows applicable platform conventions for how users interact with that type of component ::assertion-required - title, role, or organization making the assertion (if different from the conformance claim) - date of when the review was completed - date of assertion (if different from the date of the conformance claim) ::assertion-recommended - results from the review - process or policy for maintaining the review

The focusable item uses the user agent default focus indicator.

If a custom focus indicator is used, it has sufficient adjacent contrast and change of contrast.

If a custom focus indicator is used, it has sufficient size and adjacency.

[Title, role, or organization] asserts that: - Our organization has a style guide that includes guidance on focus indicators and a policy and/or processes that the style guide must be followed. ::assertion-required - title, role, or organization making the assertion (if different from the conformance claim) - date of when the design style guide was published - date of assertion (if different from the date of the conformance claim) ::assertion-recommended - copy of the policy implementing the use of design style guide on focus style - whether training was provided for authors - date training was provided - number or proportion of authors who completed the training - copy of the design style guide (if any) where focus style has been defined

The keyboard focus moves sequentially through content in an order and way that preserves meaning and operability.

The focus order does not include hidden, static, or groups of repeated interactive elements.

A user can focus on a content "area", such as a modal or popup, then resume their view of all content using a limited number of steps.

The user can ensure that the appearance of the pointer is not overridden by the authored interface.

Provide a more visible pointer indicator than the platform default. The enhanced pointer indicator can be enabled in a setting, and be visible temporarily (for a few seconds) or permanently.

The user can choose to always have a visible pointer indicator.

There is a visible indication of the activation of an interactive element when selected by the pointer.

The default pointer meets the [non-text-contrast] requirement, and is at least as large as the platform default.

There is a visible pointer indicator.

The pointer indicator is always visible.

Biometric identification is not the only way to identify or authenticate.

Authentication does not rely solely on a single type of biometrics.

Voice identification is not the only way to identify or authenticate.

Functionality does not rely solely on full or gross body movement.

Content and functionality does not rely solely on eye tracking.

If pointer hover can trigger content, then the pointer can be moved over the additional content without the additional content disappearing.

A mechanism is available to dismiss content that appears on pointer hover or keyboard focus without moving pointer hover or keyboard focus, unless the additional content does not obscure or replace other content.

Content that appears on pointer hover or keyboard focus remains visible until the hover or keyboard focus trigger is removed, the user dismisses it, or its information is no longer valid.

The ability to switch between input methods is available at any time.

Path-based gestures are not the only way of achieving any functionality.

Pointer selection of elements moves the keyboard focus to that element, even if the user selects an interactive element and drags away from the element without activation.

The keyboard interface can always move forward to the next interactive element and back to the previous interactive element.

Documentation for each custom keyboard command is actively available on the page/view to which it applies, or within the applicable process.

Except for skip links and other elements that are hidden but specifically added to aid keyboard navigation, tabbing does not move the keyboard focus onto content that was not visible before the tab action.

When keyboard focus moves from one context to another within a page/view, whether automatically or by user request, the keyboard focus is preserved so that, when the user returns to the previous context, the keyboard focus is restored to its previous location unless that location no longer exists.

The keyboard focus only moves as a result of user interaction.

All content that can be accessed by other input modalities can be accessed using keyboard interface only.

All components on the page/view that can be operated by pointer, audio (voice or other), gesture, camera, or other means can be operated using keyboard interface only.

Custom keyboard commands do not conflict with standard platform keyboard commands or they can be remapped.

Components that can be activated or entered using the keyboard interface, can be deactivated or exited using a standard keyboard navigation-operation technique, standard platform keyboard commands.

[Title, role, or organization] asserts that: - A review has been conducted and changes made (when necessary) to ensure that there is minimal difference between the number of input commands required when using the keyboard interface only and the number of commands when using other input modalities.

If any keyboard action needed to navigate, perceive, and operate the full content of the page/view is not a common keyboard navigation technique, then it is described in the page/view where it is required or on a page/view earlier in the process where it is used.

Adjacent interactive elements that achieve the same outcome are not included in the page/view.

The method of pointer cancellation is consistent for each type of interaction within a set of pages/views.

At least one of the following is true for functionality that can be activated using a simple pointer input: No down event : The down event of the pointer is not used to execute any part of the function. Cancel or undo : Completion of the function is on the up event and a mechanism is available to cancel the function before completion, or there is a mechanism to undo the function after completion. Up reversal : The up event reverses any outcome of the preceding down event.

Specific pointer pressure is not the only way of achieving any functionality.

Functionality does not rely solely on specific pointer speed.

All functionality and content available using complex pointer inputs is also available using a simple pointer input, or a sequence of simple pointer inputs that do not require timing.

[Title, role, or organization] asserts that: - We have tested voice input and communication systems with generated speech to ensure the systems work with artificial speech as well as human speech. ::assertion-required - title, role, or organization making the assertion (if different from the conformance claim) - date of when the policy was implemented - date of assertion (if different from the date of the conformance claim) ::assertion-recommended - systems tested - accuracy rates

A real-time text option is available for real-time bidirectional voice communication.

Content or functionality does not rely on speech alone.

Error messages are visually collocated with the error source or the focus is moved to the error message and a mechanism is available to move to the input that is in error.

Error messages persist at least until the error is resolved or the user dismisses them.

Errors that are programmatically determined are identified and the problem is described to the user in text.

Error messages include suggestions for corrections.

When input validation fails, the errors are visually and programmatically associated with the element that caused the error or that can resolve it.

Error messages are visually indicated using at least two of the following: * a symbol that is consistent throughout the conformance scope * color that differentiates the error message from surrounding content * a textual indication

Data entered is validated after the user enters data, either: * when the user leaves the field, or * when the form is submitted

[Title, role, or organization] asserts that: * For each form in the conformance claim, we have reviewed the form designs to reduce the possibility of users making mistakes. This review includes checking to make sure that we: * Make the user enter as little information as possible. * Clearly indicate required fields. * For long numbers, divide input fields into chunks (supporting autocomplete across fields). * Use an interface where only valid input can be selected. * Use autocomplete and personalization of form controls. * Use common words and metrics or units that users are likely to be familiar with. * Automatically correct input errors when possible and reliable. * Provide the user with known suggestions and corrections. ::assertion-required * title, role, or organization making the assertion * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * documentation of which forms were reviewed * documentation of any changes made as a result of the review * date of usability testing, if applicable

Data entry interfaces allow for users to do at least one of the following before submission: * Review, confirm, and correct all information. * Review and correct input errors found during validation.

Data entry interfaces notify users of submission status at the time of submission.

Audio shifting designed to create a perception of motion can be paused or turned off.

Haptic feedback can be reduced or turned off.

Flashes are below the general flash and red flash thresholds without a minimum size.

Flashes are below the general flash and red flash thresholds.

Content does not include pseudo-motion or visual motion lasting longer than 5 seconds.

Content does not include pseudo-motion or visual motion lasting longer than 5 seconds.

[Title, role, or organization] asserts that: * We have reviewed content for violent, explicit, or troubling content and provided appropriate warnings before accessing the content. ::assertion-required - title, role, or organization making the assertion (if different from the conformance claim) - date of when the review was conducted - date of assertion (if different from the date of the conformance claim)

Content does not include a change of contrast (over 4.5:1) going from light to dark (or dark to light) of more than 30% of the visible content area (viewport).

A warning is provided before users encounter triggers and a mechanism is available to access the same information without the triggering content.

Visual stimulation from combinations of density, color, movement, etc. can be reduced or turned off.

Where content includes infinite scrolling, a mechanism is provided prior to the scrolling content that allows users to switch off infinite scrolling. No content should be rendered unavailable as a result of switching on this option.

When new content becomes visible and covers the main content, a mechanism is available to dismiss the new content.

[Title, role, or organization] asserts that: * We have reviewed layout conventions for similar products or processes. * The layout used follows a conventional pattern or a tested non-conventional pattern was used. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * report covering review of layouts for similar products or processes * design log capturing decision to use specific layouts * if a non-conventional layout is used, usability testing results that demonstrate the utility of the approach taken

Styling is used to enhance the visual separation between meaningful blocks of content.

Meaningful blocks of content are programmatically determinable and visually presented with sufficient surrounding space.

[Title, role, or organization] asserts that: * Our organization has a process and policy for reviewing written content for clear structure before publication. The process includes confirming: * all of the core requirements in the Structure guideline are met * content sections are as concise as possible * icons are considered as possible ways to help users understand the content structure and identify key parts * authors consider when to turn sentences into lists to make the information easier to understand and remember * If a style guide is used by authors, it must provide guidance on these aspects of clear structure. * If author training is provided, it must provide guidance on these aspects of clear structure. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of when the policy was implemented * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * copy of the policy implementing the clear structure review * whether training was provided for authors: * date training was provided * number or proportion of authors who completed the training * copy of the style guide (if any) where clear structure review has been defined

Meaningful blocks of content are organized with a logical hierarchy of headings.

[Title, role, or organization] asserts that: * We conducted usability testing to ensure that a diverse group of users, including people with cognitive and mental health challenges, understand the site's information hierarchy and menu organization and are able to find key information. ::assertion-required * title, role, or organization making the assertion * date of assertion * date of the testing ::assertion-recommended * documentation of usability testing and results * scope of testing * number of participants and disabilities represented * documentation of changes made as a result of usability findings

Ordered content includes programmatically determinable markers that indicate the position of each item.

Relationships of meaning between elements are conveyed programmatically.

Meaningful blocks of content have a semantically appropriate label that defines their purpose.

A list of all steps in a multi-step process is visually and programmatically available at each step.

The current step within a multi-step process is visually and programmatically indicated.

[Title, role, or organization] asserts that: * We have reviewed conventions for presenting current location within the conformance scope. * The presentation of current location within the conformance scope uses appropriate visually and programmatically patterns.

When content triggers a change of page/view there is a visual change within the view and programmatic notification of the change.

The page/view has a title that describes its name, topic, or purpose.

A visual and programmatically available mechanism exists that allows users to return to the starting point of the conformance scope.

The labeling of navigation items within blocks of navigation that are repeated on multiple pages/views in the conformance scope or process is consistent.

The relative order of navigation items is consistent within blocks of navigation that are repeated on multiple pages/views of the conformance scope or process.

The relative order of structural components remains consistent throughout each variation of pages/views in the conformance scope.

The completion of a process does not include time limits.

[Title, role, or organization] asserts that: * Products and processes in scope have no non-essential time limits for engagement or completion. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of assertion

Users are informed at the start of the process or session that a time limit exists, its length, and that it can be adjusted.

A mechanism exists to extend the time limit before timeout, or the time limit can be disabled.

[Title, role, or organization] asserts that: * We conducted a usability test that included participants with cognitive disabilities and/or mental health based disabilities to evaluate content for misleading wording, artificial pressure, misdirection, and other deceptive practices. * We removed any deceptive practices found. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of assertion ::assertion-recommended * number of participants * the deceptive practices evaluated * maintained records of usability testing protocol, and results * disabilities represented within the group of participants

[Title, role, or organization] asserts that: * We conducted an expert review to evaluate content for misleading wording, artificial pressure, misdirection, and other deceptive practices. * We removed any deceptive practices found. ::assertion-required * title, role, or organization making the assertion * date of assertion ::assertion-recommended * the deceptive practices evaluated * maintained records of deceptive practices found, and resolutions

The completion of a process does not include artificial time limits.

During the completion of a process, preselected options that impact finance, privacy or safety are visibly and programmatically available to the user by default.

Automated input of personal information from user agents, third-party tools, or paste is not prevented.

Processes can be completed without a cognitive function test.

Copying of content is not prevented.

Processes can be completed without memorizing and recalling information from previous stages of the process.

Information and resources that are needed to complete a multi-step process are provided at the start of the process, including the: - number of steps it might take (if known in advance), - details of any resources needed to perform the task, and - overview of the process and next step.

The instructions needed to complete a multi-step process are available.

The interface indicates when user input or action is required in order to proceed to the next step.

In a multi-step process, the interface supports stepping backwards in a process and returning to the current point without data loss.

Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated, or available for the user to select.

Data entry and other task completion processes allow saving and resuming from the current step in the task.

[Title, role, or organization] asserts that: * Usability testing has been conducted to review for unnecessary steps in the process or unnecessary information being requested. * The sample of test participants included people with cognitive disabilities and/or mental health based disabilities. ::assertion-required * title, role, or organization making the assertion * date of assertion ::assertion-recommended * maintained records of usability testing protocol, scope of the testing, and results * number of participants and disabilities represented within the group of participants * record of actions taken to address identified issues

[Title, role, or organization] asserts that: * Content author(s) train AI models using representative and unbiased disability-related information that is proportional to the general population.

[Title, role, or organization] asserts that: * Content author(s) conduct usability testing and ethics reviews to minimize the possibility that algorithms disadvantage people with disabilities.

[Title, role, or organization] asserts that: * We have a policy and process to review — and have reviewed — the data set, results, and/or algorithm in order to minimize the possibility that algorithms are disadvantageous for people with disabilities. ::assertion-required * title, role, or organization making the assertion * date of assertion * disabilities considered * what was reviewed (data set, results, or algorithm itself) * review scope ::assertion-recommended * results * copy of any process and policy * copy of usability testing, if conducted * steps taken to resolve the issues found

Legal, financial, privacy, and security consequences are provided before finalizing an agreement.

Choices with legal, financial, privacy, or security consequences are accompanied by a description of the benefits, risks, and potential consequences when users make the choice.

[Title, role, or organization] asserts that: * When considering the safety and security of our users, we considered use cases of people with diverse disabilities. For example, people with cognitive or learning disabilities are sometimes targeted on social media for sexual exploitation and other bad intent. * Research has been conducted on risks to safety, wellbeing, and mental health for users with diverse disabilities and, when risks are found, all reasonable practical steps have been identified and taken to mitigate the risk. ::assertion-required * title, role, or organization making the assertion * date of assertion ::assertion-recommended * list of steps that have been taken * list of use cases used

Use of assistive technology, accessible alternative versions, accessibility-related modifications of content, and accessibility-related settings do not expose people with disabilities to additional risk.

A mechanism is available to provide feedback to authors.

Help is labeled consistently and is available in a consistent location relative to other content.

Context-sensitive help is available.

Conversational support allowing both text and speech formats is available.

:::ednote Editors are considering removal of this requirement.

Information explaining why a visible interactive element is disabled is available and, if the user can take action(s) to enable the element, those action(s) are described.

[Title, role, or organization] asserts that: * Help and training was added based on usability testing with people with cognitive and mental health disabilities to identify gaps. ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of when the usability testing was conducted * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * usability findings * solutions added

A mechanism to learn a new interface or revert to the older design is available.

:::ednote Editors are considering removal of this requirement.

Instructions and help do not rely on sensory characteristics.

Support is available during data entry, task completion and search.

[Title, role, or organization] asserts that: * We have conducted a review to identify when users need to make substantial decisions about money, privacy, or well-being. In these situations, additional support was provided, such as: * a clear layout of options advantages and disadvantages * aids for comprehension such as icons and graphics * reduced distractions ::assertion-required * title, role, or organization making the assertion (if different from the conformance claim) * date of when the policy was implemented * date of assertion (if different from the date of the conformance claim) ::assertion-recommended * results of review * documentation of decisions and changes made as a result

All content fits within 320 CSS pixels in the default orientation of text without requiring scrolling in more than one direction. Sections of content within the page/view that scroll in a different direction to the page/view fit within 320 CSS pixels of the page-scrolling direction.

Content supports both portrait and landscape orientations.

If the platform has a default orientation, content supports that orientation. If the platform does not have a default orientation, content supports both portrait and landscape orientations.

Blocks of text are legible at 320 CSS pixels in the orientation of text, without the need to scroll in the orientation of text.

Content can be controlled using assistive and adaptive technology.

The timing or positioning of notifications can be changed, suppressed, or saved.

Content responds to users’ platform and user agent accessibility-related settings.

Assistive technologies can access content and interactions when using mechanisms that convey alternative points of regard or focus.

Meaningful changes in visual content are conveyed programmatically.

When the focus changes on-focus or automatically, the user is notified visually and programmatically.

When content triggers a device change or an automatic user agent change, the user is notified before the change occurs.

Patterns, designs, or images placed behind text are avoided or can be removed by the user.

When font size conveys visual meaning (such as headings), the text maintains its meaning and purpose when text is resized.

Closed captions and audio descriptions can be turned on and off.

Alternatives for media can be searched and queried.

Audio or video that lasts five minutes or longer can be navigated by chapters.

A mechanism is available to pause, stop, and adjust the volume independently of the overall system volume level, of any automatically playing audio in a page/view.