Challenge - 5 Problems
Navigation Mastery
Get all challenges correct to earn this badge!
Test your skills under time pressure!
🧠 Conceptual
intermediate2:00remaining
Why is semantic HTML important for navigation?
Which reason best explains why using semantic HTML elements like
Attempts:
2 left
💡 Hint
Think about how assistive technologies read web pages.
✗ Incorrect
Using semantic elements like
❓ layout
intermediate2:00remaining
Bootstrap navigation responsiveness
What happens to a Bootstrap navigation bar when viewed on a small mobile screen?
Attempts:
2 left
💡 Hint
Bootstrap uses a special button to show/hide navigation on small screens.
✗ Incorrect
Bootstrap's navbar component automatically collapses into a toggle button on small screens. This keeps the navigation compact and easy to use on mobile devices.
❓ accessibility
advanced2:00remaining
ARIA roles in navigation
Which ARIA role should be added to a custom navigation container to improve accessibility?
Attempts:
2 left
💡 Hint
This role identifies navigation landmarks for assistive technologies.
✗ Incorrect
The role="navigation" attribute tells screen readers that the element is a navigation section, helping users understand the page structure.
❓ selector
advanced2:00remaining
CSS selector for active navigation link
Given a Bootstrap navbar, which CSS selector correctly styles the active navigation link?
Bootsrap
<ul class="nav"> <li class="nav-item"> <a class="nav-link active" href="#">Home</a> </li> <li class="nav-item"> <a class="nav-link" href="#">About</a> </li> </ul>
Attempts:
2 left
💡 Hint
Look for the class that marks the active link.
✗ Incorrect
The active class is on the a element with class nav-link. The selector .nav-link.active targets it directly.
❓ rendering
expert3:00remaining
Screen reader behavior with missing navigation landmarks
What is the likely effect on screen reader users if a website's navigation is built without semantic
Attempts:
2 left
💡 Hint
Think about how screen readers find important page sections.
✗ Incorrect
Without semantic landmarks like <nav> or ARIA roles, screen readers cannot easily identify navigation areas. This makes it harder for users relying on assistive technology to find and use the navigation.