IT Service Request Forms Style Guide

A knowledge base article about IT Service Request Forms Style Guide provided by the UC Berkeley IT Service Hub - Knowledge Portal

Images form Categories and Items will be match higher level categories from the existing technology.berkeley.edu site.
Images should be 128 x 128.
Service Titles and definition/description wording will be pulled from the existing technology.berkeley.edusite.
Order and organization of the forms and service categories will be pulled from the existing technology.berkeley.edu site.
Question wording/phrasing will be changed to be consistent, in the same voice, when needed.
Contingent questions will use the wording: “If you answered yes to the above question, [insert next question/contingent question here]?” Ie. "If you answered yes to the above question, which database platform is the source database?"
Question formats will be changed to be most efficient where needed (ie. First Name/Last Name, will be combined into one user lookup question).
Answer formats will be changed to optimize functionality where needed (ie. Name → Blank Text Box to Fill, will be changed to Name → User lookup).
Title case for anything that is a title, sentence case for everything else will be used throughout all forms (ie. Questions, more information sections, descriptions).
Form layouts will be consistent (single column vs. double column, banners, etc.)
Links out to other websites for more information will remain in the technology.berkeley.edu, more information in each form will not include major links to outside information.
Forms will be one page (does not limit the number of questions).
No conditional questions.
No customized notifications.
No pop-ups.
Html can be added in the long description of a form, but you cannot put it anywhere else (ie. "more information").
H1 for heading/title in description.