WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Whether or not to disable form submit button

for

From: jp Jamous
Date: Dec 17, 2023 2:50PM

1. Most developers use the disabled attribute and not aria-disabled. It is important to keep an eye on this one.
2. Aria-disabled is rendered through the accessibility tree, which makes it discoverable by assistive technologies. What would happen to keyboard only users?
I am not trying to argue with anyone on the list. I just like to remind folks that WCAG does not only focus on users with assistive technologies. There are many users that fall under the cognitive and motor categories. Many of them do not use Ats. It is important for us as accessibility professionals not to fall in the same trap like UX Designers. We

The approach I mentioned, which validates each form field once focus is lost, can accomplish the following:
1. Informs all users of the invalid field before the user proceeds. This helps keep those with certain cognitive disabilities focused on filling out the various parts of a form, especially if it is lengthy.
2. Reduces overhead navigation, because both screen reader and keyboard only users would not have to navigate from the Submit button back to the various form elements that failed validation. overhead navigation.
3. Provides a client-side validation approach, which would eliminate unnecessary postback to the server. This can be very helpful for mobile users or those with poor internet connections.
4. Standardizes the form validation, which provides an efficient user experience for various types of users and avoids using the disabled attribute on the Submit button.

Again my 2 cents. 😊