- From: Marc Haunschild (Accessibility Consulting) <marc.haunschild@accessibility.consulting>
- Date: Thu, 25 Apr 2024 07:29:37 +0200
- Cc: "ML W3C, WAI" <w3c-wai-ig@w3.org>
Hi everyone, I think, I cannot add anything about WCAG pass/fail what’s not already said. But anyway a thought/ user feedback to consider. When I find a form - especially lengthy forms - I usually write something into the first field and press enter. That brings me to the next required field. It’s the default behavior of a simple html form. If even this doesn’t work the form feels broken and I lose trust in the whole website. Just my 2 cents… -- Mit freundlichen Grüßen Marc Haunschild https://Accessibility.Consulting > Am 24.04.2024 um 09:56 schrieb Ginger Claassen <ginger.claassen@gmx.de>: > > 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 > >
Received on Thursday, 25 April 2024 05:30:12 UTC