WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: wcag 3.3.4

for

From: Jonathan Avila
Date: Jul 18, 2016 8:42AM

> . The Place Order button is disabled until all fields are completed and validated (e.g., if the CC # is incorrect, a message is dynamically displayed).

My concern is that some users may not understand why the place order button is not available and additionally some screen reader users may tend to use the tab key for form input and may become confused when the place order button that is disabled is not in the focus order. I'm not advocating disabled buttons to generally be in the focus order -- but I would recommend a message perhaps that was in the focus order when the button was disabled to alert users to the situation.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group
<EMAIL REMOVED>
703.637.8957 (Office)
Visit us online: Website | Twitter | Facebook | Linkedin | Blog
Check out our Digital Accessibility Webinars!


-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Jennison Mark Asuncion
Sent: Thursday, July 14, 2016 5:42 PM
To: webaim-forum
Subject: [WebAIM] wcag 3.3.4

Looking for a sanity check - imagine a screen with fields: credit card #, month and year of expiration, and postal code. The Place Order button is disabled until all fields are completed and validated (e.g., if the CC # is incorrect, a message is dynamically displayed). Once the Place Order button is pressed, the order is in fact being placed, and there is text letting the user know this is the case.

Based on WCAG 3.3.4, one of the following must be true:
1) Reversible: Submissions are reversible.
2) Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
3) Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

Based on this, I am saying this meets 3.3.4, specifically #2. Am I on track?

Jennison