We currently have parameter pages in a web application containing a list of controls with check boxes, which allows you to enable / disable certain features. We also have a backup option below them that is disabled until the previous checkboxes are changed.
We try to conform this form so that it is more accessible and the current approach is simply not to disable the backup option, but to return an error if no changes have been made. brought and a success message in case of successful modification.
That does not seem to make sense more usable but only helps to bypass the accessibility rule that a send button should not be disabled. However, from the point of view of interaction, the power of disabled The appearance of a button allows the user to know that his work is not finished.
There are 3 possible solutions that I have proposed for this scenario:
- Maintain a LILY view of these controls where no action can be taken unless you click on EDIT to change the controls. in EDIT mode, the check box options are available as well as SAVE And CANCEL and ** SAVE * would be disabled until a change is made (not knowing if it improves accessibility, but at least the idea that you "edit these fields and you need to back it up" more deliberately ).
- Assign a style to the button that looks like a disabled button, but use HTML to treat it as a normal button. If you click on the button, we can display a warning saying "You have not made any changes, please change some commands to save".
- Change the checkboxes to make it a switch-type component that simply saves automatically, eliminating the "Save" button from the equation.
If accessibility-minded people have ideas about which of these options (or an alternative I did not think of) that would make this scenario more user-friendly while making it accessible, please let me know.