Contrast of disabled UI controls

I wonder if there is an opportunity in WCAG 2.1 to reconsider the exception for 1.4.3 with disabled UI controls.  Even though a control may be disable, the control will likely be available once the user has entered some text.  Being able to read the text of the control can in some situations be very helpful in figuring out what you need to do to get the control to be available.  Other times there is a control that is disabled until all input is submitted and the contrast makes it unreadable.  But having access to that text to know what the form will do before hand is very important to deciding whether a user may want to fill out the form or not.  For example, say there is a button that says signup for email which I don't want to do but I must enter data in the fields first before I know what the form is asking permission to do.  Sometimes I'll just enter fake data to see what the submit button actually says in order to figure out if I really want to fill out the form.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>
703.637.8957 (Office)
Visit us online: Website<http://www.ssbbartgroup.com/> | Twitter<https://twitter.com/SSBBARTGroup> | Facebook<https://www.facebook.com/ssbbartgroup> | Linkedin<https://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog/>
Check out our Digital Accessibility Webinars!<http://www.ssbbartgroup.com/webinars/>