ARIA attributes in Bootstrap components - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does ARIA stand for and why is it important in Bootstrap components?

ARIA stands for Accessible Rich Internet Applications. It helps make Bootstrap components usable by people with disabilities by providing extra information to assistive technologies like screen readers.

beginner

Which ARIA attribute is commonly used in Bootstrap modals to indicate the modal dialog role?

The attribute role="dialog" is used to tell assistive technologies that the element is a dialog window, helping users understand the context.

beginner

How does the aria-expanded attribute work in Bootstrap's collapsible components?

The aria-expanded attribute shows if a collapsible element is open (true) or closed (false). This helps screen readers announce the current state to users.

intermediate

What is the purpose of aria-labelledby in Bootstrap components?

aria-labelledby links an element to another element that labels it, like a heading or title. This helps screen readers identify what the component is about.

beginner

Why should Bootstrap developers include ARIA attributes in their components?

Including ARIA attributes ensures that Bootstrap components are accessible to all users, including those using assistive technologies. It improves usability and meets accessibility standards.

Which ARIA attribute indicates if a Bootstrap dropdown menu is open or closed?

A aria-label

B aria-hidden

C aria-checked

D aria-expanded

aria-expanded shows whether the dropdown is open (true) or closed (false).

What role attribute does Bootstrap use for modal dialogs to help screen readers?

A role="dialog"

B role="button"

C role="alert"

D role="navigation"

role="dialog" identifies the modal as a dialog window for assistive technologies.

Which ARIA attribute helps link a Bootstrap component to its label or title?

A aria-describedby

B aria-controls

C aria-labelledby

D aria-live

aria-labelledby connects the component to the element that labels it.

In Bootstrap, what does aria-hidden="true" mean for an element?

A The element is hidden from screen readers

B The element is disabled

C The element is clickable

D The element is visible to screen readers

aria-hidden="true" hides the element from assistive technologies.

Why is it important to update ARIA attributes dynamically in Bootstrap components?

A To improve page load speed

B To keep assistive technologies informed about changes

C To reduce CSS file size

D To enable animations

Dynamic updates to ARIA attributes keep screen readers aware of component state changes, improving accessibility.

Explain how ARIA attributes improve accessibility in Bootstrap components. Give examples of at least two ARIA attributes and their roles.

Think about how screen readers understand component states and roles.

Describe the use of aria-labelledby and why it is important in Bootstrap components.

Consider how a screen reader knows what a component is about.

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