WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Question about inactive buttons and feedback...

for

From: Patrick H. Lauke
Date: Mar 11, 2019 11:44AM

On 11/03/2019 15:05, Ray Alexander wrote:
> 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?

If you can focus and activate the button (and it pops up some
notification), then it's not inactive as such ... there is an action
associated with it being activated. So the exemption under 1.4.3 would
not apply, I'd say.

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke