Free Online Flashcard Deck

7 Forms and User Input Free Online FlashCards

Study 7 Forms and User Input with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.

12 cards
01
Front

What is the purpose of an HTML <form>?

Back

A <form> groups related controls for collecting and submitting information.

02
Front

How do you explicitly associate a label with a form control?

Back

Give each control a visible label and connect them with matching for and id values.

03
Front

How should related radio buttons be grouped accessibly?

Back

Use <fieldset> to group related controls and <legend> to describe the group.

04
Front

What does a control's name attribute do?

Back

The name attribute identifies a control's value in submitted form data; controls without a name are generally omitted.

05
Front

How can input type and autocomplete improve a form?

Back

An appropriate type, such as email, and useful autocomplete values help browsers and users enter data.

06
Front

What does a form's action attribute specify?

Back

The action attribute specifies where the browser sends the form.

07
Front

How does GET send form values, and what is it suitable for?

Back

GET places form values in the URL and suits requests such as searches.

08
Front

How does POST send form values, and when is it commonly used?

Back

POST sends form values in the request body and is commonly used when submitting or changing data.

09
Front

How should native validation requirements be communicated?

Back

Use visible instructions alongside native constraints such as required, email, minlength, maxlength, min, and max.

10
Front

Why are client-side checks not a security boundary?

Back

Client-side checks improve usability but are not a security boundary; users can alter page code or bypass the page.

11
Front

What validation must happen on the server?

Back

Validate submitted data on the server too, and handle invalid or unexpected values safely.

12
Front

Why handle a form's submit event instead of only a button click?

Back

Listen for the form's submit event so keyboard-based submission is handled, not just button clicks.