ARIA attributes in Bootstrap components

Introduction

ARIA attributes help make Bootstrap components usable by everyone, including people who use screen readers or keyboard navigation.

When you want to make a dropdown menu accessible to screen readers.

When you use modals and want to inform assistive technologies about their role and state.

When you create tabs and need to indicate which tab is active.

When you build collapsible sections and want to show if they are expanded or collapsed.

When you want to improve keyboard navigation and screen reader support in interactive components.

Syntax

Bootsrap

<element aria-attribute="value">...</element>

ARIA attributes start with aria- and provide extra information about elements.

Bootstrap components often include ARIA attributes automatically to improve accessibility.

Examples

This button uses aria-pressed to indicate it is toggled on.

Bootsrap

<button class="btn btn-primary" aria-pressed="true">Toggle</button>

The modal has role="dialog" and aria-modal="true" to tell screen readers it is a popup window.

Bootsrap

<div class="modal" role="dialog" aria-modal="true" aria-labelledby="modalTitle">...</div>

Tabs use role="tablist", role="tab", and aria-selected to show which tab is active.

Bootsrap

<ul class="nav nav-tabs" role="tablist">
  <li class="nav-item" role="presentation">
    <button class="nav-link active" id="home-tab" data-bs-toggle="tab" type="button" role="tab" aria-controls="home" aria-selected="true">Home</button>
  </li>
</ul>

The collapse button uses aria-expanded and aria-controls to indicate if the content is shown or hidden.

Bootsrap

<button class="btn btn-link" data-bs-toggle="collapse" data-bs-target="#collapseExample" aria-expanded="false" aria-controls="collapseExample">Toggle</button>

Sample Program

This example shows a Bootstrap modal with ARIA attributes like aria-labelledby, aria-hidden, and aria-modal to help screen readers understand the modal's purpose and state.

Bootsrap

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Bootstrap ARIA Example</title>
  <link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.0/dist/css/bootstrap.min.css" rel="stylesheet">
</head>
<body>
  <main class="container mt-4">
    <h1>Accessible Modal Example</h1>

    <!-- Button to open modal -->
    <button type="button" class="btn btn-primary" data-bs-toggle="modal" data-bs-target="#exampleModal" aria-haspopup="dialog" aria-controls="exampleModal">
      Open Modal
    </button>

    <!-- Modal -->
    <div class="modal fade" id="exampleModal" tabindex="-1" aria-labelledby="modalTitle" aria-hidden="true" role="dialog" aria-modal="true">
      <div class="modal-dialog">
        <div class="modal-content">
          <div class="modal-header">
            <h5 class="modal-title" id="modalTitle">Modal Title</h5>
            <button type="button" class="btn-close" data-bs-dismiss="modal" aria-label="Close"></button>
          </div>
          <div class="modal-body">
            <p>This modal uses ARIA attributes to improve accessibility.</p>
          </div>
          <div class="modal-footer">
            <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">Close</button>
          </div>
        </div>
      </div>
    </div>
  </main>

  <script src="https://cdn.jsdelivr.net/npm/bootstrap@5.3.0/dist/js/bootstrap.bundle.min.js"></script>
</body>
</html>

Important Notes

Bootstrap automatically adds many ARIA attributes to its components to help accessibility.

You can add or customize ARIA attributes if you want to improve or fix accessibility for your specific use case.

Always test your site with keyboard navigation and screen readers to ensure ARIA attributes work as expected.

Summary

ARIA attributes make Bootstrap components accessible to all users.

They provide extra information about roles, states, and properties of UI elements.

Bootstrap includes many ARIA attributes by default, but you can add more if needed.

Practice

1. What is the main purpose of ARIA attributes in Bootstrap components?

easy

A. To increase the loading speed of Bootstrap pages

B. To change the visual style of components

C. To add animations to Bootstrap elements

D. To improve accessibility by describing roles and states to assistive technologies

Solution

1. Step 1: Understand ARIA attributes

   ARIA attributes provide extra information about UI elements to assistive technologies like screen readers.

2. Step 2: Identify their role in Bootstrap

   Bootstrap uses ARIA attributes to make components accessible, not for styling or performance.

3. Final Answer:

   To improve accessibility by describing roles and states to assistive technologies -> Option D

4. Quick Check:

   ARIA = Accessibility info [OK]

Hint: ARIA attributes describe roles and states for accessibility [OK]

Common Mistakes:

• Thinking ARIA changes visual styles
• Assuming ARIA improves page speed
• Confusing ARIA with animations

2. Which ARIA attribute is correctly used in this Bootstrap button to indicate it controls a collapsible section?
<button class='btn btn-primary' aria-controls='collapseExample' aria-expanded='false'>Toggle</button>

easy

A. aria-controls and aria-expanded

B. aria-hidden and aria-pressed

C. aria-label and aria-live

D. aria-checked and aria-disabled

Solution

1. Step 1: Identify ARIA attributes for collapsible controls

   Buttons controlling collapsible areas use aria-controls to reference the collapsible element and aria-expanded to indicate open/closed state.

2. Step 2: Match attributes in the code snippet

   The button uses aria-controls='collapseExample' and aria-expanded='false', which is correct for collapsible control.

3. Final Answer:

   aria-controls and aria-expanded -> Option A

4. Quick Check:

   Collapsible button uses aria-controls + aria-expanded [OK]

Hint: Collapsible buttons use aria-controls and aria-expanded [OK]

Common Mistakes:

• Using aria-hidden which hides elements
• Confusing aria-pressed with aria-expanded
• Using aria-checked which is for checkboxes

3. What will be the effect of this Bootstrap alert component on screen readers?

<div class='alert alert-warning' role='alert' aria-live='assertive'>Warning message!</div>

medium

A. Screen readers will announce the warning message immediately and with high priority

B. Screen readers will ignore the alert message

C. The alert will only be visible visually but not read aloud

D. The alert will be read only when the user focuses on it

Solution

1. Step 1: Understand role='alert'

   The role='alert' tells assistive technologies this is an important message that should be announced immediately.

2. Step 2: Understand aria-live='assertive'

   This attribute makes screen readers announce the content as soon as it appears, interrupting other speech if needed.

3. Final Answer:

   Screen readers will announce the warning message immediately and with high priority -> Option A

4. Quick Check:

   role alert + aria-live assertive = immediate announcement [OK]

Hint: role alert with aria-live assertive triggers immediate screen reader alert [OK]

Common Mistakes:

• Thinking alerts are ignored by screen readers
• Assuming aria-live polite delays announcement
• Believing alerts require focus to be read

4. Identify the error in this Bootstrap modal trigger button:

<button type='button' class='btn btn-primary' data-bs-toggle='modal' data-bs-target='#myModal' aria-expanded='true'>Open Modal</button>

medium

A. data-bs-target should be a class selector, not an ID

B. data-bs-toggle should be 'dropdown' instead of 'modal'

C. aria-expanded should not be set on the modal trigger button

D. Missing aria-label attribute for accessibility

Solution

1. Step 1: Check ARIA usage on modal trigger buttons

   Modal trigger buttons should not use aria-expanded because modals are overlays, not expandable sections.

2. Step 2: Verify other attributes

   data-bs-toggle='modal' and data-bs-target='#myModal' are correct. aria-label is optional if button text is descriptive. data-bs-target uses ID selector correctly.

3. Final Answer:

   aria-expanded should not be set on the modal trigger button -> Option C

4. Quick Check:

   Modal triggers do not use aria-expanded [OK]

Hint: Modal triggers do not use aria-expanded attribute [OK]

Common Mistakes:

• Adding aria-expanded to modal buttons
• Confusing modal toggle with dropdown toggle
• Using class selector instead of ID for data-bs-target

5. You want to make a Bootstrap tab component fully accessible. Which ARIA attributes should you add to the tab buttons to indicate their roles and states correctly?

hard

A. aria-checked, aria-expanded, and aria-hidden

B. role='tab', aria-selected, and aria-controls

C. role='button', aria-pressed, and aria-live

D. aria-label, aria-disabled, and aria-haspopup

Solution

1. Step 1: Identify ARIA roles for tabs

   Tab buttons should have role='tab' to define their role in the tablist.

2. Step 2: Use state attributes for tabs

   aria-selected indicates which tab is active, and aria-controls links the tab to its tab panel.

3. Final Answer:

   role='tab', aria-selected, and aria-controls -> Option B

4. Quick Check:

   Tabs need role tab + aria-selected + aria-controls [OK]

Hint: Tabs use role tab plus aria-selected and aria-controls [OK]

Common Mistakes:

• Using aria-checked which is for checkboxes
• Confusing aria-pressed with aria-selected
• Adding aria-live which is for live regions