You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Back" "Next" "Submit" buttons are in a fixed position on the screen
On form screens, the "Next" button should shift to "Submit" if any of the form fields are used. For example, if email address is entered, "Message" field becomes required
Utilize in-line validation to ensure all required fields are completed
"Submit" button should be grayed out if all required fields are not completed. Required fields: anywhere where data is entered. We're only asking for necessary information so all will be required
Email addresses should be checked as a valid pattern/format
For EFO, committee ID should match committee_id pattern (e.g. C{0-9}^8(?)), but doesn't necessarily have to be a valid committee. Offer the same kind of lookup used in RAD form? If committee isn't found in the lookup, offer a way to still enter what the form user knows
What we're after:
We're developing an agency contact form, primarily for use by prominently public-facing offices.
Related issues
Form features:
C{0-9}^8(?)), but doesn't necessarily have to be a valid committee. Offer the same kind of lookup used in RAD form? If committee isn't found in the lookup, offer a way to still enter what the form user knowsPrototype:
https://invis.io/3812YD5HUQMK
Completion criteria