Project Proposal
Project Proposal
Professor Littleton
CDA4010: User Interface Design
Team:
Angel Selva Rodriguez
Jimmy Pena
Benton Lamlein
John Armon Antolin
Karli Dattilo
Section 1: Platform
The same principle will be applicable for the footer. The footer
section will not be added as a main part of the page.
If possible, the footer section will be hidden when filling out the
form. This will allow users to complete the form faster since their
attention will be centered on the form itself and not in the
adjacent elements of the page. There will be no lateral bar or
lateral navigation bar while filling out the form. This will maximize
the space available for the form. It will also allow us to use bigger
fonts and fields.
This also will help people with some sort of visual disability. Since
the space for fonts and fields will be maximized. The attention of
the people that are easy-distractible will be focused on the big
section of the page. This section will contain the fields and labels
that will indicate the users the actions to take and what is next to
do.
The text displayed below the validated field will be big enough so
the user can notice that there is an error. The user will also be
able to clearly read what is the error.
For people that cannot read, adding a clear and precise error
message will help their page-reading software to convey to them
what the error is. This type of software is capable of
understanding what parts of the page labels are and ready them
back to the user.
For the sake of clarity, validation will happen both client side and
server side. Visual feedback in the form of red text will indicate to
the user that the input they have just completed is not
acceptable. So to not confuse the user, there will be no “greying
out” of the submit button unless all of the fields are validated.
Instead the user will be able to submit, but the page will just
refresh and alert the user to the fields they must correct. What
happened and how to fix it will be clearly displayed. To aid in
accessibility default HTML5 input types will be used. Default input
types like: <button>, <checkbox>, <date>, <email>, <file>,
<number>, <password>, <text>, and others. are easily dealt
with by screen readers and other assistive technology. This will
also make coding easier as most of the functionality is built in.
● Type error - if the user inputs anything but a number into the
field.
○ “Please only enter numbers”
● Length error - There will likely be an upper and lower limit to
the size of most number inputs.
○ “Phone number must be at least 8 digits”
Empty Errors
● Incomplete form - if the user has not filled out the necessary
fields to progress the form.
○ “Please fill out Last Name before submitting”
Section 8: Omitted Questions from Original Form
This section will be like the original application form with minor
adjustments:
• The maiden name will be omitted as reasoned out in
section 8 of this document.
Education
This section will be like the original application form with minor
wording adjustments:
• School types will only show the options high school and
college because the enumeration of undergraduate, graduate,
post-graduate and professional can be determined when the
major/degree/certificate section is filled
Employment History
References
The reference section will have minor changes:
To move forward with the hiring process, I agree to the terms and
conditions below. My at-will status with Unfinished Business will
not change for any reason like: