Re: Start over link for an error page

If there is no other way to correct mistakes after submission, the "start
over" or "go back" might be necessary to meet 3.3.4 or 3.3.6...

*3.3.4 Error Prevention (Legal, Financial, Data):* For Web pages
<https://www.w3.org/TR/2008/REC-WCAG20-20081211/#webpagedef> that cause legal
commitments
<https://www.w3.org/TR/2008/REC-WCAG20-20081211/#legalcommitmentsdef> or
financial transactions for the user to occur, that modify or delete
user-controllable
<https://www.w3.org/TR/2008/REC-WCAG20-20081211/#user-controllabledef> data
in data storage systems, or that submit user test responses, at least one
of the following is true: (Level AA)

   1.

   *Reversible: *Submissions are reversible.
   2.

   *Checked: *Data entered by the user is checked for input errors
   <https://www.w3.org/TR/2008/REC-WCAG20-20081211/#input-errordef> and the
   user is provided an opportunity to correct them.
   3.

   *Confirmed: *A mechanism
   <https://www.w3.org/TR/2008/REC-WCAG20-20081211/#mechanismdef> is
   available for reviewing, confirming, and correcting information before
   finalizing the submission.

*3.3.6 Error Prevention (All):* For Web pages
<https://www.w3.org/TR/2008/REC-WCAG20-20081211/#webpagedef> that require
the user to submit information, at least one of the following is true:
(Level AAA)

   1.

   *Reversible: *Submissions are reversible.
   2.

   *Checked: *Data entered by the user is checked for input errors
   <https://www.w3.org/TR/2008/REC-WCAG20-20081211/#input-errordef> and the
   user is provided an opportunity to correct them.
   3.

   *Confirmed: *A mechanism
   <https://www.w3.org/TR/2008/REC-WCAG20-20081211/#mechanismdef> is
   available for reviewing, confirming, and correcting information before
   finalizing the submission.

*Matthew Kreiling*

We're all in it together.

360-545-3116

*"To live is so startling it leaves little time for anything else."*

—Emily Dickinson



On Fri, Aug 2, 2019 at 11:11 AM ALAN SMITH <alands289@gmail.com> wrote:

> Angela,
>
>
>
> It is not a requirement.
>
>
>
> Multiple Ways is for finding website content not for getting back to the
> start of some place on a page or in a process.
>
>
>
> This may be some kind of Error Suggestion in a way also but not exactly as
> written in WCAG3.3.3.
>
>
>
> This would be something like a Bypass Blocks idea to get “back” to
> something quickly.
>
> However, it just seems to me to be a nice function and with proper
> labeling, keyboard selection and color contrast (and all the other things
> we do to buttons and links), it would be accessible.
>
>
>
> Alan Smith
>
>
>
> *From: *Davis, Angela (ITS) <Angela.Davis@its.ny.gov>
> *Sent: *Friday, August 2, 2019 1:20 PM
> *To: *w3c-wai-ig@w3.org
> *Subject: *Start over link for an error page
>
>
>
> Hello,
>
>
>
> I’m auditing a credit card error page and I was wondering if a start over
> link is an accessibility requirement? This link when clicked would take the
> user back to the beginning of the transaction.
>
>
>
> I’m assuming it is not because 2.4.5 Multiple Ways (Level AA) states more
> than one way is available to locate a Web page within a set of Web pages
> except where the Web Page is the result of, or a step in, a process.
>
>
>
> I’m also questioning this because the benefits listed on
> https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways.html make it
> seem as if it should be included on this type of page.
>
>
>
> Any information is helpful!
>
>
>
> Thanks,
>
>
>
> *Angela Davis*
>
> Information Technology Specialist 2
>
> *NYS Office of Information Technology Services*
>
> Citizen Services Cluster | Application Systems Engineering
>
>
>