Examples to Understanding 3.3.4 Error Prevention? #3249
Replies: 3 comments
-
converted to a discussion, as (very high-level) question is not about the spec itself. |
Beta Was this translation helpful? Give feedback.
-
if that has been implemented correctly, that's possibly a reasonable approach. however, in most cases (such as that bootstrap-looking modal you have there) the back button doesn't actually close the modal as such, but navigates to the previous page in the browser's history, so it's not equivalent to an actual close control. and just relying on the user being able to press |
Beta Was this translation helpful? Give feedback.
-
@patrickhlauke Is what you said 'just a bad approach(UX), not against accessibility' correct? |
Beta Was this translation helpful? Give feedback.
-
Is it against accessibility if there is no cancel button(e.g. X) in a dialog without cancel function as in the example above? The only way to return to the previous step is to use 'Back button' after switching screens.
In a practical case, the two buttons on the bottom ('No, Thaks' and 'Payment') are the means to move on to the next step in the dialog below. In this case, the only way the user can cancel is by using the ESC key. In this case, is it against accessibility because it cannot be reversed?
Beta Was this translation helpful? Give feedback.
All reactions