Re: Inactive buttons, contrast and accessibility

Colour contrast of disabled buttons is exempt from the SC.



Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: Jeremy Echols <jechols@uoregon.edu>
Sent: 24 April 2024 19:20
To: Ginger Claassen <ginger.claassen@gmx.de>; ML W3C, WAI <w3c-wai-ig@w3.org>
Subject: RE: Inactive buttons, contrast and accessibility

Nice client-side error handling should address any concerns without making any changes to the submit button. Hit submit without a password? Identify the error and move focus to the password field. I think most browsers can do this for you just with HTML attributes now, even.

Don't take my word for this, though - it might be that you need to do some work to make sure it's accessible beyond just a "required" attribute. But it's at least something to consider.

-----Original Message-----
From: Ginger Claassen <ginger.claassen@gmx.de>
Sent: Wednesday, April 24, 2024 00:53
To: ML W3C, WAI <w3c-wai-ig@w3.org>
Subject: Inactive buttons, contrast and accessibility

Good Morning everybody,


We have a rather difficult issue in a web portal.

There is a login form and the question is now what to do about the submit button if one of the fields user name or password has not been filled.

Do we make the button inactive i.e. contrast does not meet WCAG and remove it from tab-order or do we keep it in tab-order and provide a tool tip why it is inactive and what to do about the contrast in the latter case?

Sighted users would think the button is an interactive element if we fulfill contrast requirements.


I am looking forward for some helpful input here!


Thanks and solong


     Ginger