Overriding color palette in Tailwind - Practice Problems & Coding Challenges

Challenge - 5 Problems

📝 Syntax

intermediate

Correct way to override a color in Tailwind config

You want to override the default blue color in your Tailwind CSS configuration to a custom hex value #1E40AF. Which option correctly overrides the blue color without removing other default colors?

Tailwind

module.exports = {
  theme: {
    extend: {
      colors: {
        blue: '#1E40AF',
      },
    },
  },
};

A module.exports = { theme: { extend: { colors: { blue: '#1E40AF' } } } };

B module.exports = { theme: { colors: { blue: '#1E40AF' } } };

C module.exports = { theme: { extend: { blue: '#1E40AF' } } };

D module.exports = { extend: { colors: { blue: '#1E40AF' } } };

💡 Hint

Use the extend key inside theme to add or override colors without removing defaults.

In Tailwind CSS, to override or add to the default theme colors, you must use extend inside the theme object. Option A correctly places the new blue color inside extend.colors, preserving other default colors.

🧠 Conceptual

intermediate

Effect of overriding colors without extend

What happens if you override the colors object directly inside theme in Tailwind config without using extend?

A The colors are ignored and default colors remain unchanged.

B Your custom colors are merged with default colors automatically.

C All default colors are replaced, only your custom colors remain.

D Tailwind throws a configuration error and fails to build.

💡 Hint

Think about what happens when you replace an object instead of extending it.

When you override the colors object directly inside theme, Tailwind replaces the entire default colors object with yours. This means only your custom colors are available, and all default colors are lost.

❓ selector

advanced

Using custom color in Tailwind CSS class

After overriding the primary color in your Tailwind config with #FF5733, which class will correctly apply this color as a background?

A bg-primary

B background-primary

C bg-primary-500

D background-primary-500

💡 Hint

Tailwind uses bg- prefix for background colors and the exact key name for custom colors.

When you add a custom color named primary in Tailwind config, you use bg-primary to apply it as a background color. The -500 suffix is used only for default color scales, not for single custom colors.

❓ layout

advanced

Responsive color override with Tailwind

You want the background color to be primary on small screens and secondary on medium and larger screens. Which class combination achieves this?

A bg-secondary md:bg-primary

B bg-primary md:bg-secondary

C md:bg-primary bg-secondary

D bg-primary bg-secondary md:bg-primary

💡 Hint

Tailwind uses prefixes like md: to apply styles at certain screen sizes.

The class bg-primary applies the background color on all screens by default. The md:bg-secondary overrides it on medium and larger screens. This combination sets primary on small and secondary on medium+ screens.

❓ accessibility

expert

Ensuring accessible contrast with custom colors

You override Tailwind's color palette with a custom brand color #123456. What should you do to ensure text using brand background is accessible for users with visual impairments?

A Add <code>aria-hidden="true"</code> to elements with <code>brand</code> background.

B Use the <code>brand</code> color for both background and text for consistency.

C Only rely on default Tailwind colors for text to ensure accessibility.

D Check contrast ratio and add a custom text color that meets WCAG standards.

💡 Hint

Accessibility means good contrast between text and background colors.

Custom colors may not have enough contrast with default text colors. To ensure accessibility, check the contrast ratio (using tools) and define a text color that meets WCAG guidelines when used on the custom background.