Re: Inactive buttons, contrast and accessibility

Hi Ginger,

I think it isn’t a good practice to make the submit button inactive when the user hasn’t filled in all fields.

Maybe you can check if the form is completely accessible?
Is it clear that the user is on a login form? And is it clear which fields are available and required to fill in?

Provide some good error handling.
Which error does the user get when the user hasn’t filled in a field?

Documentation:
- https://www.w3.org/WAI/tutorials/forms/
- https://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error.html

Kind regards,

Sebastian




—
Sebastian Vyaene
sebastian@hellopixel.be
https://www.hellopixel.be

> On 24 Apr 2024, at 09:52, Ginger Claassen <ginger.claassen@gmx.de> wrote:
> 
> 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
> 
>