Keyboard navigation support in Bootsrap - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to make the button focusable by keyboard.

Bootsrap

<button type="button" [1]>Click me</button>

Drag options to blanks, or click blank then click option'

Atabindex="0"

Bdisabled

Chidden

Daria-hidden="true"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'disabled' makes the button unfocusable.

Using 'hidden' or 'aria-hidden' hides the element from keyboard and screen readers.

Adding tabindex="0" makes the button reachable by keyboard navigation.

2fill in blank

medium

Complete the code to add an accessible label for screen readers.

Bootsrap

<button type="button" aria-[1]="Close menu">×</button>

Drag options to blanks, or click blank then click option'

Aexpanded

Bhidden

Cpressed

Dlabel

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'aria-hidden' hides the element from assistive technologies.

Using 'aria-pressed' or 'aria-expanded' is for toggle states, not labels.

The aria-label attribute provides an accessible name for screen readers.

3fill in blank

hard

Fix the error in the code to allow keyboard users to open the dropdown menu.

Bootsrap

<div class="dropdown">
  <button class="btn btn-secondary dropdown-toggle" type="button" id="dropdownMenuButton" data-bs-toggle=[1] aria-expanded="false">
    Dropdown button
  </button>
  <ul class="dropdown-menu" aria-labelledby="dropdownMenuButton">
    <li><a class="dropdown-item" href="#">Action</a></li>
  </ul>
</div>

Drag options to blanks, or click blank then click option'

A"modal"

B"dropdown"

C"collapse"

D"tooltip"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'modal' or 'collapse' disables dropdown behavior.

Using 'tooltip' does not open menus.

The data-bs-toggle="dropdown" attribute enables Bootstrap's dropdown toggle behavior for keyboard and mouse users.

4fill in blank

hard

Fill both blanks to make the dropdown accessible and keyboard navigable.

Bootsrap

<div class="dropdown">
  <button class="btn btn-primary dropdown-toggle" type="button" id="dropdownMenuButton" data-bs-toggle=[1] aria-haspopup=[2] aria-expanded="false">
    Menu
  </button>
  <ul class="dropdown-menu" aria-labelledby="dropdownMenuButton">
    <li><a class="dropdown-item" href="#">Item 1</a></li>
  </ul>
</div>

Drag options to blanks, or click blank then click option'

A"dropdown"

B"true"

C"false"

D"menu"

Attempts:

3 left

💡 Hint

Common Mistakes

Leaving aria-haspopup as false or missing reduces accessibility.

Using wrong toggle values disables dropdown behavior.

Setting data-bs-toggle="dropdown" activates the dropdown. Adding aria-haspopup="true" informs assistive tech that the button controls a menu.

5fill in blank

hard

Fill all three blanks to create a keyboard accessible modal trigger button.

Bootsrap

<button type="button" class="btn btn-primary" data-bs-toggle=[1] data-bs-target=[2] aria-[3]="false">
  Launch modal
</button>

Drag options to blanks, or click blank then click option'

A"modal"

B"#exampleModal"

Cexpanded

Dpressed

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong toggle values disables modal functionality.

Incorrect aria attribute reduces accessibility.

The button uses data-bs-toggle="modal" to open a modal. The data-bs-target="#exampleModal" points to the modal's ID. The aria-expanded="false" indicates the modal is initially closed.

Practice

1. What is the main purpose of keyboard navigation support in Bootstrap?

easy

A. To disable mouse clicks on buttons

B. To add animations to buttons

C. To change the color scheme automatically

D. To allow users to navigate the website using only the keyboard

Solution

1. Step 1: Understand keyboard navigation

   Keyboard navigation means users can move through a website using keys like Tab, Enter, and arrow keys without a mouse.

2. Step 2: Identify Bootstrap's support

   Bootstrap components are designed to support keyboard navigation for accessibility and ease of use.

3. Final Answer:

   To allow users to navigate the website using only the keyboard -> Option D

4. Quick Check:

   Keyboard navigation = navigate site with keyboard [OK]

Hint: Keyboard navigation means using keys, not mouse [OK]

Common Mistakes:

• Thinking it adds visual effects
• Confusing with color or style changes
• Assuming it disables mouse input

2. Which HTML attribute is commonly used in Bootstrap to make custom elements focusable for keyboard navigation?

easy

A. tabindex

B. aria-label

C. data-toggle

D. role

Solution

1. Step 1: Identify attribute for focus

   The tabindex attribute allows elements to receive keyboard focus and be reachable by Tab key.

2. Step 2: Confirm Bootstrap usage

   Bootstrap uses tabindex to enable keyboard navigation on custom interactive elements.

3. Final Answer:

   tabindex -> Option A

4. Quick Check:

   Focusable elements use tabindex [OK]

Hint: tabindex controls keyboard focus order [OK]

Common Mistakes:

• Confusing aria-label with focus control
• Using data-toggle which is for JS behavior
• Using role which defines semantics, not focus

3. Consider this Bootstrap button code:

<button class="btn btn-primary">Click Me</button>

What happens when you press the Tab key repeatedly on the page?

medium

A. The button will change color automatically

B. The button will receive focus and can be activated with Enter or Space

C. The button will be skipped and not receive focus

D. The button will submit a form immediately

Solution

1. Step 1: Understand default button behavior

   Native buttons are focusable by default and receive keyboard focus when tabbing.

2. Step 2: Bootstrap styling does not remove focus

   Bootstrap styles do not disable keyboard focus or activation on buttons.

3. Final Answer:

   The button will receive focus and can be activated with Enter or Space -> Option B

4. Quick Check:

   Native buttons are keyboard accessible [OK]

Hint: Native buttons are focusable by default [OK]

Common Mistakes:

• Thinking Bootstrap disables keyboard focus
• Assuming buttons skip focus by default
• Confusing visual style with behavior

4. You have a custom Bootstrap dropdown menu that is not reachable by keyboard. Which is the most likely cause?

medium

A. Missing tabindex="-1" on the dropdown toggle button

B. Adding disabled attribute to the dropdown menu

C. Missing tabindex="0" or focusable attribute on the toggle element

D. Using aria-hidden="true" on the dropdown menu

Solution

1. Step 1: Check focusability of toggle

   For keyboard navigation, the dropdown toggle must be focusable, usually with tabindex="0" or a native focusable element.

2. Step 2: Identify common mistakes

   Missing tabindex or using tabindex="-1" prevents keyboard focus on toggle, making dropdown unreachable.

3. Final Answer:

   Missing tabindex="0" or focusable attribute on the toggle element -> Option C

4. Quick Check:

   Focusable toggle needs tabindex=0 [OK]

Hint: Toggle must be focusable with tabindex=0 [OK]

Common Mistakes:

• Using tabindex=-1 disables focus
• Hiding menu with aria-hidden disables access
• Disabling menu instead of toggle

5. You want to create a custom Bootstrap card component that is keyboard accessible. Which combination of attributes and roles should you add to the card container to support keyboard navigation and screen readers?

hard

A. tabindex="0" role="button" aria-label="Card details"

B. tabindex="-1" role="presentation" aria-hidden="true"

C. tabindex="0" role="img" aria-label="Card image"

D. tabindex="-1" role="button" aria-disabled="true"

Solution

1. Step 1: Make card focusable

   Adding tabindex="0" makes the card reachable by keyboard Tab key.

2. Step 2: Define semantic role and label

   Using role="button" tells assistive tech the card is interactive, and aria-label describes it.

3. Final Answer:

   tabindex="0" role="button" aria-label="Card details" -> Option A

4. Quick Check:

   Focusable + role=button + aria-label = accessible card [OK]

Hint: Use tabindex=0 and role=button for custom interactive elements [OK]

Common Mistakes:

• Using tabindex=-1 disables keyboard focus
• Using role=presentation hides semantics
• Marking aria-disabled true disables interaction