A brief overview of CoreUI for Bootstrap features and limitations for the creation of accessible content.
CoreUI for Bootstrap provides an easy-to-use framework of ready-made styles, layout tools, and interactive components, allowing developers to create websites and applications that are visually appealing, functionally rich, and accessible out of the box.
The overall accessibility of any project built with CoreUI for Bootstrap depends in large part on the author’s markup, additional styling, and scripting they’ve included. However, provided that these have been implemented correctly, it should be perfectly possible to create websites and applications with CoreUI for Bootstrap that fulfill WCAG 2.1 (A/AA/AAA), Section 508, and similar accessibility standards and requirements.
CoreUI for Bootstrap styling and layout can be applied to a wide range of markup structures. This documentation aims to provide developers with best practice examples to demonstrate the use of CoreUI for Bootstrap itself and illustrate appropriate semantic markup, including ways in which potential accessibility concerns can be addressed.
CoreUI for Bootstrap interactive components—such as modal dialogs, dropdown menus, and custom tooltips—are designed to work for touch, mouse, and keyboard users. Through the use of relevant WAI-ARIA roles and attributes, these components should also be understandable and operable using assistive technologies (such as screen readers).
Some combinations of colors that currently make up CoreUI for Bootstrap default palette—used throughout the framework for things such as button variations, alert variations, form validation indicators—may lead to insufficient color contrast (below the recommended WCAG 2.1 text color contrast ratio of 4.5:1 and the WCAG 2.1 non-text color contrast ratio of 3:1), particularly when used against a light background. Authors are encouraged to test their specific uses of color and, where necessary, manually modify/extend these default colors to ensure adequate color contrast ratios.
Content which should be visually hidden, but remain accessible to assistive technologies such as screen readers, can be styled using the
.visually-hidden class. This can be useful in situations where additional visual information or cues (such as meaning denoted through the use of color) need to also be conveyed to non-visual users.
<p class="text-danger"> <span class="visually-hidden">Danger: </span> This action is not reversible </p>
For visually hidden interactive controls, such as traditional “skip” links, use the
.visually-hidden-focusable class. This will ensure that the control becomes visible once focused (for sighted keyboard users). Watch out, compared to the equivalent
.sr-only-focusable classes in past versions, CoreUI’s
.visually-hidden-focusable is a standalone class, and must not be used in combination with the
<a class="visually-hidden-focusable" href="#content">Skip to main content</a>
CoreUI for Bootstrap includes support for the
prefers-reduced-motion media feature. In browsers/environments that allow the user to specify their preference for reduced motion, most CSS transition effects in CoreUI for Bootstrap (for instance, when a modal dialog is opened or closed, or the sliding animation in carousels) will be disabled, and meaningful animations (such as spinners) will be slowed down.
On browsers that support
prefers-reduced-motion, and where the user has not explicitly signaled that they’d prefer reduced motion (i.e. where
prefers-reduced-motion: no-preference), CoreUI for Bootstrap enables smooth scrolling using the