Consider a form with method="post". What is the main difference in how data is sent compared to method="get"?
Think about where the data is placed in the HTTP request for POST vs GET.
When a form uses method="post", the data is sent inside the HTTP request body. This keeps the data out of the URL, unlike GET where data appears in the URL query string.
In an HTML form, which attribute defines the URL where the form data is sent after submission?
It usually looks like a URL or path.
The action attribute specifies the URL where the form data is sent when the form is submitted.
Given this HTML form snippet, what will the user see in the browser?
<form action="/submit" method="get"> <label for="email">Email:</label> <input type="email" id="email" name="email" required> <button type="submit">Send</button> </form>
Look at the type and label elements.
The label is linked to the email input by for and id. The input type is email, so the browser enforces email format. The button text is 'Send'.
You want to style only the submit button inside any form on the page. Which CSS selector achieves this?
Look for a selector that targets buttons with a specific attribute inside forms.
The selector form button[type="submit"] targets all button elements with type="submit" inside any form. Option A targets input elements, not button elements.
Which practice improves accessibility for screen reader users when filling out forms?
Think about how screen readers identify form fields.
Properly linked label elements ensure screen readers announce the label when the input is focused. Placeholders alone are not sufficient because they disappear when typing and are not always read by screen readers.