Alert and notification patterns in Tailwind - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a simple alert box with Tailwind CSS.

Tailwind

<div class="bg-[1]-100 border border-[1]-400 text-[1]-700 px-4 py-3 rounded relative" role="alert">
  <strong class="font-bold">Alert!</strong>
  <span class="block sm:inline">This is an alert message.</span>
</div>

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

Ared

Bgreen

Cblue

Dyellow

Attempts:

3 left

💡 Hint

Common Mistakes

Using a color that does not match the alert's purpose.

Forgetting to keep the color consistent across background, border, and text.

The alert box uses the red color scheme for background, border, and text to indicate an error or important alert.

2fill in blank

medium

Complete the code to add a close button to the alert with proper accessibility.

Tailwind

<button type="button" class="absolute top-0 bottom-0 right-0 px-4 py-3" aria-label="[1]">
  <svg class="fill-current h-6 w-6 text-gray-500" role="button" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 20 20">
    <title>Close</title>
    <path d="M14.348 5.652a1 1 0 00-1.414-1.414L10 7.172 7.066 4.238a1 1 0 10-1.414 1.414L8.586 10l-2.934 2.934a1 1 0 101.414 1.414L10 12.828l2.934 2.934a1 1 0 001.414-1.414L11.414 10l2.934-2.934z"/>
  </svg>
</button>

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

AClose alert

BDismiss

CClose notification

DRemove alert

Attempts:

3 left

💡 Hint

Common Mistakes

Using vague labels like 'Dismiss' without context.

Not including an aria-label at all.

The aria-label should clearly describe the button's action for screen readers. "Close alert" is clear and descriptive.

3fill in blank

hard

Fix the error in the Tailwind alert code to make the alert background color correct.

Tailwind

<div class="bg-[1]-500 border border-[1]-700 text-white px-4 py-3 rounded relative" role="alert">
  <strong class="font-bold">Success!</strong>
  <span class="block sm:inline">Your operation completed successfully.</span>
</div>

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

Ared

Bblue

Cgreen

Dyellow

Attempts:

3 left

💡 Hint

Common Mistakes

Using red for success alerts, which is confusing.

Mismatching background and border colors.

Green is the correct color for success alerts. Using green-500 for background and green-700 for border fits the success message.

4fill in blank

hard

Fill both blanks to create a warning alert with an icon and proper color.

Tailwind

<div class="flex items-center bg-[1]-100 border-l-4 border-[2]-500 text-[2]-700 p-4" role="alert">
  <svg class="fill-current w-6 h-6 mr-4" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 20 20">
    <path d="M10 15a1.5 1.5 0 110-3 1.5 1.5 0 010 3zm.25-9.75v4.5h-1.5v-4.5h1.5z"/>
  </svg>
  <p class="font-bold">Warning!</p>
</div>

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

Ayellow

Bred

Corange

Dblue

Attempts:

3 left

💡 Hint

Common Mistakes

Using red or orange which may confuse warning with error.

Mismatching colors between background and border.

Yellow is the standard color for warning alerts. Both background and border use yellow shades for consistency.

5fill in blank

hard

Fill all three blanks to create a responsive notification banner with Tailwind CSS.

Tailwind

<div class="fixed top-0 inset-x-0 bg-[1]-600 text-white p-4 flex justify-between items-center">
  <p class="text-sm font-medium">[2]</p>
  <button class="ml-4 text-white hover:text-[3]-200 focus:outline-none focus:ring-2 focus:ring-white rounded" aria-label="Close notification">
    &times;
  </button>
</div>

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

Ablue

BNew update available!

Dgreen

Attempts:

3 left

💡 Hint

Common Mistakes

Using mismatched colors for background and hover states.

Leaving the notification message blank or unclear.

The banner uses a blue background with white text. The message is "New update available!" and the close button changes to a lighter blue on hover for clarity.

Practice

1. What is the main purpose of an alert in a web page using Tailwind CSS?

easy

A. To decorate the page with colorful boxes

B. To quickly inform users about important messages or statuses

C. To create navigation menus

D. To add animations to images

Solution

1. Step 1: Understand the role of alerts

   Alerts are designed to catch user attention for important information like success, errors, or warnings.

2. Step 2: Differentiate alerts from other UI elements

   Alerts are not for decoration or navigation but for communication of status or messages.

3. Final Answer:

   To quickly inform users about important messages or statuses -> Option B

4. Quick Check:

   Alerts = Important user messages [OK]

Hint: Alerts are for important messages, not decoration [OK]

Common Mistakes:

• Thinking alerts are just decorative boxes
• Confusing alerts with navigation or layout elements
• Ignoring the purpose of user communication

2. Which Tailwind CSS class combination correctly styles a success alert with green background and white text?

easy

A. bg-green-500 text-white p-4 rounded

B. bg-red-500 text-black p-2 rounded

C. bg-yellow-300 text-gray-700 p-6 rounded

D. bg-blue-600 text-white p-1 rounded

Solution

1. Step 1: Identify success alert colors

   Success alerts typically use green backgrounds with white text for contrast.

2. Step 2: Match Tailwind classes

   bg-green-500 sets green background, text-white sets white text, p-4 adds padding, and rounded rounds corners.

3. Final Answer:

   <code>bg-green-500 text-white p-4 rounded</code> -> Option A

4. Quick Check:

   Green background + white text = success alert [OK]

Hint: Green background with white text means success alert [OK]

Common Mistakes:

• Using red or yellow for success alerts
• Forgetting padding or rounded corners
• Mixing text colors that reduce readability

3. What will be the visual result of this Tailwind alert code?

<div class="bg-red-100 border border-red-400 text-red-700 px-4 py-3 rounded relative" role="alert">
  <strong class="font-bold">Error!</strong>
  <span class="block sm:inline"> Something went wrong.</span>
</div>

medium

A. A yellow alert box with bold 'Warning!' and message 'Check your input.'

B. A green alert box with bold 'Success!' and message 'Operation completed.'

C. A blue alert box with italic 'Info' and message 'Please read carefully.'

D. A red alert box with bold 'Error!' and message 'Something went wrong.'

Solution

1. Step 1: Analyze the color classes

   bg-red-100, border-red-400, and text-red-700 create a red-themed alert indicating an error or danger.

2. Step 2: Read the content inside the alert

   The text includes a bold 'Error!' and a message 'Something went wrong.', matching the red error style.

3. Final Answer:

   A red alert box with bold 'Error!' and message 'Something went wrong.' -> Option D

4. Quick Check:

   Red colors + 'Error!' text = error alert [OK]

Hint: Red background and 'Error!' text means error alert [OK]

Common Mistakes:

• Confusing red alert with success or info
• Ignoring the role attribute for accessibility
• Misreading the text content inside the alert

4. Identify the error in this Tailwind alert code snippet:

<div class="bg-yellow-200 text-yellow-800 p-3 rounded">
  <strong>Warning!</strong> Please check your input.
</div>

medium

A. Missing role="alert" attribute for accessibility

B. Wrong color classes for a warning alert

C. Padding class p-3 is invalid in Tailwind

D. The <strong> tag should not be used inside alerts

Solution

1. Step 1: Check accessibility attributes

   Alerts should have role="alert" to notify assistive technologies about important messages.

2. Step 2: Verify color and padding classes

   bg-yellow-200 and text-yellow-800 are correct for warning alerts; p-3 is a valid padding class.

3. Final Answer:

   Missing role="alert" attribute for accessibility -> Option A

4. Quick Check:

   Accessibility needs role="alert" [OK]

Hint: Always add role="alert" for alert accessibility [OK]

Common Mistakes:

• Forgetting role attribute for screen readers
• Thinking padding classes are invalid
• Misunderstanding semantic tags usage

5. You want to create a dismissible info alert using Tailwind CSS that is accessible and responsive. Which combination of features should you include?

hard

A. Add role="dialog" and hide the alert on small screens

B. Use only bg-blue-500 and text-white classes without accessibility roles

C. Use role="alert", aria-live="polite", a close button with keyboard support, and responsive padding classes

D. Use aria-hidden="true" to hide the alert from screen readers

Solution

1. Step 1: Ensure accessibility with roles and live regions

   Use role="alert" and aria-live="polite" so screen readers announce the alert politely.

2. Step 2: Add a close button with keyboard support

   Make the alert dismissible by adding a button accessible via keyboard (e.g., tabindex and aria-label).

3. Step 3: Use responsive padding classes

   Apply padding classes like p-4 sm:p-6 to ensure good spacing on all screen sizes.

4. Final Answer:

   Use role="alert", aria-live="polite", a close button with keyboard support, and responsive padding classes -> Option C

5. Quick Check:

   Accessibility + dismissible + responsive = Use role="alert", aria-live="polite", a close button with keyboard support, and responsive padding classes [OK]

Hint: Combine accessibility roles, keyboard support, and responsive design [OK]

Common Mistakes:

• Ignoring accessibility roles
• Not providing keyboard support for dismiss button
• Hiding alerts from screen readers incorrectly