E-mail List Archives
Thread: Confirmation Modal
Number of posts in this thread: 3 (In chronological order)
From: Francesco Mammetti
Date: Fri, May 05 2023 9:07AM
Subject: Confirmation Modal
No previous message | Next message →
"In a confirmation modal, I switched the 'cancel' and 'confirm' buttons to
prevent permanent delete errors. Is this incorrect?" In a normal modal, the
'confirm' button is on the left and the 'cancel' button is on the right.
However, for a confirmation modal that involves deleting content, I
reversed the button positions to prevent errors. Would this be considered
inaccessible?
Ciao
Francesco
From: Dean.Vasile
Date: Fri, May 05 2023 10:21AM
Subject: Re: Confirmation Modal
← Previous message | Next message →
Speaking from his screen reader user perspective.
What matters to me is whether my screen reader can read the buttons and I can access them
To me it doesn't matter which one is left or right?
However, I'm not sure if there are guidelines that determine that
Dino
617-799-1162
Dino's Canteen 1618
11 Eglin St,
Hanscom AFB
Bedford, MA
> On May 5, 2023, at 11:07 AM, Francesco Mammetti < = EMAIL ADDRESS REMOVED = > wrote:
>
> "In a confirmation modal, I switched the 'cancel' and 'confirm' buttons to
> prevent permanent delete errors. Is this incorrect?" In a normal modal, the
> 'confirm' button is on the left and the 'cancel' button is on the right.
> However, for a confirmation modal that involves deleting content, I
> reversed the button positions to prevent errors. Would this be considered
> inaccessible?
>
> Ciao
> Francesco
> > > >
From: Mark Magennis
Date: Fri, May 05 2023 10:34AM
Subject: Re: Confirmation Modal
← Previous message | No next message
There isn't any standard that says you should put the buttons in any particular order and this would only be considered an accessibility issue if it disproportionally affects people with disabilities or users of assistive technologies. Users with some types of cognitive impairments may be affected more than others and be more likely to select the unintended action, but really this is a general usability issue that could affect anyone. So you're right to address it but I wouldn't file it under 'accessibility' any more than I would file any other general usability issue under 'accessibility'.
Mark