This is usually noted in the documentation. 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).īecause Bootstrap’s components are purposely designed to be fairly generic, authors may need to include further ARIA roles and attributes, as well as JavaScript behavior, to more accurately convey the precise nature and functionality of their component. Interactive componentsīootstrap’s interactive components-such as modal dialogs, dropdown menus and custom tooltips-are designed to work for touch, mouse and keyboard users. This documentation aims to provide developers with best practice examples to demonstrate the use of Bootstrap itself and illustrate appropriate semantic markup, including ways in which potential accessibility concerns can be addressed. Structural markupīootstrap’s styling and layout can be applied to a wide range of markup structures.

However, provided that these have been implemented correctly, it should be perfectly possible to create websites and applications with Bootstrap that fulfill WCAG 2.0 (A/AA/AAA), Section 508 and similar accessibility standards and requirements. The overall accessibility of any project built with Bootstrap depends in large part on the author’s markup, additional styling, and scripting they’ve included. A brief overview of Bootstrap’s features and limitations for the creation of accessible content.īootstrap 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.

Html accessibility screen reader