Make it Easy to Undo Form Errors | Cognitive Accessibility Design Pattern | WAI

<!DOCTYPE html> <html class="no-js" lang="en" dir="ltr" prefix="og: http://ogp.me/ns#"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <script> document.documentElement.className = document.documentElement.className.replace('no-js', 'has-js'); function downloadJSAtOnload() { var element = document.createElement("script"); element.src = "/WAI/assets/scripts/main.js?1739902561245459979"; document.body.appendChild(element); } window.addEventListener("load", downloadJSAtOnload, false); </script> <link rel="stylesheet" href="/WAI/assets/css/style.css?1739902561245459979"> <title> Make it Easy to Undo Form Errors | Cognitive Accessibility Design Pattern | WAI | W3C</title> <meta name="generator" content="Jekyll v4.3.3" /> <meta property="og:title" content="Make it Easy to Undo Form Errors" /> <meta name="author" content="W3C Web Accessibility Initiative (WAI)" /> <meta property="og:locale" content="en_US" /> <meta name="description" content="User Need I need to check my work and go back without losing the work I have just done. What to Do Always allow the user to check their work and correct any mistakes. Once the user has fixed their mistake it should be easy to get back to the place they were at without redoing additional steps. For financial transactions and important information, allow the user to easily cancel the transactions. Provide clear information and simple instructions for important information such as the amount of time the user has to cancel a transaction. How it Helps People with cognitive and learning disabilities make many more mistakes filling out forms than the general population. When mistakes cannot be easily corrected they cannot complete the task. The ability to undo errors helps people with cognitive and learning disabilities safely use forms and reduces the consequences that result from a mistake. For example, a user with a memory impairment may not remember that they have already added an item to their shopping cart and may add the item a second time. They may confuse the dates when booking a trip or make other mistakes. It is essential that people with cognitive and learning disabilities have the opportunity to check their work and fix their mistakes easily. For people with cognitive and learning disabilities, mistakes being theoretically reversible is not enough. Often the process of reversing a transaction is too complex for them to manage without help. They may not have access to that help meaning they have to live with all the mistakes they have made. In addition, if the process of correcting mistakes is too difficult, users may stop, either losing the transaction or buying unwanted items. The effect of this happening multiple times is devastating. As a result, many users with disabilities may stop using the Internet for many tasks. Allowing the user to change the number of items in the shopping cart at any time can significantly reduce mistakes. A summary of the order, including product quantities and other costs before the final submission, gives the user the chance to identify any errors and make changes to the order. In this example given, a summary of the purchase helps the user see the error in quantity as well as a higher than expected order total. In some cases, a user may realize that a mistake has been made after the final submission of data. Provide simple language instructions on how to cancel transactions and help the user understand the amount of time needed to cancel a transaction. This makes them less susceptible to scams. For example, a user with Attention-Deficit/Hyperactivity Disorder purchasing a travel ticket on a web site may struggle with details and may have an impaired attention span. The successful completion of the order relies on the information provided at multiple steps in the process. An error such as an incorrect street number or zip code in the billing address will result in the order not going though. If a summary is not provided before submitting the final order, the user may not understand the reason for the declined payment and give up on the order. The user may also stop if there is not a clear and achievable way to make a correction. More Details This typically includes: Change: It is simple for the user to review all the data and correct mistakes, including mistakes that might not be automatically identified. The user can change information via clearly labeled actions and get back to the place they were at, in one clearly labeled action without unwanted loss of data. (Some data may need to be entered if it is dependent on the item that was changed.) Confirmed: A summary is provided before submitting important information and the user is told when they are about to submit the final information. Time frames and instruction for canceling transactions are clear and easy to follow. Getting Started Start with forms where a mistake can have serious consequences such as financial loss or vulnerability. Examples Use: A summary provided before submitting important information. It allows the user to correct information and return to the summary with a single click. Clickable breadcrumbs that allow the user to see the previous steps, go back, and change them. Avoid:" /> <meta property="og:description" content="User Need I need to check my work and go back without losing the work I have just done. What to Do Always allow the user to check their work and correct any mistakes. Once the user has fixed their mistake it should be easy to get back to the place they were at without redoing additional steps. For financial transactions and important information, allow the user to easily cancel the transactions. Provide clear information and simple instructions for important information such as the amount of time the user has to cancel a transaction. How it Helps People with cognitive and learning disabilities make many more mistakes filling out forms than the general population. When mistakes cannot be easily corrected they cannot complete the task. The ability to undo errors helps people with cognitive and learning disabilities safely use forms and reduces the consequences that result from a mistake. For example, a user with a memory impairment may not remember that they have already added an item to their shopping cart and may add the item a second time. They may confuse the dates when booking a trip or make other mistakes. It is essential that people with cognitive and learning disabilities have the opportunity to check their work and fix their mistakes easily. For people with cognitive and learning disabilities, mistakes being theoretically reversible is not enough. Often the process of reversing a transaction is too complex for them to manage without help. They may not have access to that help meaning they have to live with all the mistakes they have made. In addition, if the process of correcting mistakes is too difficult, users may stop, either losing the transaction or buying unwanted items. The effect of this happening multiple times is devastating. As a result, many users with disabilities may stop using the Internet for many tasks. Allowing the user to change the number of items in the shopping cart at any time can significantly reduce mistakes. A summary of the order, including product quantities and other costs before the final submission, gives the user the chance to identify any errors and make changes to the order. In this example given, a summary of the purchase helps the user see the error in quantity as well as a higher than expected order total. In some cases, a user may realize that a mistake has been made after the final submission of data. Provide simple language instructions on how to cancel transactions and help the user understand the amount of time needed to cancel a transaction. This makes them less susceptible to scams. For example, a user with Attention-Deficit/Hyperactivity Disorder purchasing a travel ticket on a web site may struggle with details and may have an impaired attention span. The successful completion of the order relies on the information provided at multiple steps in the process. An error such as an incorrect street number or zip code in the billing address will result in the order not going though. If a summary is not provided before submitting the final order, the user may not understand the reason for the declined payment and give up on the order. The user may also stop if there is not a clear and achievable way to make a correction. More Details This typically includes: Change: It is simple for the user to review all the data and correct mistakes, including mistakes that might not be automatically identified. The user can change information via clearly labeled actions and get back to the place they were at, in one clearly labeled action without unwanted loss of data. (Some data may need to be entered if it is dependent on the item that was changed.) Confirmed: A summary is provided before submitting important information and the user is told when they are about to submit the final information. Time frames and instruction for canceling transactions are clear and easy to follow. Getting Started Start with forms where a mistake can have serious consequences such as financial loss or vulnerability. Examples Use: A summary provided before submitting important information. It allows the user to correct information and return to the summary with a single click. Clickable breadcrumbs that allow the user to see the previous steps, go back, and change them. Avoid:" /> <link rel="canonical" href="https://www.w3.org/WAI/WCAG2/supplemental/patterns/o4p05-form-undo/" /> <meta property="og:url" content="https://www.w3.org/WAI/WCAG2/supplemental/patterns/o4p05-form-undo/" /> <meta property="og:site_name" content="Web Accessibility Initiative (WAI)" /> <meta property="og:type" content="article" /> <meta property="article:published_time" content="2025-02-18T18:16:01+00:00" /> <meta name="twitter:card" content="summary_large_image" /> <meta property="twitter:title" content="Make it Easy to Undo Form Errors" /> <meta name="twitter:site" content="@w3c_wai" /> <meta name="twitter:creator" content="@W3C Web Accessibility Initiative (WAI)" /> <script type="application/ld+json"> {"@context":"https://schema.org","@type":"BlogPosting","author":{"@type":"Person","name":"W3C Web Accessibility Initiative (WAI)"},"dateModified":"2025-02-18T18:16:01+00:00","datePublished":"2025-02-18T18:16:01+00:00","description":"User Need I need to check my work and go back without losing the work I have just done. What to Do Always allow the user to check their work and correct any mistakes. Once the user has fixed their mistake it should be easy to get back to the place they were at without redoing additional steps. For financial transactions and important information, allow the user to easily cancel the transactions. Provide clear information and simple instructions for important information such as the amount of time the user has to cancel a transaction. How it Helps People with cognitive and learning disabilities make many more mistakes filling out forms than the general population. When mistakes cannot be easily corrected they cannot complete the task. The ability to undo errors helps people with cognitive and learning disabilities safely use forms and reduces the consequences that result from a mistake. For example, a user with a memory impairment may not remember that they have already added an item to their shopping cart and may add the item a second time. They may confuse the dates when booking a trip or make other mistakes. It is essential that people with cognitive and learning disabilities have the opportunity to check their work and fix their mistakes easily. For people with cognitive and learning disabilities, mistakes being theoretically reversible is not enough. Often the process of reversing a transaction is too complex for them to manage without help. They may not have access to that help meaning they have to live with all the mistakes they have made. In addition, if the process of correcting mistakes is too difficult, users may stop, either losing the transaction or buying unwanted items. The effect of this happening multiple times is devastating. As a result, many users with disabilities may stop using the Internet for many tasks. Allowing the user to change the number of items in the shopping cart at any time can significantly reduce mistakes. A summary of the order, including product quantities and other costs before the final submission, gives the user the chance to identify any errors and make changes to the order. In this example given, a summary of the purchase helps the user see the error in quantity as well as a higher than expected order total. In some cases, a user may realize that a mistake has been made after the final submission of data. Provide simple language instructions on how to cancel transactions and help the user understand the amount of time needed to cancel a transaction. This makes them less susceptible to scams. For example, a user with Attention-Deficit/Hyperactivity Disorder purchasing a travel ticket on a web site may struggle with details and may have an impaired attention span. The successful completion of the order relies on the information provided at multiple steps in the process. An error such as an incorrect street number or zip code in the billing address will result in the order not going though. If a summary is not provided before submitting the final order, the user may not understand the reason for the declined payment and give up on the order. The user may also stop if there is not a clear and achievable way to make a correction. More Details This typically includes: Change: It is simple for the user to review all the data and correct mistakes, including mistakes that might not be automatically identified. The user can change information via clearly labeled actions and get back to the place they were at, in one clearly labeled action without unwanted loss of data. (Some data may need to be entered if it is dependent on the item that was changed.) Confirmed: A summary is provided before submitting important information and the user is told when they are about to submit the final information. Time frames and instruction for canceling transactions are clear and easy to follow. Getting Started Start with forms where a mistake can have serious consequences such as financial loss or vulnerability. Examples Use: A summary provided before submitting important information. It allows the user to correct information and return to the summary with a single click. Clickable breadcrumbs that allow the user to see the previous steps, go back, and change them. Avoid:","headline":"Make it Easy to Undo Form Errors","mainEntityOfPage":{"@type":"WebPage","@id":"https://www.w3.org/WAI/WCAG2/supplemental/patterns/o4p05-form-undo/"},"url":"https://www.w3.org/WAI/WCAG2/supplemental/patterns/o4p05-form-undo/"}</script>  <meta name="twitter:image" property="og:image" content="https://www.w3.org/WAI/assets/images/social-sharing-default.jpg"> <link rel="alternate" type="application/rss+xml" href="/WAI/feed.xml"> </head> <body id="top" class="page-make-it-easy-to-undo-form-errors resource-patterns tight-page"> <a href="#main" class="button button--skip-link">Skip to content</a> <div class="minimal-header-container default-grid"> <header class="minimal-header" id="site-header"> <div class="minimal-header-container"> <div class="minimal-header-name"> Supplemental Guidance to WCAG 2 </div> <p class="minimal-header-subtitle"> Additional ways to improve accessibility, not required to meet WCAG) </p> </div> <a class="minimal-header-link" href="/WAI/WCAG2/supplemental/about/">About Supplemental Guidance and WCAG</a> <div class="minimal-header-logo"> <a href="/WAI/"> <img alt="W3C" src="/WAI/assets/images/w3c2.svg" width="92" height="44"/> <img alt="Web Accessibility Initiative" src="/WAI/assets/images/wai.svg"/> </a> </div> </header> </div> <div class="default-grid nav-container"> <div class="nav" > <nav class="nav standalone-resource-pager" aria-label="Cognitive Accessibility Design Pattern"> <ul> <li class="nav__item"> <a href="/WAI/WCAG2/supplemental/#cognitiveaccessibilityguidance"><img src="/WAI/content-images/wai-wcag-supplemental/brain.svg" alt="" class="category-icon">All Cognitive</a> </li> <li class="nav__item"><a href="/WAI/WCAG2/supplemental/objectives/o4-minimize-mistakes/"><svg focusable="false" aria-hidden="true" class="icon-arrow-up-thin pager-icon"><use xlink:href="/WAI/assets/images/icons.svg#icon-arrow-up-thin"></use></svg> Objective: Help Users Avoid Mistakes and Know How to Correct Them</a></li> <li class="nav__item"><a href="/WAI/WCAG2/supplemental/patterns/o4p04-supportive-forms/"><svg focusable="false" aria-hidden="true" class="icon-arrow-left-thin pager-icon"><use xlink:href="/WAI/assets/images/icons.svg#icon-arrow-left-thin"></use></svg> Previous Pattern</a></li> <li class="nav__item"><a href="/WAI/WCAG2/supplemental/patterns/o4p06-clear-labels/">Next Pattern <svg focusable="false" aria-hidden="true" class="icon-arrow-right-thin pager-icon"><use xlink:href="/WAI/assets/images/icons.svg#icon-arrow-right-thin"></use></svg></a></li> </ul> </nav> </div> </div> <div class="default-grid with-gap leftcol"> <style> .nav { background: none; } .nav-related-info { /* blue bar with the "About:" links */ background: #005a9c; color: #fff; } .nav-related-info a { color: #fff !important; } .nav-page-specific { /* light blue bar with page/section specific navigation/pager */ margin-bottom: 1.25em; } .nav a:link, .nav a:visited { color: #036; color: var(--w3c-blue); } .nav a:hover, .nav a:active { color: var(--dk-blue); } .nav-hack.sidebar a:hover, .nav-hack.sidebar a:active { color: var(--dk-blue); text-decoration: underline; } .standalone-resource-about, .standalone-resource-pager { margin: 0; } nav.standalone-resource-about { padding: .5em 0 1.5em 0; font-style: italic; } .nav .standalone-resource-pager ul { align-items: center; } .nav .standalone-resource-pager a, .nav .standalone-resource-pager span { margin-left: 0; margin-right: 1.5em; padding: .5em; } .pager-icon { vertical-align: middle; padding: 0 0 0.15em 0; margin: 0 -0.4em; width: 1.65em; height: 2em; fill: var(--dk-blue) } .category-icon { vertical-align: middle; padding: 0 0.25em 0.25em 0.25em; width: 2em; height: 2em; } .zstandalone-resource-pager { padding: .7em 0; } .standalone-resource-pager zul { display: block; } .standalone-resource-pager zul li { display: inline; } .nav-hack { font-size: .85rem; /*justify-self: end;*/ align-self: start; } .nav-hack ul { list-style: none; border-bottom: 1px solid #BCBCBC; padding-left: 0 } .nav-hack li:not(:first-child){ padding-top: 0.4em; line-height: 1.2; border-top: 1px solid #BCBCBC; } .nav-hack li a { text-decoration: none; } .nav-hack h3 { margin: 0; font-size: 1rem; } .nav-hack p { margin: 0; } h2#sidebar-header { font-size: .95rem; } /* skip link */ .button--skip-link { background-color: var(--gold) !important; border-color: var(--gold) !important; outline-color: currentColor !important; color: var(--off-black) !important; font-weight: 600; font-size: larger; margin: 0 auto; position: absolute; z-index: 20; left: 0; right: 0; top: 0.5em; width: 10em; opacity: 1; transition: transform 0.1875s ease-out, opacity 0.1875s ease-out; } .button--skip-link:not(:focus):not(:hover) { transform: translateY(-4em); opacity: 0; } .standalone-resource-navrule { border:none; border-top: 1px solid grey } .standalone-resource-about ul, .standalone-resource-pager ul { list-style: none; } .standalone-resource-about a, .standalone-resource-pager a, .standalone-resource-about span, .standalone-resource-pager span { margin-left:.8em; margin-right:.8em; } .minimal-header-name a { text-decoration: none; } .minimal-header-name a:hover, .minimal-header-name a:focus { text-decoration: underline; } </style> <nav class="box nav-hack sidebar standalone-resource__sidebar " aria-labelledby="sidebar-header"> <h2 id="sidebar-header" class="box-h ">Page Contents</h2> <div class="box-i"> <ul> <li><a href="#userneed">User Need</a></li> <li><a href="#whattodo">What to Do</a></li> <li><a href="#howithelps">How it Helps</a></li> <li><a href="#moredetails">More Details</a></li> <li><a href="#gettingstarted">Getting Started</a></li> <li><a href="#examples">Examples</a></li> <li><a href="#userstoriesandpersonas">User Stories and Personas</a></li> </ul> </div> </nav> <main id="main" class="standalone-resource__main"> <header> <h1> <span class="standalone-resource__type-of-guidance"> Cognitive Accessibility Design Pattern: </span> Make it Easy to Undo Form Errors </h1> </header> <section> <h2 id="userneed">User Need</h2> <blockquote> <p> I need to check my work and go back without losing the work I have just done. </p> </blockquote> </section> <section class="wtd"> <h2 id="whattodo">What to Do</h2> <p> Always allow the user to check their work and correct any mistakes. Once the user has fixed their mistake it should be easy to get back to the place they were at without redoing additional steps. </p> <p> For financial transactions and important information, allow the user to easily cancel the transactions. Provide clear information and simple instructions for important information such as the amount of time the user has to cancel a transaction. </p> </section> <section> <h2 id="howithelps">How it Helps</h2> <p> People with cognitive and learning disabilities make many more mistakes filling out forms than the general population. When mistakes cannot be easily corrected they cannot complete the task. </p> <p> The ability to undo errors helps people with cognitive and learning disabilities safely use forms and reduces the consequences that result from a mistake. </p> <p> For example, a user with a memory impairment may not remember that they have already added an item to their shopping cart and may add the item a second time. They may confuse the dates when booking a trip or make other mistakes. </p> <p> It is essential that people with cognitive and learning disabilities have the opportunity to check their work and fix their mistakes easily. </p> <p> For people with cognitive and learning disabilities, mistakes being theoretically reversible is not enough. Often the process of reversing a transaction is too complex for them to manage without help. They may not have access to that help meaning they have to live with all the mistakes they have made. In addition, if the process of correcting mistakes is too difficult, users may stop, either losing the transaction or buying unwanted items. </p> <p> The effect of this happening multiple times is devastating. As a result, many users with disabilities may stop using the Internet for many tasks. </p> <p> Allowing the user to change the number of items in the shopping cart at any time can significantly reduce mistakes. </p> <p> A summary of the order, including product quantities and other costs before the final submission, gives the user the chance to identify any errors and make changes to the order. In this example given, a summary of the purchase helps the user see the error in quantity as well as a higher than expected order total. </p> <p> In some cases, a user may realize that a mistake has been made after the final submission of data. Provide simple language instructions on how to cancel transactions and help the user understand the amount of time needed to cancel a transaction. This makes them less susceptible to scams. </p> <p> For example, a user with Attention-Deficit/Hyperactivity Disorder purchasing a travel ticket on a web site may struggle with details and may have an impaired attention span. The successful completion of the order relies on the information provided at multiple steps in the process. An error such as an incorrect street number or zip code in the billing address will result in the order not going though. If a summary is not provided before submitting the final order, the user may not understand the reason for the declined payment and give up on the order. The user may also stop if there is not a clear and achievable way to make a correction. </p> </section> <section> <h2 id="moredetails">More Details</h2> <p>This typically includes:</p> <ul> <li> Change: It is simple for the user to review all the data and correct mistakes, including mistakes that might not be automatically identified. The user can change information via clearly labeled actions and get back to the place they were at, in one clearly labeled action without unwanted loss of data. (Some data may need to be entered if it is dependent on the item that was changed.) </li> <li> Confirmed: A summary is provided before submitting important information and the user is told when they are about to submit the final information. </li> <li> Time frames and instruction for canceling transactions are clear and easy to follow. </li> </ul> </section> <section> <h2 id="gettingstarted">Getting Started</h2> <p> Start with forms where a mistake can have serious consequences such as financial loss or vulnerability. </p> </section> <section> <h2 id="examples">Examples</h2> <p><span class="use"></span><strong>Use:</strong></p> <ul> <li> A summary provided before submitting important information. It allows the user to correct information and return to the summary with a single click. </li> <li> Clickable breadcrumbs that allow the user to see the previous steps, go back, and change them. </li> </ul> <p><span class="avoid"></span><strong>Avoid:</strong></p> <ul> <li> A summary provided before submitting important information, but the user cannot make corrections without losing other data entered. </li> </ul> </section> <section> <h2 id="userstoriesandpersonas">User Stories and Personas</h2> <h3>User Story</h3> <ul> <li> <a href="https://www.w3.org/TR/coga-usable/#undo-user-story">Undo <svg focusable="false" aria-hidden="true" class="icon-different-view "><use xlink:href="/WAI/assets/images/icons.svg#icon-different-view"></use></svg></a> </li> </ul> <h3>Personas</h3> <ul> <li> <a href="https://www.w3.org/TR/coga-usable/#alison-an-aging-user-with-mild-cognitive-impairment">Alison : An Aging User with Mild Cognitive Impairment <svg focusable="false" aria-hidden="true" class="icon-different-view "><use xlink:href="/WAI/assets/images/icons.svg#icon-different-view"></use></svg></a> </li> <li> <a href="https://www.w3.org/TR/coga-usable/#maria-a-user-who-has-memory-loss">Maria : A User who has Memory Loss <svg focusable="false" aria-hidden="true" class="icon-different-view "><use xlink:href="/WAI/assets/images/icons.svg#icon-different-view"></use></svg></a> </li> <li> <a href="https://www.w3.org/TR/coga-usable/#tal-a-student-who-has-dyslexia-and-impaired-eye-hand-coordination">Tal : A Student who has Dyslexia and Impaired Eye Hand Coordination <svg focusable="false" aria-hidden="true" class="icon-different-view "><use xlink:href="/WAI/assets/images/icons.svg#icon-different-view"></use></svg></a> </li> </ul> <h3>Glossary</h3> <ul> <li><a href="https://www.w3.org/TR/coga-usable/#glossary">Cognitive Accessibility Glossary<svg focusable="false" aria-hidden="true" class="icon-different-view "><use xlink:href="/WAI/assets/images/icons.svg#icon-different-view"></use></svg></a></li> </ul> </section> </main> </div> <div class="default-grid with-gap leftcol"> <div class="standalone-resource__prevnext"><aside class="box box-icon box-space-above" id="helpimprove" aria-label="feedback"><header class="box-h box-h-icon box-h-space-above box-h-icon"> <svg focusable="false" aria-hidden="true" class="icon-comments "><use xlink:href="/WAI/assets/images/icons.svg#icon-comments"></use></svg> <h2> Help improve this page </h2></header><div class="box-i"><p>Please share your ideas, suggestions, or comments via e-mail to the publicly-archived list <a href="mailto:public-cognitive-a11y-tf@w3.org?body=%5Binclude%20a%20relevant%20email%20Subject%5D%0A%0A%5Bput%20comment%20here...%5D%0A%0A">public-cognitive-a11y-tf@w3.org</a> or via GitHub.</p> <div class="button-group"> <a href="mailto:public-cognitive-a11y-tf@w3.org?body=%5Binclude%20a%20relevant%20email%20Subject%5D%0A%0A%5Bput%20comment%20here...%5D%0A%0A" class="button"><span>E-mail</span></a><a href=" https://github.com/w3c/wai-wcag-supplemental/edit/main/_collections/_patterns/o4p05-form-undo.html " class="button"><span>Fork & Edit on GitHub</span></a><a href="https://github.com/w3c/wai-wcag-supplemental/issues/new?template=content-issue.yml&title=[]%20&wai-url=https://www.w3.org/WAI/WCAG2/supplemental/patterns/o4p05-form-undo/" class="button"><span>New GitHub Issue</span></a></div></div></aside> </div> </div> <a class="button button-backtotop" href="#top"><span><svg focusable="false" aria-hidden="true" class="icon-arrow-up "><use xlink:href="/WAI/assets/images/icons.svg#icon-arrow-up"></use></svg> Back to Top</span></a> </div> <footer id="wai-site-footer" class="page-footer default-grid" aria-label="Page"> <div class="inner"style="-ms-grid-column: 2; -ms-grid-column-span: 8; grid-column: 2 / 8;"><p><strong>Date:</strong> Content first published 29 April 2021 in <a href="https://www.w3.org/TR/coga-usable/">Making Content Usable for People with Cognitive and Learning Disabilities</a> ("Content Usable"). This user interface posted in January 2022.</p> <p>This content is from the "Content Usable" Working Group Note by Cognitive and Learning Disabilities Accessibility Task Force (<a href="https://www.w3.org/groups/tf/cognitive-a11y-tf">Coga TF</a>) <a href="https://www.w3.org/groups/tf/cognitive-a11y-tf/participants">participants</a>. It is published by the Accessibility Guidelines Working Group (<a href="https://www.w3.org/groups/wg/ag">AG WG</a>) and the Accessible Platform Architectures (<a href="https://www.w3.org/groups/wg/apa">APA</a>) Working Group. This user interface was designed by the Accessibility Education and Outreach Working Group (<a href="https://www.w3.org/groups/wg/eowg">EOWG</a>) with contributions from Steve Lee, Hidde de Vries, Shadi Abou-Zahra, and Shawn Lawton Henry, as part of the <a href="https://www.w3.org/WAI/about/projects/wai-guide/"> WAI-Guide project</a>, co-funded by the European Commission.</p> </div> </footer> <footer class="site-footer grid-4q" aria-label="Site"> <div class="q1-start q3-end about"> <div> <p><a class="largelink" href="https://www.w3.org/WAI/" lang="en" dir="auto" translate="no">W3C Web Accessibility Initiative (WAI)</a></p> <p>Strategies, standards, and supporting resources to make the Web accessible to people with disabilities.</p> </div> <div class="social" lang="en" dir="auto" translate="no"> <ul> <li><a href="https://w3c.social/@wai"><svg focusable="false" aria-hidden="true" class="icon-mastodon "><use xlink:href="/WAI/assets/images/icons.svg#icon-mastodon"></use></svg> Mastodon</a></li> <li><a href="https://www.linkedin.com/company/w3c-wai/"><svg focusable="false" aria-hidden="true" class="icon-linkedin "><use xlink:href="/WAI/assets/images/icons.svg#icon-linkedin"></use></svg> LinkedIn</a></li> <li><a href="https://www.w3.org/WAI/feed.xml"><svg focusable="false" aria-hidden="true" class="icon-rss "><use xlink:href="/WAI/assets/images/icons.svg#icon-rss"></use></svg> Feed</a></li> <li><a href="https://www.youtube.com/channel/UCU6ljj3m1fglIPjSjs2DpRA/playlists/"><svg focusable="false" aria-hidden="true" class="icon-youtube "><use xlink:href="/WAI/assets/images/icons.svg#icon-youtube"></use></svg> YouTube</a></li> <li><a href="https://www.w3.org/WAI/news/subscribe/" class="button">Get News in Email</a></li> </ul> </div> <div lang="en" dir="auto" translate="no"> <p>Copyright 漏 2025 World Wide Web Consortium (<a href="https://www.w3.org/">W3C</a><sup>庐</sup>). See <a href="/WAI/about/using-wai-material/">Permission to Use WAI Material</a>.</p> </div> </div> <div lang="en" dir="auto" translate="no" class="q4-start q4-end"> <ul style="margin-bottom:0"> <li><a href="/WAI/about/contacting/">Contact WAI</a></li> <li><a href="/WAI/sitemap/">Site Map</a></li> <li><a href="/WAI/news/">News</a></li> <li><a href="/WAI/sitemap/#archive">Archive</a></li> <li><a href="/WAI/about/accessibility-statement/">Accessibility Statement</a></li> <li><a href="/WAI/translations/"> Translations</a></li> <li><a href="/WAI/roles/">Resources for Roles</a></li> </ul> </div> </footer> <script src="/WAI/assets/scripts/details4everybody.js?1739902561245459979"></script>  <script src="/WAI/assets/scripts/svg4everybody.js?1739902561245459979"></script> <script> svg4everybody(); </script><script> var translationStrings = {}; </script> </body> </html>

CINXE.COM

Make it Easy to Undo Form Errors | Cognitive Accessibility Design Pattern | WAI | W3C