Naming conventions in CSS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding BEM Naming Convention

Which of the following CSS class names correctly follows the BEM (Block Element Modifier) naming convention for a button component with a disabled state?

A button_disabled

B button--disabled

C button__disabled

D button-disabled

💡 Hint

BEM uses double hyphens for modifiers and double underscores for elements.

In BEM, modifiers use double hyphens --. So button--disabled is correct for a disabled modifier of the button block.

📝 Syntax

intermediate

Valid CSS Class Name Syntax

Which of these CSS class names is invalid according to CSS naming rules?

A 2nd-section

B footer_nav

C _header-main

D contentArea

💡 Hint

CSS class names cannot start with a digit.

CSS class names cannot start with a number. Option A starts with '2', so it is invalid.

❓ selector

advanced

Selector Specificity with Naming Conventions

Given these CSS classes, which selector has the highest specificity?

CSS

.nav__item { color: blue; }
.nav--active .nav__item { color: red; }
.nav__item--highlighted { color: green; }

A .nav--active .nav__item

B .nav__item, .nav--active

C .nav__item--highlighted

D .nav__item

💡 Hint

More class selectors in a selector increase specificity.

Option A has two class selectors combined, so it has higher specificity than the single-class selectors in A and C.

❓ layout

advanced

Naming Conventions Impact on CSS Grid Layout

If you have a CSS Grid container named grid-container and grid items named grid-item--large and grid-item--small, which CSS rule correctly applies a larger grid area to the large item using these class names?

A .grid-container .grid-item-large { grid-area: 1 / 1 / 3 / 3; }

B .grid-item_large { grid-area: 1 / 1 / 3 / 3; }

C .grid-item--small { grid-area: 1 / 1 / 3 / 3; }

D .grid-item--large { grid-area: 1 / 1 / 3 / 3; }

💡 Hint

Match the exact class name with correct syntax.

Option D uses the exact class name grid-item--large with correct CSS syntax to assign the grid area.

❓ accessibility

expert

Naming Conventions and Accessibility in CSS

Which naming convention practice best supports accessibility when styling components for screen readers and keyboard navigation?

A Use only IDs for styling to ensure uniqueness and avoid confusion.

B Use short, generic class names like <code>a1</code>, <code>b2</code> to keep CSS file size small.

C Use descriptive class names that reflect the component role, like <code>btn-submit</code> or <code>nav-link</code>.

D Avoid naming conventions and rely on inline styles for accessibility.

💡 Hint

Good naming helps assistive technologies understand page structure.

Descriptive class names help developers and assistive tools understand the purpose of elements, improving accessibility.

Practice

1. Which of the following is the best practice for naming CSS classes?

easy

A. Use camelCase, like mainHeader.

B. Use uppercase letters and underscores, like Main_Header.

C. Use lowercase letters and hyphens to separate words, like main-header.

D. Use spaces between words, like main header.

Solution

1. Step 1: Understand common CSS naming styles

   CSS classes should be easy to read and consistent. Lowercase with hyphens is widely accepted.

2. Step 2: Compare options

   Use lowercase letters and hyphens to separate words, like main-header. uses lowercase and hyphens, which is recommended. Options B and C use uppercase or camelCase, less common in CSS. Use spaces between words, like main header. uses spaces, which is invalid in class names.

3. Final Answer:

   Use lowercase letters and hyphens to separate words, like main-header. -> Option C

4. Quick Check:

   Lowercase + hyphens = best CSS naming [OK]

Hint: Use lowercase and hyphens for CSS classes [OK]

Common Mistakes:

• Using spaces in class names
• Using uppercase letters
• Using camelCase instead of hyphens

2. Which CSS class name follows the BEM naming convention?

easy

A. button--primary

B. button_primary

C. buttonPrimary

D. button primary

Solution

1. Step 1: Recall BEM naming rules

   BEM uses block__element--modifier format. Double hyphens separate modifiers.

2. Step 2: Identify correct format

   button--primary uses double hyphens for modifier --primary, matching BEM. Options A and B use camelCase or underscores, not BEM. button primary uses space, invalid in class names.

3. Final Answer:

   button--primary -> Option A

4. Quick Check:

   BEM modifier uses double hyphens [OK]

Hint: BEM modifiers use double hyphens (--modifier) [OK]

Common Mistakes:

• Using underscores instead of hyphens
• Using camelCase for BEM
• Using spaces in class names

3. Given this CSS class name: card__title--large, what does it represent in BEM?

medium

A. Block: card, Modifier: title, Element: large

B. Modifier: card, Block: title, Element: large

C. Element: card, Block: title, Modifier: large

D. Block: card, Element: title, Modifier: large

Solution

1. Step 1: Break down the BEM parts

   In card__title--large, card is the block, title is the element (after double underscore), and large is the modifier (after double hyphen).

2. Step 2: Match parts to options

   Block: card, Element: title, Modifier: large correctly identifies block, element, and modifier. Other options mix these parts incorrectly.

3. Final Answer:

   Block: card, Element: title, Modifier: large -> Option D

4. Quick Check:

   BEM = block__element--modifier [OK]

Hint: BEM: block__element--modifier order [OK]

Common Mistakes:

• Confusing element and modifier positions
• Mixing block and element names
• Ignoring double underscores and hyphens

4. Identify the error in this CSS class name: nav__item_active

medium

A. Class name is too long

B. Underscore used instead of double hyphen for modifier

C. Spaces are used instead of underscores

D. Double underscore missing between block and element

Solution

1. Step 1: Check BEM syntax

   BEM requires modifiers to be separated by double hyphens --, not underscores.

2. Step 2: Analyze the class name

   The class nav__item_active uses a single underscore for the modifier, which is incorrect. It should be nav__item--active.

3. Final Answer:

   Underscore used instead of double hyphen for modifier -> Option B

4. Quick Check:

   Modifier separator = double hyphen [OK]

Hint: Modifiers need double hyphens, not underscores [OK]

Common Mistakes:

• Using single underscore for modifiers
• Forgetting double underscore between block and element
• Using spaces in class names

5. You want to create CSS classes for a card component with a title and a highlighted state using BEM. Which naming set is correct?

hard

A. card, card__title, card--highlighted

B. card, card_title, card_highlighted

C. card, card-title, card-highlighted

D. card, card__title--highlighted, card__highlighted

Solution

1. Step 1: Understand BEM structure for blocks, elements, and modifiers

   Block is card. Element is card__title. Modifier on block is card--highlighted.

2. Step 2: Evaluate options

   card, card__title, card--highlighted correctly uses BEM naming. card, card_title, card_highlighted uses underscores, not BEM. card, card-title, card-highlighted uses hyphens but not BEM format. card, card__title--highlighted, card__highlighted incorrectly applies modifier to element and duplicates modifier.

3. Final Answer:

   card, card__title, card--highlighted -> Option A

4. Quick Check:

   BEM block, element, modifier naming [OK]

Hint: BEM: block, block__element, block--modifier [OK]

Common Mistakes:

• Using underscores instead of BEM separators
• Applying modifiers to elements incorrectly
• Mixing hyphen and underscore styles