Bootstrap 5.3.8 • Chapter 21 • Responsive LTR + RTL
Checks Radios and Switches
Every topic includes its own Bootstrap coding example, explanation, ten teaching examples, expected result, practice, and responsive Persian/Arabic checks.
21.1 form-check
form-check is part of Bootstrap 5.3.8 covered in Chapter 21. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax. The example uses Bootstrap classes or APIs directly so you can connect the class name to its visual or interactive result.
For form-check in Chapter 21, inspect the DOM structure, Bootstrap class names, responsive breakpoint, and any data-bs attributes or JavaScript initialization. When Google Translate is active, also verify that longer labels wrap and the correct LTR or RTL Bootstrap stylesheet is enabled.
Test form-check at phone, tablet, laptop, and wide-screen sizes. Then translate the example to Persian and Arabic, increase browser zoom, and inspect whether rows, columns, forms, menus, overlays, and labels remain inside the viewport.
Concept in plain language
form-check is part of Bootstrap 5.3.8 covered in Chapter 21. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax.
10 teaching examples
Example 1: Minimal component
Build the smallest profile screen that demonstrates form-check. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 21, topic 1, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the checkout example for form-check. Compare the mobile layout with the tablet or desktop layout. Chapter 21, topic 1, example 2.
Example 3: Long translation
Replace a short English label in the contact form with a much longer translated label while using form-check. Confirm wrapping does not widen the viewport. Chapter 21, topic 1, example 3.
Example 4: Persian test
Translate the article to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 21, topic 1, example 4.
Example 5: Arabic test
Translate the settings panel to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 21, topic 1, example 5.
Example 6: Accessibility review
Use form-check in the gallery and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 21, topic 1, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the support page. Adjust the Bootstrap structure without hiding meaningful content. Chapter 21, topic 1, example 7.
Example 8: Utility comparison
Rebuild one part of the event page using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 21, topic 1, example 8.
Example 9: JavaScript-state test
If form-check uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the analytics page. If not, verify the example works without JavaScript. Chapter 21, topic 1, example 9.
Example 10: Production review
Review form-check in the account page for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 21, topic 1, example 10.
Bootstrap coding example
<div class="form-check"><input class="form-check-input" type="checkbox" id="c1"><label class="form-check-label" for="c1">Option</label></div>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for form-check.
- Read the HTML nesting first. Bootstrap components often depend on a specific relationship between wrappers, controls, and content.
- Resize the viewport and observe which responsive classes become active at each breakpoint.
- Translate the visible content. Long labels must wrap, .row children must be able to shrink, and tables should use a local responsive wrapper instead of widening the page.
- Switch to Persian or Arabic and confirm that the page has dir=rtl, Bootstrap's RTL stylesheet is active, start/end utilities behave correctly, and code examples remain LTR.
Expected result: The browser demonstrates form-check with responsive behavior. Persian and Arabic use RTL layout without creating page-wide horizontal scrolling; genuinely wide code or tables scroll locally.
Practice exercise
Build a new Bootstrap 5.3.8 example for form-check from Chapter 21. Test it at 320px, 768px, and desktop width, translate its visible text to Persian and Arabic, and explain which Bootstrap classes or JavaScript API create the final behavior.
21.2 Checkboxes
Checkboxes is part of Bootstrap 5.3.8 covered in Chapter 21. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax. The example uses Bootstrap classes or APIs directly so you can connect the class name to its visual or interactive result.
For Checkboxes in Chapter 21, inspect the DOM structure, Bootstrap class names, responsive breakpoint, and any data-bs attributes or JavaScript initialization. When Google Translate is active, also verify that longer labels wrap and the correct LTR or RTL Bootstrap stylesheet is enabled.
Test Checkboxes at phone, tablet, laptop, and wide-screen sizes. Then translate the example to Persian and Arabic, increase browser zoom, and inspect whether rows, columns, forms, menus, overlays, and labels remain inside the viewport.
Concept in plain language
Checkboxes is part of Bootstrap 5.3.8 covered in Chapter 21. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax.
10 teaching examples
Example 1: Minimal component
Build the smallest contact form that demonstrates Checkboxes. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 21, topic 2, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the article example for Checkboxes. Compare the mobile layout with the tablet or desktop layout. Chapter 21, topic 2, example 2.
Example 3: Long translation
Replace a short English label in the settings panel with a much longer translated label while using Checkboxes. Confirm wrapping does not widen the viewport. Chapter 21, topic 2, example 3.
Example 4: Persian test
Translate the gallery to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 21, topic 2, example 4.
Example 5: Arabic test
Translate the support page to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 21, topic 2, example 5.
Example 6: Accessibility review
Use Checkboxes in the event page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 21, topic 2, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the analytics page. Adjust the Bootstrap structure without hiding meaningful content. Chapter 21, topic 2, example 7.
Example 8: Utility comparison
Rebuild one part of the account page using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 21, topic 2, example 8.
Example 9: JavaScript-state test
If Checkboxes uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the lesson page. If not, verify the example works without JavaScript. Chapter 21, topic 2, example 9.
Example 10: Production review
Review Checkboxes in the admin page for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 21, topic 2, example 10.
Bootstrap coding example
<div class="form-check"><input class="form-check-input" type="checkbox" id="c2"><label class="form-check-label" for="c2">Email updates</label></div>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Checkboxes.
- Read the HTML nesting first. Bootstrap components often depend on a specific relationship between wrappers, controls, and content.
- Resize the viewport and observe which responsive classes become active at each breakpoint.
- Translate the visible content. Long labels must wrap, .row children must be able to shrink, and tables should use a local responsive wrapper instead of widening the page.
- Switch to Persian or Arabic and confirm that the page has dir=rtl, Bootstrap's RTL stylesheet is active, start/end utilities behave correctly, and code examples remain LTR.
Expected result: The browser demonstrates Checkboxes with responsive behavior. Persian and Arabic use RTL layout without creating page-wide horizontal scrolling; genuinely wide code or tables scroll locally.
Practice exercise
Build a new Bootstrap 5.3.8 example for Checkboxes from Chapter 21. Test it at 320px, 768px, and desktop width, translate its visible text to Persian and Arabic, and explain which Bootstrap classes or JavaScript API create the final behavior.
21.3 Radio Buttons
Radio Buttons is part of Bootstrap 5.3.8 covered in Chapter 21. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax. The example uses Bootstrap classes or APIs directly so you can connect the class name to its visual or interactive result.
For Radio Buttons in Chapter 21, inspect the DOM structure, Bootstrap class names, responsive breakpoint, and any data-bs attributes or JavaScript initialization. When Google Translate is active, also verify that longer labels wrap and the correct LTR or RTL Bootstrap stylesheet is enabled.
Test Radio Buttons at phone, tablet, laptop, and wide-screen sizes. Then translate the example to Persian and Arabic, increase browser zoom, and inspect whether rows, columns, forms, menus, overlays, and labels remain inside the viewport.
Concept in plain language
Radio Buttons is part of Bootstrap 5.3.8 covered in Chapter 21. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax.
10 teaching examples
Example 1: Minimal component
Build the smallest settings panel that demonstrates Radio Buttons. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 21, topic 3, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the gallery example for Radio Buttons. Compare the mobile layout with the tablet or desktop layout. Chapter 21, topic 3, example 2.
Example 3: Long translation
Replace a short English label in the support page with a much longer translated label while using Radio Buttons. Confirm wrapping does not widen the viewport. Chapter 21, topic 3, example 3.
Example 4: Persian test
Translate the event page to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 21, topic 3, example 4.
Example 5: Arabic test
Translate the analytics page to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 21, topic 3, example 5.
Example 6: Accessibility review
Use Radio Buttons in the account page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 21, topic 3, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the lesson page. Adjust the Bootstrap structure without hiding meaningful content. Chapter 21, topic 3, example 7.
Example 8: Utility comparison
Rebuild one part of the admin page using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 21, topic 3, example 8.
Example 9: JavaScript-state test
If Radio Buttons uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the booking page. If not, verify the example works without JavaScript. Chapter 21, topic 3, example 9.
Example 10: Production review
Review Radio Buttons in the course page for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 21, topic 3, example 10.
Bootstrap coding example
<div class="form-check"><input class="form-check-input" type="radio" name="choice" id="r1"><label class="form-check-label" for="r1">Choice A</label></div>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Radio Buttons.
- Read the HTML nesting first. Bootstrap components often depend on a specific relationship between wrappers, controls, and content.
- Resize the viewport and observe which responsive classes become active at each breakpoint.
- Translate the visible content. Long labels must wrap, .row children must be able to shrink, and tables should use a local responsive wrapper instead of widening the page.
- Switch to Persian or Arabic and confirm that the page has dir=rtl, Bootstrap's RTL stylesheet is active, start/end utilities behave correctly, and code examples remain LTR.
Expected result: The browser demonstrates Radio Buttons with responsive behavior. Persian and Arabic use RTL layout without creating page-wide horizontal scrolling; genuinely wide code or tables scroll locally.
Practice exercise
Build a new Bootstrap 5.3.8 example for Radio Buttons from Chapter 21. Test it at 320px, 768px, and desktop width, translate its visible text to Persian and Arabic, and explain which Bootstrap classes or JavaScript API create the final behavior.
21.4 Switches
Switches is part of Bootstrap 5.3.8 covered in Chapter 21. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax. The example uses Bootstrap classes or APIs directly so you can connect the class name to its visual or interactive result.
For Switches in Chapter 21, inspect the DOM structure, Bootstrap class names, responsive breakpoint, and any data-bs attributes or JavaScript initialization. When Google Translate is active, also verify that longer labels wrap and the correct LTR or RTL Bootstrap stylesheet is enabled.
Test Switches at phone, tablet, laptop, and wide-screen sizes. Then translate the example to Persian and Arabic, increase browser zoom, and inspect whether rows, columns, forms, menus, overlays, and labels remain inside the viewport.
Concept in plain language
Switches is part of Bootstrap 5.3.8 covered in Chapter 21. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax.
10 teaching examples
Example 1: Minimal component
Build the smallest support page that demonstrates Switches. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 21, topic 4, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the event page example for Switches. Compare the mobile layout with the tablet or desktop layout. Chapter 21, topic 4, example 2.
Example 3: Long translation
Replace a short English label in the analytics page with a much longer translated label while using Switches. Confirm wrapping does not widen the viewport. Chapter 21, topic 4, example 3.
Example 4: Persian test
Translate the account page to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 21, topic 4, example 4.
Example 5: Arabic test
Translate the lesson page to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 21, topic 4, example 5.
Example 6: Accessibility review
Use Switches in the admin page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 21, topic 4, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the booking page. Adjust the Bootstrap structure without hiding meaningful content. Chapter 21, topic 4, example 7.
Example 8: Utility comparison
Rebuild one part of the course page using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 21, topic 4, example 8.
Example 9: JavaScript-state test
If Switches uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the dashboard. If not, verify the example works without JavaScript. Chapter 21, topic 4, example 9.
Example 10: Production review
Review Switches in the profile screen for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 21, topic 4, example 10.
Bootstrap coding example
<div class="form-check form-switch"><input class="form-check-input" type="checkbox" role="switch" id="s1"><label class="form-check-label" for="s1">Dark mode</label></div>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Switches.
- Read the HTML nesting first. Bootstrap components often depend on a specific relationship between wrappers, controls, and content.
- Resize the viewport and observe which responsive classes become active at each breakpoint.
- Translate the visible content. Long labels must wrap, .row children must be able to shrink, and tables should use a local responsive wrapper instead of widening the page.
- Switch to Persian or Arabic and confirm that the page has dir=rtl, Bootstrap's RTL stylesheet is active, start/end utilities behave correctly, and code examples remain LTR.
Expected result: The browser demonstrates Switches with responsive behavior. Persian and Arabic use RTL layout without creating page-wide horizontal scrolling; genuinely wide code or tables scroll locally.
Practice exercise
Build a new Bootstrap 5.3.8 example for Switches from Chapter 21. Test it at 320px, 768px, and desktop width, translate its visible text to Persian and Arabic, and explain which Bootstrap classes or JavaScript API create the final behavior.
21.5 Inline Checks
Inline Checks is part of Bootstrap 5.3.8 covered in Chapter 21. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax. The example uses Bootstrap classes or APIs directly so you can connect the class name to its visual or interactive result.
For Inline Checks in Chapter 21, inspect the DOM structure, Bootstrap class names, responsive breakpoint, and any data-bs attributes or JavaScript initialization. When Google Translate is active, also verify that longer labels wrap and the correct LTR or RTL Bootstrap stylesheet is enabled.
Test Inline Checks at phone, tablet, laptop, and wide-screen sizes. Then translate the example to Persian and Arabic, increase browser zoom, and inspect whether rows, columns, forms, menus, overlays, and labels remain inside the viewport.
Concept in plain language
Inline Checks is part of Bootstrap 5.3.8 covered in Chapter 21. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax.
10 teaching examples
Example 1: Minimal component
Build the smallest analytics page that demonstrates Inline Checks. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 21, topic 5, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the account page example for Inline Checks. Compare the mobile layout with the tablet or desktop layout. Chapter 21, topic 5, example 2.
Example 3: Long translation
Replace a short English label in the lesson page with a much longer translated label while using Inline Checks. Confirm wrapping does not widen the viewport. Chapter 21, topic 5, example 3.
Example 4: Persian test
Translate the admin page to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 21, topic 5, example 4.
Example 5: Arabic test
Translate the booking page to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 21, topic 5, example 5.
Example 6: Accessibility review
Use Inline Checks in the course page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 21, topic 5, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the dashboard. Adjust the Bootstrap structure without hiding meaningful content. Chapter 21, topic 5, example 7.
Example 8: Utility comparison
Rebuild one part of the profile screen using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 21, topic 5, example 8.
Example 9: JavaScript-state test
If Inline Checks uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the checkout. If not, verify the example works without JavaScript. Chapter 21, topic 5, example 9.
Example 10: Production review
Review Inline Checks in the contact form for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 21, topic 5, example 10.
Bootstrap coding example
<div class="form-check form-check-inline"><input class="form-check-input" type="checkbox" id="i1"><label class="form-check-label" for="i1">Inline</label></div>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Inline Checks.
- Read the HTML nesting first. Bootstrap components often depend on a specific relationship between wrappers, controls, and content.
- Resize the viewport and observe which responsive classes become active at each breakpoint.
- Translate the visible content. Long labels must wrap, .row children must be able to shrink, and tables should use a local responsive wrapper instead of widening the page.
- Switch to Persian or Arabic and confirm that the page has dir=rtl, Bootstrap's RTL stylesheet is active, start/end utilities behave correctly, and code examples remain LTR.
Expected result: The browser demonstrates Inline Checks with responsive behavior. Persian and Arabic use RTL layout without creating page-wide horizontal scrolling; genuinely wide code or tables scroll locally.
Practice exercise
Build a new Bootstrap 5.3.8 example for Inline Checks from Chapter 21. Test it at 320px, 768px, and desktop width, translate its visible text to Persian and Arabic, and explain which Bootstrap classes or JavaScript API create the final behavior.
Chapter 21 review — 10 questions and answers
1. What should you inspect when form-check does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in form-check. Then inspect computed styles to see which declaration wins.
2. How should form-check be tested before publishing?
Answer: Test form-check on narrow and wide screens, with long translated text, in Persian and Arabic RTL mode, at increased zoom, and with keyboard navigation where the component is interactive.
3. What should you inspect when Checkboxes does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Checkboxes. Then inspect computed styles to see which declaration wins.
4. How should Checkboxes be tested before publishing?
Answer: Test Checkboxes on narrow and wide screens, with long translated text, in Persian and Arabic RTL mode, at increased zoom, and with keyboard navigation where the component is interactive.
5. What should you inspect when Radio Buttons does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Radio Buttons. Then inspect computed styles to see which declaration wins.
6. How should Radio Buttons be tested before publishing?
Answer: Test Radio Buttons on narrow and wide screens, with long translated text, in Persian and Arabic RTL mode, at increased zoom, and with keyboard navigation where the component is interactive.
7. What should you inspect when Switches does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Switches. Then inspect computed styles to see which declaration wins.
8. How should Switches be tested before publishing?
Answer: Test Switches on narrow and wide screens, with long translated text, in Persian and Arabic RTL mode, at increased zoom, and with keyboard navigation where the component is interactive.
9. What should you inspect when Inline Checks does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Inline Checks. Then inspect computed styles to see which declaration wins.
10. How should Inline Checks be tested before publishing?
Answer: Test Inline Checks on narrow and wide screens, with long translated text, in Persian and Arabic RTL mode, at increased zoom, and with keyboard navigation where the component is interactive.