Attribute best practices in HTML - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add an alternative text for the image for accessibility.

HTML

<img src="flower.jpg" alt=[1]>

Drag options to blanks, or click blank then click option'

A"flower.jpg"

Bflower

Cimage

D"A beautiful red flower"

Attempts:

3 left

💡 Hint

Common Mistakes

Leaving alt empty or missing

Using the image filename as alt text

Using non-descriptive words like 'image' or 'flower'

The alt attribute should describe the image content for screen readers. It needs to be a descriptive text in quotes.

2fill in blank

medium

Complete the code to make the link open in a new tab safely.

HTML

<a href="https://example.com" target=[1] rel="noopener noreferrer">Visit</a>

Drag options to blanks, or click blank then click option'

A"_self"

B"_blank"

C"_parent"

D"_top"

Attempts:

3 left

💡 Hint

Common Mistakes

Using target="_self" which opens in the same tab

Forgetting rel="noopener noreferrer" causing security risks

Using invalid target values

The target="_blank" attribute opens the link in a new tab. The rel="noopener noreferrer" improves security and performance.

3fill in blank

hard

Fix the error by completing the code to correctly label the input for accessibility.

HTML

<label for=[1]>Name:</label>
<input type="text" id="name" name="name">

Drag options to blanks, or click blank then click option'

A"name"

B"username"

C"inputName"

D"user"

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatching label for and input id

Using different or missing ids

Not using a label at all

The for attribute in the label must match the id of the input it labels. Here, both should be "name".

4fill in blank

hard

Fill both blanks to create a button that is disabled and has an accessible label.

HTML

<button type=[1] disabled=[2] aria-label="Submit form">Send</button>

Drag options to blanks, or click blank then click option'

A"submit"

B"button"

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using type="button" which does not submit forms

Setting disabled to false when intending to disable

Missing aria-label for accessibility

The button type should be "submit" to send form data. The disabled attribute is set to true to disable the button. The aria-label helps screen readers understand the button's purpose.

5fill in blank

hard

Fill all three blanks to create an input with a placeholder, required attribute, and a descriptive aria-label.

HTML

<input type=[1] placeholder=[2] required=[3] aria-label="Enter your email address">

Drag options to blanks, or click blank then click option'

A"text"

B"email"

C"Enter your email"

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using type="text" instead of "email"

Omitting the required attribute

Not providing an aria-label for accessibility

The input type should be "email" to validate email addresses. The placeholder shows example text inside the input. The required attribute set to true makes the field mandatory. The aria-label describes the input for screen readers.

Practice

1. Which of the following is the best practice for writing HTML attributes?

easy

A. Always use quotes around attribute values, even if not required.

B. Omit quotes to make the code shorter.

C. Use uppercase letters for attribute names.

D. Write attribute values without spaces only.

Solution

1. Step 1: Understand attribute syntax rules

   HTML allows attribute values without quotes only if they contain no spaces or special characters, but quotes improve clarity and prevent errors.

2. Step 2: Recognize best practice for readability and compatibility

   Using quotes consistently around attribute values ensures the code works well across browsers and is easier to read.

3. Final Answer:

   Always use quotes around attribute values, even if not required. -> Option A

4. Quick Check:

   Quotes improve clarity and prevent errors [OK]

Hint: Always put quotes around attribute values for safety [OK]

Common Mistakes:

• Skipping quotes causes parsing errors
• Using uppercase attribute names (should be lowercase)
• Assuming quotes are optional always

2. Which of the following is the correct syntax for adding an alt attribute to an image?

easy

A.

B.

C.

D.

Solution

1. Step 1: Check attribute value syntax

   The alt attribute must have a value describing the image, enclosed in quotes for best practice.

2. Step 2: Identify the correct option

   <img src='photo.jpg' alt='Beautiful sunset'> uses quotes around the descriptive text, making it valid and accessible.

3. Final Answer:

   <img src='photo.jpg' alt='Beautiful sunset'> -> Option B

4. Quick Check:

   Alt text must be quoted and descriptive [OK]

Hint: Alt text always needs quotes and meaningful description [OK]

Common Mistakes:

• Leaving alt attribute empty or missing value
• Not using quotes around attribute values
• Using alt without value or with empty value

3. What will be the rendered result of this HTML snippet?

<button disabled>Click me</button>

medium

A. A clickable button labeled 'Click me'.

B. A button labeled 'disabled' instead of 'Click me'.

C. An error message in the browser.

D. A button labeled 'Click me' that is grayed out and cannot be clicked.

Solution

1. Step 1: Understand the disabled attribute effect

   The disabled attribute on a button makes it inactive and visually grayed out, preventing user interaction.

2. Step 2: Predict the visual and functional output

   The button text remains 'Click me', but the button cannot be clicked and appears disabled.

3. Final Answer:

   A button labeled 'Click me' that is grayed out and cannot be clicked. -> Option D

4. Quick Check:

   Disabled attribute disables button interaction [OK]

Hint: Disabled attribute disables and grays out form controls [OK]

Common Mistakes:

• Thinking disabled changes button text
• Expecting an error from disabled attribute
• Assuming button remains clickable

4. Identify the error in this HTML code snippet:

<a href=example.com target=_blank>Visit</a>

medium

A. Missing quotes around attribute values.

B. Incorrect tag name used.

C. The href attribute is not allowed on <a> tags.

D. The target attribute value should be 'self' instead of '_blank'.

Solution

1. Step 1: Check attribute value syntax

   Both href and target attribute values should be enclosed in quotes for proper HTML syntax.

2. Step 2: Confirm tag and attribute correctness

   The <a> tag supports href and target attributes; only quotes are missing.

3. Final Answer:

   Missing quotes around attribute values. -> Option A

4. Quick Check:

   Always quote attribute values for valid HTML [OK]

Hint: Always quote attribute values to avoid errors [OK]

Common Mistakes:

• Forgetting quotes around attribute values
• Confusing tag names
• Misunderstanding target attribute usage

5. You want to make a form input accessible and user-friendly. Which attribute usage is the best practice?

hard

A.

B.

C.

D.

Solution

1. Step 1: Understand accessibility attributes

   Using aria-label provides a clear description for screen readers, improving accessibility.

2. Step 2: Combine with placeholder and id for usability

   Including id and placeholder helps both visual users and assistive technologies understand the input purpose.

3. Final Answer:

   <input type='text' id='email' aria-label='Email address' placeholder='Enter email'> -> Option C

4. Quick Check:

   Use aria-label for accessibility plus placeholder for hints [OK]

Hint: Use aria-label plus placeholder for accessible inputs [OK]

Common Mistakes:

• Omitting aria-label reduces screen reader clarity
• Using aria-hidden hides input from assistive tech
• Relying only on placeholder for description