Disabled state styling in Tailwind - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the disabled attribute do in HTML form elements?

It makes the form element unclickable and uneditable by the user. The element is also skipped when tabbing through the page.

beginner

How do you apply a gray background and change cursor to not-allowed for a disabled button using Tailwind CSS?

Use bg-gray-300 for background and cursor-not-allowed to show the disabled cursor style.

intermediate

Which Tailwind CSS variant targets disabled elements for styling?

The disabled: variant applies styles only when the element has the disabled attribute.

beginner

Why is it important to style disabled elements differently?

It helps users understand which elements are inactive or unavailable, improving usability and accessibility.

intermediate

How can you ensure disabled buttons are accessible for keyboard users?

Disabled buttons should not be focusable. The disabled attribute automatically removes them from the tab order.

Which Tailwind CSS class changes the cursor to indicate a disabled element?

A cursor-not-allowed

B cursor-pointer

C cursor-default

D cursor-wait

The class cursor-not-allowed changes the cursor to a symbol that indicates the element is disabled.

What does the disabled: prefix in Tailwind CSS do?

A Applies styles on hover

B Applies styles only when the element is disabled

C Applies styles on focus

D Applies styles on active state

The disabled: variant applies styles only if the element has the disabled attribute.

Which HTML attribute disables a button so it cannot be clicked?

A readonly

B hidden

C inert

D disabled

The disabled attribute disables the button, making it unclickable and unfocusable.

Why should disabled elements have a different visual style?

A To show they are inactive or unavailable

B To make the page colorful

C To confuse users

D To increase page load speed

Different styling helps users recognize which elements are inactive or unavailable.

Which Tailwind class would you use to make a disabled button's background light gray?

A bg-blue-500

B bg-red-600

C bg-gray-300

D bg-green-200

The class bg-gray-300 applies a light gray background, commonly used for disabled elements.

Explain how to style a disabled button using Tailwind CSS and why it is important.

Think about how users know a button is inactive.

Describe the accessibility benefits of using the disabled attribute on form elements.

Consider keyboard and screen reader users.

Practice

1. What does the disabled: prefix in Tailwind CSS do?

easy

A. Removes the element from the page

B. Disables the element functionality

C. Applies styles only when the element has the disabled attribute

D. Makes the element visible only on hover

Solution

1. Step 1: Understand the disabled attribute

   The HTML disabled attribute marks an element as inactive or unusable.

2. Step 2: Role of Tailwind's disabled: prefix

   The disabled: prefix applies CSS styles only when the element is disabled, allowing visual changes without affecting functionality.

3. Final Answer:

   Applies styles only when the element has the disabled attribute -> Option C

4. Quick Check:

   disabled: prefix = style on disabled [OK]

Hint: Remember disabled: styles only affect disabled elements [OK]

Common Mistakes:

• Thinking disabled: disables functionality
• Confusing disabled: with hover: or focus:
• Assuming disabled: removes elements

2. Which Tailwind CSS class correctly changes the cursor to 'not-allowed' when a button is disabled?

easy

A. disabled:cursor-not-allowed

B. cursor-not-allowed

C. cursor-disabled

D. disabled:cursor-disabled

Solution

1. Step 1: Identify the cursor style for disabled state

   The cursor style for disabled elements is not-allowed, which shows a 'no' symbol.

2. Step 2: Use Tailwind's disabled prefix

   To apply this style only when disabled, use disabled:cursor-not-allowed. Plain cursor-not-allowed applies always.

3. Final Answer:

   disabled:cursor-not-allowed -> Option A

4. Quick Check:

   disabled:cursor-not-allowed = correct syntax [OK]

Hint: Use disabled: prefix before cursor class for disabled styling [OK]

Common Mistakes:

• Using cursor-not-allowed without disabled:
• Using non-existent cursor-disabled class
• Placing disabled: after the class name

3. What will be the background color of this button when disabled?

<button disabled class="bg-blue-500 disabled:bg-gray-400">Click me</button>

medium

A. Red (#ef4444)

B. Blue (#3b82f6)

C. No background color

D. Gray (#9ca3af)

Solution

1. Step 1: Check the button's disabled attribute

   The button has the disabled attribute, so disabled styles apply.

2. Step 2: Analyze Tailwind classes for background

   The normal background is bg-blue-500. When disabled, disabled:bg-gray-400 overrides it to gray.

3. Final Answer:

   Gray (#9ca3af) -> Option D

4. Quick Check:

   disabled attribute triggers disabled:bg-gray-400 [OK]

Hint: Disabled attribute triggers disabled: styles override base [OK]

Common Mistakes:

• Ignoring disabled: prefix effect
• Assuming base bg-blue-500 stays
• Confusing gray-400 with gray-500

4. Identify the error in this Tailwind usage for disabled styling:

<input disabled class="disabled:bg-gray-300 cursor-not-allowed" />

medium

A. Cursor style should use disabled: prefix

B. Cannot style input elements with Tailwind

C. disabled:bg-gray-300 is invalid syntax

D. Missing disabled attribute on input

Solution

1. Step 1: Check the disabled attribute presence

   The input has the disabled attribute, so disabled styles can apply.

2. Step 2: Analyze cursor style usage

   The cursor style cursor-not-allowed applies always. To apply only when disabled, it should be disabled:cursor-not-allowed.

3. Final Answer:

   Cursor style should use disabled: prefix -> Option A

4. Quick Check:

   Cursor needs disabled: prefix for disabled state [OK]

Hint: Add disabled: prefix to cursor styles for disabled elements [OK]

Common Mistakes:

• Forgetting disabled: prefix on cursor
• Thinking disabled:bg-gray-300 is wrong
• Assuming inputs can't be styled

5. You want a button to have a blue background normally, but when disabled, it should have a gray background and the text should be lighter gray. Which Tailwind classes achieve this?

hard

A. bg-blue-600 disabled:bg-gray-400 text-white text-gray-300

B. bg-blue-600 disabled:bg-gray-400 disabled:text-gray-300 text-white

C. bg-blue-600 bg-gray-400 disabled:text-gray-300 text-white

D. bg-blue-600 disabled:bg-gray-400 text-gray-300 disabled:text-white

Solution

1. Step 1: Set normal background and text colors

   Use bg-blue-600 for blue background and text-white for white text normally.

2. Step 2: Apply disabled styles with prefix

   Use disabled:bg-gray-400 for gray background and disabled:text-gray-300 for lighter gray text when disabled.

3. Step 3: Verify order and prefixes

   Classes must have disabled: prefix for disabled styles; base styles apply otherwise.

4. Final Answer:

   bg-blue-600 disabled:bg-gray-400 disabled:text-gray-300 text-white -> Option B

5. Quick Check:

   Disabled styles need disabled: prefix [OK]

Hint: Use disabled: prefix on all styles changing when disabled [OK]

Common Mistakes:

• Missing disabled: prefix on text color
• Placing disabled classes without prefix
• Mixing order causing style override issues