E-mail List Archives
Question about inactive buttons and feedback...
From: Ray Alexander
Date: Mar 11, 2019 9:05AM
- Next message: Jim Homme: "Re: Question about inactive buttons and feedback..."
- Previous message: Greenfield, Mark: "Re: Heading structure"
- Next message in Thread: Jim Homme: "Re: Question about inactive buttons and feedback..."
- Previous message in Thread: None
- View all messages in this Thread
We are having a debate at work about inactive UI components.
We all understand and agree that, according to 1.4.3, inactive user interface components do not need to conform to color contrast requirements.
I have read back through the archives of this email list to try and find an answer to our debate, but no luck.
Here is the question: if an "inactive" button provides feedback about why the button is inactive, is it still an inactive button?
For example...there is a process that requires 3 actions be taken before the process can be submitted. There is an inactive button below the list of 3 actions. If the button is pressed while 1 action remains uncompleted, can we provide the user with information about what needs to be completed to continue? Or, does adding in that feedback re-define the button as an active UI component?
Thanks,
Ray
Sent from my iPhone
- Next message: Jim Homme: "Re: Question about inactive buttons and feedback..."
- Previous message: Greenfield, Mark: "Re: Heading structure"
- Next message in Thread: Jim Homme: "Re: Question about inactive buttons and feedback..."
- Previous message in Thread: None
- View all messages in this Thread