• Responsive Survey Form Design

    Introduction to forms

    An HTML form is a section of a document containing normal content, markup, special elements called controls (checkboxes, radio buttons, menus, etc.), and labels on those controls. Users generally "complete" a form by modifying its controls (entering text, selecting menu items, etc.), before submitting the form to an agent for processing (e.g., to a Web server, to a mail server, etc.)

    Here's a simple form that includes labels, radio buttons, and push buttons (reset the form or submit it):

    <FORM action="http://somesite.com/prog/adduser" method="post">
        <P>
        <LABEL for="firstname">First name: </LABEL>
                  <INPUT type="text" id="firstname"><BR>
        <LABEL for="lastname">Last name: </LABEL>
                  <INPUT type="text" id="lastname"><BR>
        <LABEL for="email">email: </LABEL>
                  <INPUT type="text" id="email"><BR>
        <INPUT type="radio" name="sex" value="Male"> Male<BR>
        <INPUT type="radio" name="sex" value="Female"> Female<BR>
        <INPUT type="submit" value="Send"> <INPUT type="reset">
        </P>
     </FORM>

    Controls

    Users interact with forms through named controls.

    A control's "control name" is given by its name attribute. The scope of the name attribute for a control within a FORM element is the FORM element

    Each control has both an initial value and a current value, both of which are character strings. Please consult the definition of each control for information about initial values and possible constraints on values imposed by the control. In general, a control's "initial value" may be specified with the control element's value attribute. However, the initial value of a TEXTAREA element is given by its contents, and the initial value of an OBJECT element in a form is determined by the object implementation (i.e., it lies outside the scope of this specification).

    Control Types

    HTML defines the following control types:

    buttons
    Authors may create three types of buttons:
    • submit buttons: When activated, a submit button submits a form. A form may contain more than one submit button.
    • reset buttons: When activated, a reset button resets all controls to their initial values.
    • push buttons: Push buttons have no default behavior. Each push button may have client-side scripts associated with the element's event attributes. When an event occurs (e.g., the user presses the button, releases it, etc.), the associated script is triggered.

      Authors should specify the scripting language of a push button script through a default script declaration (with the META element).

    Authors create buttons with the BUTTON element or the INPUT element. Please consult the definitions of these elements for details about specifying different button types.

    Note. Authors should note that the BUTTON element offers richer rendering capabilities than the INPUT element.

    checkboxes
    Checkboxes (and radio buttons) are on/off switches that may be toggled by the user. A switch is "on" when the control element's checked attribute is set. When a form is submitted, only "on" checkbox controls can become successful.

    Several checkboxes in a form may share the same control name. Thus, for example, checkboxes allow users to select several values for the same property. The INPUT element is used to create a checkbox control.

    radio buttons
    Radio buttons are like checkboxes except that when several share the same control name, they are mutually exclusive: when one is switched "on", all others with the same name are switched "off". The INPUT element is used to create a radio button control.
    If no radio button in a set sharing the same control name is initially "on", user agent behavior for choosing which control is initially "on" is undefined. Note. Since existing implementations handle this case differently, the current specification differs from RFC 1866 ([RFC1866] section 8.1.2.4), which states:
    At all times, exactly one of the radio buttons in a set is checked. If none of the <INPUT> elements of a set of radio buttons specifies `CHECKED', then the user agent must check the first radio button of the set initially.

    Since user agent behavior differs, authors should ensure that in each set of radio buttons that one is initially "on"

    menus
    Menus offer users options from which to choose. The SELECT element creates a menu, in combination with the OPTGROUP and OPTION elements.
    text input
    Authors may create two types of controls that allow users to input text. The INPUT element creates a single-line input control and the TEXTAREA element creates a multi-line input control. In both cases, the input text becomes the control's current value.
    file select
    This control type allows the user to select files so that their contents may be submitted with a form. The INPUT element is used to create a file select control.
    hidden controls
    Authors may create controls that are not rendered but whose values are submitted with a form. Authors generally use this control type to store information between client/server exchanges that would otherwise be lost due to the stateless nature of HTTP (see [RFC2616]). The INPUT element is used to create a hidden control.
    object controls
    Authors may insert generic objects in forms such that associated values are submitted along with other controls. Authors create object controls with the OBJECT element.

    The elements used to create controls generally appear inside a FORM element, but may also appear outside of a FORM element declaration when they are used to build user interfaces. This is discussed in the section on intrinsic events. Note that controls outside a form cannot be successful controls.

    The following Form is the example design of FreeCodeCamp. I Design this form From The Course of Responsive Web Design where CodePen was the online Code Editor

    Code Editor: CodePen (FreeCodeCamp)

    ElementsHTML5, CSS3 .

    Supported Devices: Full Responsive for Mobiles, TAB, NOTES and PADS.

    please rate my work, so that I can get more confidence for  responsive websites.

    Also connect with me and get my popular working sites on-

    Github: https://github.com/Mohammad-Asif-Web

    linkedIn:https://www.linkedin.com/in/mohammadasif10/

    Facebook: https://www.facebook.com/alexasifhhossain/


    Thank you!


  • 1 comment:

    GET A FREE DAD JOKES NOW

    --Use Your Brain As A Processor Not As A Hard Disk..

    ADDRESS

    91/2 R, M, DAS ROAD, SUTRAPUR. DHAKA-1100

    EMAIL

    alexasifhhossain@gmail.com
    asifhossainhridoy10@gmail.com

    MOBILE

    +8801682240802
    +8801940929414