Hidden and visibility control in Tailwind - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ rendering

intermediate

What will be visible in the browser?

Given the following HTML snippet styled with Tailwind CSS, which text will be visible when rendered in a browser?

Tailwind

<div class="hidden md:block">Hello</div><div class="block md:hidden">World</div>

A Only 'Hello' is visible on medium and larger screens

B Only 'World' is visible on medium and larger screens

C Both 'Hello' and 'World' are visible on all screen sizes

D Neither 'Hello' nor 'World' is visible on any screen size

💡 Hint

Think about how Tailwind's responsive prefixes like md: affect visibility classes.

The hidden class hides the element on all screen sizes. The md:block class makes the element visible as a block starting from medium screens (768px and up). So the first div is hidden on small screens but visible on medium and larger screens.

The second div uses block by default but md:hidden hides it on medium and larger screens. So it is visible only on small screens.

❓ selector

intermediate

Which Tailwind class hides an element but keeps its space?

In Tailwind CSS, which class hides an element visually but still keeps its space in the layout?

A invisible

B hidden

C opacity-0

D sr-only

💡 Hint

Consider the difference between removing an element from layout vs making it transparent.

The invisible class makes the element transparent but it still occupies space in the layout.

The hidden class removes the element from the layout entirely.

opacity-0 makes the element fully transparent but it can still respond to events.

sr-only hides the element visually but keeps it accessible to screen readers.

🧠 Conceptual

advanced

What is the effect of combining 'hidden' and 'sr-only' classes?

If an element has both hidden and sr-only classes in Tailwind CSS, what will be the result?

A The element is hidden visually but accessible to screen readers

B The element is visible visually but hidden from screen readers

C The element is hidden visually and from screen readers

D The element is visible both visually and to screen readers

💡 Hint

Consider which class takes precedence and what each class does.

The hidden class applies display: none;, which hides the element visually and removes it from the accessibility tree, so screen readers cannot access it.

The sr-only class hides the element visually but keeps it accessible to screen readers.

When combined, hidden overrides sr-only, so the element is hidden both visually and from screen readers.

❓ layout

advanced

How does 'invisible' affect layout compared to 'hidden'?

Consider two divs styled with Tailwind CSS: one with invisible and one with hidden. How do they differ in layout behavior?

A Both remove the element from the layout flow

B <code>invisible</code> keeps space, <code>hidden</code> removes space

C <code>hidden</code> keeps space, <code>invisible</code> removes space

D Both keep the element visible but transparent

💡 Hint

Think about how CSS display and visibility properties affect layout.

invisible sets visibility: hidden;, which hides the element visually but keeps its space in the layout.

hidden sets display: none;, which removes the element from the layout flow entirely, so no space is reserved.

❓ accessibility

expert

Which Tailwind class combination ensures an element is hidden visually but accessible to screen readers and keyboard navigation?

You want to hide a button visually but keep it accessible to screen readers and keyboard users. Which Tailwind CSS class or combination achieves this?

A hidden

B invisible focusable

C opacity-0 pointer-events-none

D sr-only

💡 Hint

Consider the purpose of the sr-only class and how it affects accessibility.

The sr-only class hides the element visually but keeps it accessible to screen readers and keyboard navigation.

hidden removes the element from the accessibility tree.

invisible hides visually but does not guarantee keyboard accessibility.

opacity-0 pointer-events-none hides visually and disables interaction, so keyboard users cannot access it.

Practice

1. What does the Tailwind CSS class hidden do to an element?

easy

A. It changes the element's color to transparent.

B. It hides the element and removes its space from the layout.

C. It makes the element semi-transparent.

D. It hides the element but keeps its space in the layout.

Solution

1. Step 1: Understand the hidden class effect

   The hidden class in Tailwind CSS sets display: none;, which hides the element completely.

2. Step 2: Effect on layout space

   Because the element is removed from the layout flow, its space is also removed, so no empty gap remains.

3. Final Answer:

   It hides the element and removes its space from the layout. -> Option B

4. Quick Check:

   hidden = hides + removes space [OK]

Hint: Hidden removes element and space; invisible hides but keeps space [OK]

Common Mistakes:

• Thinking hidden keeps space like invisible
• Confusing hidden with opacity or visibility
• Assuming hidden only makes element transparent

2. Which Tailwind CSS class hides an element but keeps its space reserved in the layout?

easy

A. hidden

B. opacity-0

C. sr-only

D. invisible

Solution

1. Step 1: Identify the class that hides but keeps space

   The invisible class sets visibility: hidden;, which hides the element but keeps its space.

2. Step 2: Compare with other options

   hidden removes element and space, opacity-0 makes element transparent but still interactive, sr-only hides visually but accessible to screen readers.

3. Final Answer:

   invisible -> Option D

4. Quick Check:

   invisible = hide but keep space [OK]

Hint: Invisible hides but reserves space; hidden removes space [OK]

Common Mistakes:

• Choosing hidden instead of invisible
• Confusing opacity-0 with invisible
• Thinking sr-only hides visually and removes space

3. What will be the visible result of this HTML snippet with Tailwind classes?

<div class="w-24 h-24 bg-blue-500 hidden">Box</div>
<div class="w-24 h-24 bg-red-500 invisible">Box</div>

medium

A. Only the red box space is reserved but not visible; blue box is hidden and removed.

B. No boxes visible; both hidden and invisible hide elements.

C. Only the red box is visible but transparent.

D. Both boxes visible but blue is hidden behind red.

Solution

1. Step 1: Analyze the blue box with hidden

   The blue box has hidden, so it is not visible and its space is removed from layout.

2. Step 2: Analyze the red box with invisible

   The red box is invisible, so it is hidden but its space remains reserved in the layout, leaving an empty gap.

3. Final Answer:

   Only the red box space is reserved but not visible; blue box is hidden and removed. -> Option A

4. Quick Check:

   hidden removes element; invisible hides but keeps space [OK]

Hint: Hidden removes element; invisible keeps space but hides content [OK]

Common Mistakes:

• Thinking invisible shows a transparent box
• Assuming hidden keeps space
• Believing both boxes are visible

4. You want to hide a button visually but keep it accessible for screen readers. Which Tailwind class should you use?

medium

A. sr-only

B. invisible

C. hidden

D. opacity-0

Solution

1. Step 1: Understand accessibility needs

   To hide visually but keep accessible, the element must be off-screen but still in the accessibility tree.

2. Step 2: Identify the correct Tailwind class

   sr-only hides the element visually but keeps it readable by screen readers, unlike hidden or invisible.

3. Final Answer:

   sr-only -> Option A

4. Quick Check:

   sr-only = hide visually, keep screen reader access [OK]

Hint: Use sr-only to hide visually but keep screen reader access [OK]

Common Mistakes:

• Using hidden which removes from accessibility tree
• Using invisible which hides visually but not accessible
• Using opacity-0 which hides visually but still interactive

5. You have a navigation menu that should be hidden on mobile but visible on larger screens. Which Tailwind classes correctly hide the menu on small screens but show it on medium and above?

hard

A. block md:hidden

B. invisible md:hidden

C. hidden md:block

D. hidden md:hidden

Solution

1. Step 1: Understand responsive classes

   hidden hides element by default (mobile), md:block shows element as block on medium screens and larger.

2. Step 2: Check other options

   invisible md:hidden hides but keeps space on mobile and hides on medium, so menu never visible. block md:hidden shows on mobile but hides on medium, opposite of requirement. hidden md:hidden hides always.

3. Final Answer:

   hidden md:block -> Option C

4. Quick Check:

   Hide mobile, show medium+ = hidden md:block [OK]

Hint: Use hidden for mobile, md:block to show on medium screens [OK]

Common Mistakes:

• Using md:hidden hides on medium screens instead of showing
• Using invisible which keeps space and confuses layout
• Using hidden md:hidden hides always